Content Manager EE API logging

After you configure IBM CMIS for Content Manager, you can modify the logging and tracing properties of IBM CMIS for Content Manager. IBM CMIS for Content Manager uses Content Manager EE connector Java API to connect to Content Manager EE.

To change the log file and log level for the Content Manager EE connector Java API, modify the log4j2.xml file of Content Manager EE. For example, the log4j2.xml is in the following path: IBM Content Navigator_installation_directory/configure/ explodedformat/cmcmis/WEB-INF/classes/connectors. For example, on Microsoft Windows, the log4j2.xml file is in the following path:

C:\Program Files\IBM\CMIS\configure\explodedformat\cmcmis\WEB-INF\classes\connectors

The property DKAPIJavaLogLevel is used to control the log and trace levels. The fileName, SizeBasedTriggeringPolicy, and DefaultRolloverStrategy attributes under the RollingFile element are used to indicate the name of the log file, the size of each log file, and the number of backup files to maintain.

After you finish modifying the log4j2.xml file, you must run the IBM Content NavigatorConfiguration and Deployment Tool again to rebuild and redeploy the IBM CMIS for Content Manager application to make changes take effect.

Alternatively you can skip the reconfiguration and redeployment by modifying the log4j2.xml file that is installed in WAS_HOME/profiles/PROFILE_NAME/installedApps/CELL_NAME/cmcmis.ear/cmcis.war/WEB-INF/classes/connectors. For example, on Windows this file is in the following path:

C:\Program Files\WebSphere\AppServer\profiles\AppSrv01
\devhostNode01Cell\cmcmis.ear\cmcmis.war\WEB-INF\classes\connectors.

However, if you have deployed IBM CMIS for Content Manager application in a WebSphere® Application Server cluster, change the log4j2.xml file in each of cluster members. But, if you modify the log4j2.xml file of IBM Content Navigator and reconfigure and redeploy IBM CMIS for Content Manager, the configuration program applies the changes to all members of the cluster.

The Content Manager EE connector Java API dklog.log is in the following path: WAS_HOME/profiles/PROFILE_NAME/installedApps/CELL_NAME/cmcmis.ear/cmcis.war/WEB-INF/classes/cmlog/connectors. For example, on Windows, this file is in:

C:\Program Files\WebSphere\AppServer\profiles\AppSrv01
\devhostNode01Cell\cmcmis.ear\cmcmis.war\WEB-INF\classes\cmlog\connectors