IBM FileNet P8, Version 5.2.1            

Viewing the FileNet P8 log files

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

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

Component

Logs

Application Engine

WebDav error logging
To assist administrators in tracking down errors encountered by WebDAV users, you can enable logging using Log4J. Logging is disabled by default.

Content Platform Engine

Troubleshooting and error logging

The p8_server_error.log file and the pesvr_system.log file contain Content Platform Engine server errors and any embedded exceptions or errors. These log files are the primary troubleshooting tool for Content Platform Engine.

In cluster environments, the log files exist on each server. The files are located in the server_instance_name subdirectory under the current working directory of the deployed application. By default, the files are located in the following directories:

  • WebSphere® Application Server:

    install_root/profiles/profile_name/FileNet/server_instance_name

  • WebLogic Server:

    bea/user_projects/domains/domain_name/FileNet/AdminServer

  • JBoss Application Server:

    jboss_install/jboss-as/bin/FileNet/server_instance_name

Trace logging and troubleshooting

By default, the p8_server_trace.log and pesvr_trace.log files are stored in the same location as the troubleshooting and error logging files.

For information about creating a trace log, see Creating a trace log.

For descriptions of the FileNet P8 subsystems that permit trace logging, see Trace Logging Concepts.

For information about setting or viewing workflow system trace logging information, see trace.

Audit logging
See Viewing audit entries.
Event logging
See About event logs.
Storage consistency checker logging
For information about generating a log from the storage consistency checker tool, see Maintaining storage area integrity.
Rules troubleshooting
See Troubleshooting rules functionality.

DITA Rendition Engine publishing

Troubleshooting
For information about preventing full log errors during document rendering, see Troubleshooting publishing problems.


Last updated: March 2016
logs_reference.htm

© Copyright IBM Corporation 2017.