Managing the application server trace service

You can manage the trace service for a server process while the server is stopped and while it is running. You can specify which components to trace, where to send trace output, the characteristics of the trace output device, and which format to generate trace output in.

About this task

Modify the trace settings to help with diagnosing problems or tuning performance within certain applications.

Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

Procedure

Start the administrative console.
Click Troubleshooting > Logs and Trace > server_name.
Click the Diagnostic Trace link.
On the Configuration tab, do not select the None option.
If this option is selected, the trace data is not logged or recorded anywhere. All other handlers (including handlers registered by applications) still have an opportunity to process these traces.
On the Runtime tab, select either the Memory Buffer or File Trace Output option.
Specify the appropriate values for your configuration for either the Memory Buffer or File Trace Output option.
Click Apply.
Click Troubleshooting > Logs and Trace > server_name.
Click the Change Log Detail Levels link.
Under Additional properties, click Change Log Detail Levels.
On the Runtime tab, change the existing trace state by changing the trace specification to the desired state.
Click Apply.