Viewing the FileNet P8 logs

FileNet P8 provides logging capabilities for issue tracking, error tracking and troubleshooting, and auditing or process tracking.

The following list describes the logging and log file information that is available in the FileNet P8 help system for Content Platform Engine. For information about installation log files, see the appropriate installation and upgrade guide for your FileNet P8 component in Installing or upgrading FileNet P8.

Content Platform Engine system logs
Content and Process Engine system logs are written as text files in the server_instance_name subdirectory under the current working directory of the deployed application.
Content Platform Engine trace logs
When enabled, trace logs are also written as text files. By default these are located in the same directory as the system logs, but the location of the Content Engine trace log file can be changed through the Trace Logging Configuration property Output Location.
Audit logging
See Viewing audit entries.
Event logging
See About event logs.

Content Platform Engine logs for traditional deployments

In a cluster environment, the log and trace files exist on each server.

  • WebSphere® Application Server:

    install_root/profiles/profile_name/FileNet/server_instance_name

  • WebLogic Server:

    bea/user_projects/domains/domain_name/FileNet/AdminServer

The log files are named as follows:
Content Engine: ce_system0.log

Process Engine: pe_system0.log

The trace log files are named as follows:
Content Engine: ce_trace0.log

Process Engine: pe_trace0.log

Content Platform Engine logs for containerized deployments

The Content Platform Engine system and trace logs
For the Content Platform Engine instance can be found at /opt/ibm/wlp/usr/servers/defaultServer/FileNet/<CR metaname-cpeNN> on the file system of the Content Platform Engine container.
Application server logs
The Application server logs for the Content Platform Engine instance can be found at /opt/ibm/wlp/usr/servers/defaultServer/logs/<pod name> on the file system of the Content Platform Engine container.
Follow the steps to get logs
  1. Use the oc cp or kubectl cp command to work with files in the PV in the pods.
  2. See the following examples that show how to use CP. Pull log files from the PV for the fnlogs: 
    pod_name=$(kubectl get pod|grep cpe-deploy | awk '{print $1}')
oc cp $pod_name:/opt/ibm/wlp/usr/servers/defaultServer/FileNet/<CR metaname-cpe01>/ce_system.log ./localdir/