The level of tracing is determined by the log level details
you select for the loggers. Loggers are organized hierarchically.
The children of the logger will inherit the parent log level by default,
but it can be changed by defining the level of tracing on each specific
logger.
To control the trace level for the
Trust Association Interceptor,
use the options on the
com.ibm.imsconnector.* trace
group. For more specific levels of tracing, use the following trace
groups, which are relevant to the
Trust Association Interceptor:
Table 1. TAI trace groups and trace loggersTrace group |
Trace loggers |
com.ibm.imsconnector.tai.* |
*BaseIMSInterceptor
*HttpInterceptor
*SipInterceptor
|
To control the trace level for
the
Presence Server component and its subcomponents, use the
options on the
com.ibm.presence.* trace
group. For more specific levels of tracing, use the following trace
groups, which are relevant to
Presence Server:
Table 2. Presence trace groups and
trace loggersTrace group |
Trace loggers |
com.ibm.presence.* |
*aggregators.*
*authorization.*
*channel.*
*charging.*
*component.*
*configuration.*
*contentindirection.*
*document.*
*externalsource.*
*init.*
*management.*
*managing.*
*monitor.*
*pmi.*
*provider.*
*rls.*
*service.*
*services.*
*sharedlists.*
*siplets.*
*storage.*
*subscribe.*
*timers.*
*util.*
*winfo.*
*xdms.*
*xml.*
|
AG attachments: - com.ibm.websphere.sca.soap.attachments.*
- com.ibm.ws.sca.soap.attachments.*
AG handlers:- com.ibm.soa.esb.global.handlers.*
- com.ibm.sca.connections.handlers.*
- com.ibm.ws.sca.soap.attachments.handlers.*
Tracing a SIP container
To
control the trace level for the SIP container, use the options on
the com.ibm.ws.sip.* trace group. For more detailed
information about tracing a SIP container or CEI, refer the WebSphere® Application Server
Network Deployment Information
Center.