WAS v8.5 > Troubleshoot > Work with trace

Manage the application server trace service

We can manage the trace service for a server process while the server is stopped and while it is running. We 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.

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

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

  1. Start the dmgr console.

  2. Click Troubleshooting > Logs and Trace > server_name.

  3. Click the Diagnostic Trace link.

  4. On the Configuration tab, do not select the None option. If this option is selected, the trace data is not logged or recorded anywhere. Other handlers (including handlers registered by applications) still have an opportunity to process these traces.

  5. On the Runtime tab, select either the Memory Buffer or File Trace Output option.

  6. Specify the appropriate values for the configuration for either the Memory Buffer or File Trace Output option.

  7. Click Apply.

  8. Click Troubleshooting > Logs and Trace > server_name.

  9. Click the Change Log Detail Levels link.

  10. Under Additional properties, click Change Log Detail Levels.

  11. On the Runtime tab, change the existing trace state by changing the trace specification to the desired state.

  12. Click Apply.


Related


Troubleshoot applications with HPEL


+

Search Tips   |   Advanced Search