IBM service log settings

 

+

Search Tips   |   Advanced Search

 

To view this console page, click...

Troubleshooting | Logs and Trace | server name | IBM Service Logs

Use this panel to configure the IBM service log, also known as the activity.log. The IBM service log contains both the WAS messages that are written to the System.out stream and some special messages that contain extended service information that can be important when analyzing problems. There is one service log for all JVMs on a node, including all appservers and their node agent (if present). A separate activity.log is created for a deployment manager in its own logs directory. The IBM Service log is maintained in a binary format.

Use the Log and Trace Analyzer or Showlog tool to view the IBM service log.

 

Configuration tab

Enable service log

Specify creation of a log file by the IBM Service log.

File Name

Name of the file used by the IBM Service log.

Maximum File Size

Maximum size in megabytes of the service log file. The default value is 2 megabytes.

When this size is reached, the service log wraps in place. Note that the service log does not roll over to a new log file like the JVM logs.

Enable Correlation ID

Specify the generation of a correlation ID that is logged with each message.

You can use the correlation ID to correlate activity to a particular client request.

You can also use it to correlate activities on multiple appservers, if applicable.




 

Related concepts

Diagnosing problems with message logs

 

Related tasks

Configure the service log