IBM service log settings
To configure the service log, also known as the activity log.
To view this admin console page, click...
Troubleshooting | Logs and Trace | server name | IBM Service Logs
To configure the IBM service log, also known as the activity log. The 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 WAS JVMs on a node, including all appservers and their node agent (if present). A separate activity log is created for a dmgr 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 service log.
- Enable service log
-
Specifies 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
-
Generation of a correlation ID that is logged with each message.
Use the correlation ID to correlate activity to a particular client request.
We can also use it to correlate activities on multiple appservers, if applicable.
Related concepts
Diagnose problems with message logs
Related tasks
Set the service log