Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > 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.
With WAS v8 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh.
Procedure
- Start the admin console.
- Click Troubleshoot > 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 the configuration for either the Memory Buffer or File Trace Output option.
- Click Apply.
- Click Troubleshoot > 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.
Use HPEL to troubleshoot applications
Related
Trace and logging configuration