Overview of logging

Enabling logging can help you troubleshoot an issue with your IBM® Sterling Control Center Monitor engine. The IBM support team uses logging to analyze the issue and help provide a solution.

IBM Sterling Control Center Monitor follows the standard way to adjust the log level to either increase or decrease log information. You can modify the logging setting for a corresponding IBM Sterling Control Center Monitor component in the following two setting files:
  • <CC Install Location>/conf/EngineLogger.xml
  • <CC Install Location>/conf/CCClientLogger.xml
If an issue arises, the IBM support team can have you enable logging to receive information about the error. The following are two locations to enable logging:
  • <CC Install Location>/log/*.log - This file contains the major log files that are generated by various IBM Sterling Control Center Monitor components in the console.
  • <CC Install Location>/web/ccbase/logs/*.log - This file contains log information that is generated from the IBM Sterling Control Center Monitor web console.

Adjusting the log level from lower to higher decreases the amount of log information that is shown to you. Adjusting the log level from a higher to a lower level increases the amount of log information that is shown to you. For example, in the (ControlCenter6.2.0}/conf/EngineLogger.xml file, there is a setting for the SLCService component log. The Logger name="SLCService" level="ERROR",SLCServiceAppender logger generates IBM Sterling Control Center Monitor ERROR log information in the (ControlCenter6.2.0}/log/SLCService_*.log file. You can change the log default ERROR to INFO to have more log information for the SLCService component.

To enable debug logging and OpenJPA SQL logging, add the following two lines to your EngineLogger.xml file:
  • Logger name="com.ibm.tenx" level="INFO"
  • Logger name="openjpa.jdbc.SQL" level="INFO"
Adding the lines to your file redirects all logging to your IBM Sterling Control Center Monitor engine's own logging framework.
Level Description
OFF Highest possible level. Turns off all logging.
ERROR Error events, but allows the application to continue running.
WARN Run time errors that can cause potentially harmful errors.
INFO Informational messages that highlight the progress of the application.
DEBUG Detailed information on the events in the system.
TRACE More detailed information about the events in the system than DEBUG.
ALL Lowest possible level. Turns on all logging.