Recommended trace settings

The settings listed in this topic are recommended for your convenience. However, you can select log levels from either the Configuration or the Runtime tab by expanding the Components and Groups section. Click a component name to select the log level from a context menu.

The default log level displays in the text box:

*=info

When you add a setting, it is appended to the default *=info setting. Each additional setting is delimited by a colon (:). For example, if you add the setting com.ibm.rtc.*=all the following result appears in the text box:

*=info: com.ibm.rtc.*=all

Notice that a colon (:) and a space was added before the name of the setting.

All Servers

To see all messages and traces for a specific server or component, add one of the following settings:

*=info:com.ibm.rtc.*=all

*=info:com.ibm.rtc.server.*=all

Sametime® Advanced Server

To see all messages and traces for a Sametime Advanced Server, add the following setting:

*=info:com.ibm.rtc.messaging.*=fine: com.ibm.rtc.polled.*=fine: com.ibm.rtc.servlet.*=all

Sametime Bandwidth Manager

For a single server:

*=info:com.avistar.*=all

If you suspect a problem with the SIP messaging, append:

com.ibm.ws.sip.*=all:
com.ibm.sip.*=all:

If you suspect a problem with federated repository or LDAP access, append:

*=info:com.ibm.websphere.wim.*=all:
com.ibm.wsspi.wim.*=all:
com.ibm.ws.wim.*=all

Sametime Gateway Server

In addition to viewing all traces and messages using the format listed in the All Servers section in this topic, if SIP traces are required, add the following setting.

com.ibm.ws.sip.stack.transaction.transport.TransportCommLayerMgr=all

The result looks like the following example:

*=info: com.ibm.rtc.gateway.*=all: 
com.ibm.ws.sip.stack.transaction.transport.TransportCommLayerMgr=all

To enable traces for WebSphere SIP proxy servers used in a cluster, add the following settings:

*=info: com.ibm.ws.sip.*=all:com.ibm.ws.proxy.*=all:

The result looks like the following example:

*=info: com.ibm.rtc.gateway.*=all: 
*=info: com.ibm.ws.sip.*=all:com.ibm.ws.proxy.*=all: 
com.ibm.ws.sip.stack.transaction.transport.TransportCommLayerMgr=all

Sametime Media Manager components

For the combined Sametime SIP Proxy/Registrar and the Conference Manager components, select the following settings:

*=info:com.lotus.sametime.telephony.*=all:
com.ibm.mediaserver.*=all:
com.ibm.telephony.conferencing.spi.*=all:
com.ibm.ws.sip.*=all:
com.lotus.sametime.telephony.sipfocus.*=all:
com.ibm.sip.*=all:
com.lotus.sametime.telephonymanager.*=all
com.ibm.vmgrconnector.*=all

For the Sametime SIP Proxy/Registrar in the CF+PR server, residing on the same computer or separate computer:

*=info:com.ibm.ws.sip.*=all:
com.ibm.sip.*=all

For the Sametime Video Manager:

*=info:com.polycom.proximo.*=all

For the WebSphere® proxy server used by a Media Manager cluster:

*=info:com.ibm.ws.proxy.*=all:

Sametime Meeting Server

To see all messages and traces for a Sametime Meeting Server, add the following settings:

*=info: com.ibm.rtc.messaging.*=fine: 
com.ibm.rtc.polled.*=fine: com.ibm.rtc.servlet.*=all

To add the traces required for troubleshooting meeting recording issues, enter the following setting on one line without spaces:

*=info:com.ibm.stavrecorder.*=all:com.ibm.stavrecorder=all:
com.ibm.sametime.stavrecorder.*=all:com.ibm.sametime.stavrecorder=all:
com.ibm.ws.sip.*=all:com.ibm.ice.*=fine:com.ibm.meetingserver.recording.*=all

To troubleshoot issues with the WebSphere proxy server used with the Sametime Meeting Server cluster use the following setting:

*=info: com.ibm.rtc.proxy.filter.*=all

Sametime Proxy Server

The Sametime Proxy Server uses the JSR-47 logging to record various events for troubleshooting. Using the IBM® WebSphere Integrated Solutions Console, you can fine tune the amount of captured trace content.

Use the following setting to enable Sametime Proxy related logging to the FINEST level.

*=info: com.ibm.rtc.stproxy.*=all:
com.ibm.collaboration.realtime.*=all

Sometimes it is necessary to turn on rtc4web long-poll logging. Use this level to trace the long-poll traffic during the Proxy run and use states.

*=info: com.ibm.rtc.stproxy.*=all:
com.ibm.rtc.servlet.RTCServlet=fine:
com.ibm.collaboration.realtime.*=all

Use the following settings if you need to turn on all rtc4web logging to the FINEST level. However, in most cases, com.ibm.rtc.servlet.RTCServlet=fine is sufficient.

*=info: com.ibm.rtc.*=all:
com.ibm.collaboration.realtime.*=all