IBM Support

Collecting Data for IBM FileNet Process Engine (PE) installation or upgrade issues

Question & Answer


Question

What information should be collected when you experience a problem during an IBM FileNet Process Engine (PE) installation or upgrade? Collecting this information before calling IBM support will help you understand the problem and save time during data analysis.

Answer

The installation/upgrade of FileNet P8 Process Engine (PE) is comprised of multiple steps within several specific phases. Depending on the step or phase of the installation/upgrade being completed, various logs will be useful in troubleshooting any issues encountered. A PE installation/upgrade can be broken down into the following 5 phases:

1. Installing Process Engine (PE)
2. Installing the Latest Content Engine (CE) Client Files on PE servers
3. Configuring Process Task Manager
4. PE Database Upgrade
5. Configuring PE Security Tab

The sections below outline the logs that should be reviewed and attached to a PMR if an issue is encountered at a given phase.

Note: The default paths given below are in Windows format; they are essentially the same paths in Unix, just replace "\" with "/". Only where the Unix path is different will both the Windows and Unix paths be specified.


Installing Process Engine: Laying down the binaries
  • <drive>:\Program Files\IBM\FileNet\PE\PE451_setup.log
  • <drive>:\Program Files\IBM\FileNet \IS\mini_installer.log
  • <drive>:\Program Files\Common files\InstallShield\Universal\Process Engine
  • ....\fnsw_loc\logs\elogs
  • ....\fnsw_loc\logs\fn_util\fn_util.log
  • Any .log files under C:\Program Files\IBM\FileNet\PE and C:\FNSW\tmp_installer

Additionally for Unix installations:
  • ..../fnsw/tmp_installer/PE451_setup.log (if the install has errors)
  • ..../fnsw/local/logs/wizard/date_time.log

InstallShield directory files: These are useful when install/uninstall has been attempted multiple times. Below are the InstallShield default locations for various platforms:
  • AIX (Premier Only) /usr/lib/objrepos/InstallShield/Universal/common
  • Generic Unix /usr/lib/InstallShield/Universal/common
  • HP-UX (user.home)/InstallShield/Universal/common
  • Linux (user.home)/InstallShield/Universal/common
  • Solaris (user.home)/InstallShield/Universal/common
  • Windows ….\InstallShield\Universal\Common Files

Installing the latest Content Engine (CE) Client Files on PE servers
  • Windows: <drive>:\Program Files\IBM\FileNet\CEClient\ceclient_install_log_4_5_1.txt
  • UNIX: /opt/IBM/FileNet/CEClient/ceclient_install_log_4_5_1.txt

Configuring Process Task Manager
  • Windows: \fnsw_loc\logs\TM_daemon\PEDirectoryServerConnectionDebug.txt
  • UNIX: /fnsw/local/logs/TM_daemon/PEDirectoryServerConnectionDebug.txt
    NOTE: in some environments the PEDirectoryServerConnectionDebug.txt is created in the directory where the installation media is located, so if you do not find the file in the path mentioned above, check the directory where you ran the PE installer from.

PE Database Upgrade - vwtool
  • ....\fnsw_loc\logs\elogs\
  • ....\fnsw_loc\lpgs\peconfig
  • ....\fnsw_loc\tmp\vwtrace

Configuring PE Security Tab
  • ...\fnsw_loc\logs\TM_daemon\PEDirectoryServerConnectionDebug.txt
  • ....\fnsw_loc\logs\elogs\
  • .... Run “vwcemp –l” from a command prompt to verify the database connection from PE, as well as verify that security settings were saved to the database.

At the Content Engine (CE), depending on your application server platform, collect the following:

WebSphere Application Server (WAS)
  • <WAS_install_path>\profiles\<profile_name>\FileNet\<server_name>\p8_server_trace.log
  • <WAS_install_path>\profiles\<profile_name>\FileNet\<server_name>\p8_server_error.log
  • <WAS_install_path>\profiles\<profile_name>\logs\<server_name>\SystemOut.log

Oracle WebLogic Application Server
  • <WLS_install_path\user_projects\domains\<domain_name>\FileNet\<server_name>\p8_server_trace.log
  • <WLS_install_path>\user_projects\domains\<domain_name>\FileNet\<server_name>\p8_server_error.log
  • <WLS_install_path>\user_projects\domains\<domain_name>\servers\<server_name>\logs\<server_name>.log
JBoss Application Server
  • <JBOSS_home>\bin/FileNet\<server_name>\p8_server_trace.log
  • <JBOSS_home>\bin/FileNet\<server_name>\p8_server_error.log
  • <JBOSS_home>\server\default\conf\log\server.log

[{"Product":{"code":"SSNW2F","label":"FileNet P8 Platform"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Process Engine","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"4.5.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21433784

Page Feedback