Work with trace

Use trace to obtain detailed information about running the WebSphere Application Server 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 we can use these files to pinpoint the failure. Collecting a trace is often requested by IBM technical support personnel. If we are not familiar with the internal structure of WAS, the trace output might not be meaningful to you.

(ZOS) We can configure trace settings with the administrative console, or we can configure tracing from the MVS™ console using the modify command.

IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .

Tasks

1. Configure an output destination to which trace data is sent.
2. Enable trace for the appropriate WAS or application components.

3. Run the application or operation to generate the trace data.

4. (iSeries) Analyze the trace data or forward it to the appropriate organization for analysis.

5. Analyze the trace data or forward it to the appropriate organization for analysis.

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.

Subtopics

• Enable trace on client and stand-alone applications
  
• Enable trace at server startup
  
• Enable trace on a running server
  
• Manage the application server trace service
  
• Diagnostic trace service settings
  
• Select a server to configure logging and tracing
  
• Log and trace settings
  
• Set up component trace (CTRACE)
  

Use High Performance Extensible Logging to troubleshoot applications