Tracing a SIP container

You can trace a Session Initiation Protocol (SIP) container, starting either immediately or after the next server startup. This tracing writes a record of SIP events to a log file.

About this task

Follow these steps to start tracing a SIP container:

Procedure

  1. Open the administrative console.
  2. In the administrative console, click Troubleshooting > Logs and trace.
  3. Select the name of the server for the SIP container.
  4. From the General Properties section, click Diagnostic Trace Service.
  5. Under the Additional Properties section, click Change Log Detail Levels
  6. Select one of the following options:
    Option Description
    Configuration To start tracing after the next server startup
    Runtime To start tracing immediately
  7. Replace the content of the trace specification with the following code: com.ibm.ws.sip.*=all=enabled.
    Note: If you want monitor only specific pieces of SIP containers, expand the com.ibm.ws.sip section and select the individual items you wish to trace.
  8. Make sure that the Enable trace with following specification check box is checked.
  9. Click Apply > Save.

What to do next

When the changes take effect (refer to step 6), SIP-level tracing messages appear in WASProductDir/logs/serverName/trace.log, where WASProductDir is the fully qualified path name of the directory in which the product is installed and serverName is the name of the specific instance of the application server that is running the SIP container to be traced. These messages include application load events as well as SIP request and response parsing and SIP servlet invocation.
Note: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. You can also use HPEL in conjunction with your native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.