WAS v8.5 > Troubleshoot > Use basic or traditional message logs

Configure the service log

The settings for service logs are typically shared for all servers, but we can configure a separate service log for each server process by overriding the configuration values at the server level.

The configuration values for the service log are inherited by each server process from the node configuration, but under certain circumstances you might wish to configure the service logs differently for individual servers. We can use the dmgr console to change the service log settings from the server level configuration panels.

IBM recommends using the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.

In WAS v7 and earlier, the service log is enabled by default. In WAS v8x, however, the service log is disabled by default. Configure your servers to use HPEL log and trace mode and use the HPEL API if you need to be able to merge log file content from multiple servers. Use the HPEL log, trace mode and the HPEL LogViewer command if you need to be able to render log content in Common Base Event XML format.

  1. Start the dmgr console.

  2. Click Troubleshooting > Logs and Trace > server_name > IBM Service Logs.

  3. Select the Enable box to enable the service log, or clear the check box to disable the log.

  4. Set the name for the service log.

    The default name is profile_root/logs/activity.log. If the name is changed, the run time requires write access to the new file, and the file must use the .log extension.

  5. Set the maximum file size.

    Number of megabytes to which the file can grow. When the file reaches this size, it wraps, replacing the oldest data with the newest data.

  6. Save the configuration.

  7. Restart the server to apply the configuration changes.


Subtopics


Related


Troubleshoot applications with HPEL


+

Search Tips   |   Advanced Search