Tracing a SIP container
We can trace a SIP container, starting either immediately or after the next server startup. This tracing writes a record of SIP events to a log file.
Follow these steps to start tracing a SIP container:
Tasks
- Open the administrative console.
- In the administrative console, click Troubleshooting > Logs and trace.
- Select the name of the server for the SIP container.
- From the General Properties section, click Diagnostic Trace Service.
- Under the Additional Properties section, click Change Log Detail Levels
- Select one of the following options:
Option Description Configuration To start tracing after the next server startup Runtime To start tracing immediately - Replace the content of the trace specification with the following code: com.ibm.ws.sip.*=all=enabled.
If we want monitor only specific pieces of SIP containers, expand the com.ibm.ws.sip section and select the individual items you wish to trace.
- Verify the Enable trace with following specification check box is checked.
- 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 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.IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .
Configure the SIP container Browse all SIP topics Use the administrative console Use High Performance Extensible Logging to troubleshoot applications