Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support
Work with trace
Use trace to obtain detailed information about running the WAS components, including application servers, clients, and other processes in the environment.
Trace files show the time and sequence of methods called by WAS base classes, and you can use these files to pinpoint the failure. Collecting a trace is often requested by IBM technical support personnel. If you are not familiar with the internal structure of WAS, the trace output might not be meaningful to you.
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
- Configure an output destination to which trace data is sent.
- Enable trace for the appropriate WAS or application components.
- Run the application or operation to generate the trace data.
- Analyze the trace data or forward it to the appropriate organization for analysis.
Results
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.
Related
Enable trace on client and stand-alone applications
Trace and logging configuration
Enable trace at server startup
Enable trace on a running server
Manage the application server trace service
Trace output
Diagnostic trace service settings
Select a server to configure logging and tracing
Log and trace settings
Use HPEL to troubleshoot applications