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.
What to do next
When the changes take effect (refer
to step 6 above), 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.
New feature: This topic
references one or more of the application server log files. Beginning
in WebSphere Application Server Version 8.0 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 or 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.
newfeat