Step 4: Configuration, logging and tracing for IBM WebSphere Application Server

You can configure the logging and tracing of the IBM® WebSphere® Application Server. Configuring the logging and tracing aids, provides diagnostic support for your runtime environment.

About this task

A trace file is created when these control are set for logging and tracing and you run your Java™ application using WebSphere Application Server.

Important: Ensure that only one client is running when the trace is on.

To configure logging and tracing for WebSphere Application Server:

Procedure

  1. From the WebSphere Application Server administrative console, expand Troubleshooting > Logs and trace to open the Logging and tracing page. The Logging and Tracing page opens.
    The Logging and Tracing page
  2. On the Logging and Tracing page, click the server for which you would like tracing (for example, server1) and click Diagnostic Trace. The Diagnostic trace service page opens.
  3. On the Configuration tab, specify to output the trace data to a file or to the memory buffer.
  4. You can accept the default name and location of the trace output file, or you can modify it. To modify the default name and location, enter a different name and location of the file in the File name field, and click OK.
  5. On the Logging and Tracing page, click Change Log Detail Levels. The Change Log Detail Levels page opens.
  6. To enable logging and tracing in the IMS™ TM resource adapter, enter the following string in the Groups field under General Properties on the Configuration tab, and click OK.
    *=info: com.ibm.j2ca.RAIMSTM=finest

    Add other combinations of trace strings to enable tracing in other components. For example, with the following trace string, com.ibm.ejs.j2c.* provides you with logging and tracing of the WebSphere Application Server implementation of the J2EE Connector Architecture.

    Tip: Click Save to save the changes to the master configuration.
  7. Repeat the previous step for the Runtime tab and click OK.
  8. Click Save at the top.
  9. Stop the server and then restart it.
  10. Run your Java application and then examine the trace file.

Feedback