Server log settings

Default log levels are set for each server type. You change the level for a log by editing the server.xml files, and in some cases the bootstrap.properties file.

The following server.xml elements define the default log levels for each server type.

cisDev
<logging 	
   traceSpecification="com.ibm.ia.*=fine:com.ibm.rules.*=fine:*=info"
   maxFiles="5" />
cisCatalog
<logging 	
   traceSpecification="*=info" maxFiles="5" />
cisContainer, cisInbound, cisOutbound
<logging 	
   traceSpecification="com.ibm.ia.*=info:com.ibm.rules.*=info:*=info"
   maxFiles="5" />

Log messages include the following message codes:

The following example shows an information message:
CWMBD0001I: Environment successfully started
Initialization was successful.
The following example shows a warning message:
CWMBD0002E: Environment failed to start
Could not start internal services.
Ensure that the product is properly installed.
The following example shows an error message:
CWMBD0002E: Event validation is incorrectly formatted.

Messages that are related to runtime processing are written to the log files as print statements. You can search for these print statements and use the information from the statement to assist with troubleshooting.

You can control how the rule agent logs are output to print statements by adding the RuleAgentPrintLogLevel property to the solution. For example:
solutionManager setproperty OilService RuleAgentPrintLogLevel=warning
The rule agent log output is written to the trace.log and message.log files when the logging level is set to the default value of info. You can set the logging level to one of the following values:
  • severe
  • warning
  • audit
  • info
  • fine
  • finer
  • finest
  • off