IBM Content Navigator, Version 2.0.3 Supports: CMIS for OnDemand

IBM CMIS for Content Manager OnDemand log files

IBM® CMIS for Content Manager OnDemand generates several log files that you can use to troubleshoot problems that occur when you install, configure, or use IBM CMIS for Content Manager OnDemand.

Installation log files

To determine the source of a problem with the installation or configuration of the IBM CMIS for Content Manager OnDemand web application, refer to the following log files:

Installation log file
Deployment profile log files

For more information on how to find these log files, see IBM Content Navigator log files.

Runtime log files

There are two types of runtime logging for IBM CMIS for Content Manager OnDemand:

IBM Content Manager OnDemand Web Enablement Kit logging

IBM CMIS for Content Manager OnDemand bundles and performs most content operations through the ODWEK Java API.

You can configure client-side trace logging if you need to troubleshoot problems related to IBM Content Manager OnDemand. By default, the ODWEK logging is not enabled. For information about configuring the arswww.log file for IBM CMIS for Content Manager OnDemand, see Configuring logging for IBM Content Manager OnDemand Web Enablement Kit (ODWEK).

IBM CMIS web application logging

The location of configuration logging information depends on the type of web application server on which IBM CMIS for Content Manager OnDemand is deployed.

WebSphere® Application Server users

SystemOut.log

IBM CMIS uses the Apache Commons Logging API, which can be configured through the WebSphere Application Server administrative console.

If you configure detail-level logging or higher (up to fatal-level logging) information is written to this log file and to the trace.log file.

Use this log file to review messages that occur when IBM CMIS is running. This log file contains informational messages, warning messages, and error messages.

If IBM CMIS throws an exception, this log file also includes stack trace.

By default, this log file is in the WAS_profile_location/logs/server/ subdirectory of the WebSphere Application Server installation directory.

To learn more about the SystemOut.log file, see Tracing and logging configuration in the WebSphere Application Server documentation.

For information about configuring the SystemOut.log file for IBM CMIS for Content Manager OnDemand, see Configuring logging for IBM CMIS for Content Manager OnDemand on WebSphere Application Server.

trace.log

IBM CMIS uses the Apache Commons Logging API, which can be configured through the WebSphere Application Server administrative console.

If you configure finest-level logging or higher (up to fatal-level logging), information is written to this log file. This log file is used by IBM Software Support to pinpoint when and where a failure occurred.

By default, this log file is in the WAS_profile_location/logs/server/ subdirectory of the WebSphere Application Server installation directory.

To learn more about the trace.log file, see Tracing and logging configuration in the WebSphere Application Server documentation.

For information about configuring the trace.log file for IBM CMIS for Content Manager OnDemand, see Configuring logging for IBM CMIS for Content Manager OnDemand on WebSphere Application Server.

Oracle WebLogic Server users

If you use Oracle WebLogic Server, configuration information is written to the log4j.properties file. On Oracle WebLogic Server, IBM CMIS for Content Manager OnDemand uses the Apache Commons Logging API, which can be configured through the IBM Content Navigator log4j.properties file on the IBM CMIS for Content Manager OnDemand web application server.

For information about configuring the log4j.properties file, see Configuring logging for IBM CMIS for Content Manager OnDemand on Oracle WebLogic Server.