Enabling trace at server startup

Use the administrative console to enable tracing at a server's startup. You can use trace to assist you in monitoring system performance and diagnosing problems.

About this task

The diagnostic trace configuration settings for a server process determines the initial trace state for a server process. The configuration settings are read at server startup and used to configure the trace service. You can also change many of the trace service properties or settings while the server process is running.

[z/OS] You can also configure tracing from the MVS console using the modify command.

Procedure

  1. Start the administrative console.
  2. [AIX HP-UX Linux Solaris Windows] [iSeries] Click Troubleshooting > Logging and Tracing in the console navigation tree, then click Server > Diagnostic Trace.
  3. [z/OS] Click Servers > Application Servers > server_name > Troubleshooting > Diagnostic Trace Service.
  4. Click Configuration.
  5. Select the Enable Log check box to enable trace, clear the check box to disable trace. Selecting the option turns off only the final step of logging these records to the WebSphere trace file. All other handlers (including handlers registered locally by customers or even applications) still have an opportunity to process these traces.
  6. Select whether to direct trace output to either a file or an in-memory circular buffer.
    Note: Different components can produce different amounts of trace output per entry. Naming and security tracing, for example, produces a much higher trace output than Web container tracing. Consider the type of data being collected when you configure your memory allocation and output settings.
  7. If the in-memory circular buffer is selected for the trace output set the size of the buffer, specified in thousands of entries. This is the maximum number of entries that will be retained in the buffer at any given time.
  8. If a file is selected for trace output, set the maximum size in megabytes to which the file should be allowed to grow. When the file reaches this size, the existing file will be closed, renamed, and a new file with the original name reopened. The new name of the file will be based upon the original name with a timestamp qualifier added to the name. In addition, specify the number of history files to keep.
  9. Select the desired format for the generated trace.
  10. Save the changed configuration.
  11. To enter a trace string to set the trace specification to the desired state:
    1. Click Troubleshooting > Logging and Tracing in the console navigation tree.
    2. Select a server name.
    3. Click Change Log Level Details.
    4. If All Components has been enabled, you might want to turn it off, and then enable specific components.
    5. Click a component or group name. For more information see Log level settings If the selected server is not running, you will not be able to see individual component in graphic mode.
    6. Enter a trace string in the trace string box.
    7. Select Apply, then OK.
  12. Allow enough time for the nodes to synchronize, and then start the server.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=ttrb_entrss
File name: ttrb_entrss.html