IBM service log settings
Configure the IBM service log, also known as the activity log.
Service log, commonly named activity.log is deprecated.
We can only access this page when the server is configured to use basic log and trace mode.
From the admin console, click...
Troubleshoot > Logs and Trace > server name > IBM Service Logs
Configure the IBM service log, also known as the activity log. The IBM service log contains both the WebSphere Application Server 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 Java virtual machines (JVMs) on a node, including all application servers 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.
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 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
The 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 application servers, if applicable.
Related:
Use basic or traditional message logs to troubleshoot applications Configure the service log