Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Work with trace
Enable trace on a running server
Use the admin console to enable tracing on a running server. We can use trace to assist you in monitoring system performance and diagnosing problems.
We can modify the trace service state that determines which components are being actively traced for a running server by using the following procedure.
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 then click server > Diagnostic Trace.
- Select the Runtime tab.
- Select the Save runtime changes to configuration as well check box to write your changes back to the server configuration.
- Change the existing trace state by changing the trace specification to the desired state. Refer to the following topics for specific information on how to change your trace specifications:
- "Diagnostic trace service settings" describes how you can examine the current diagnostic trace settings and to change where the trace is written (memory buffer or file). If the trace is to be recorded in a memory buffer, you can specify the file to which the memory buffer is to be dumped. We can view the file for trace information.
- "Log and trace settings" describes how you can view and configure logging and trace settings for the server.
- "Managing the application server trace service" describes how you 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. We can select where the trace is written (memory buffer or file).
On an application server, trace output can be directed either to a file or to an in-memory circular buffer. If trace output is directed to the in-memory circular buffer, it must be dumped to a file before it can be viewed.
On an application client or stand-alone process, trace output can be directed either to a file or to the process console window.
- Configure the trace output if a change from the existing one is desired.
- Click Apply.
Enable trace at server startup
Turning traces on and off in servers processes using scripting
Configure traces using scripting
Trace operations using wsadmin.sh
Use HPEL to troubleshoot applications
Related
Trace and logging configuration