Enabling logging and tracing for a Sametime Proxy ServerAdded by IBM on November 23, 2011 | Version 1 (Original)
|The IBM® Sametime® Proxy Server utilizes 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.
® Proxy Server utilizes 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.
Before you begin
Ensure that the Sametime
Proxy Server is running.
About this task
Follow these steps to enable tracing on the Sametime
Parent topic: Troubleshooting a Sametime Proxy Server
- Login to the WebSphere® Integrated Solutions Console with administrator privileges on port 8601.
For example: https//yourserver.com:8601/ibm/console
- Select Troubleshooting -> Logs and Trace.
- Select STProxyServer.
- Select Diagnostic Trace.
- Select the Runtime tab.
- Select Change log level details.
- Type in the desired log setting, or select the components and levels by expanding the *[All Components] twistie.
- Enable the "Save runtime changes to configuration as well" checkbox.
will be created in ...\profiles\STPAppProfile\logs\STProxyServer
for Windows or /opt/IBM/WebSphere/AppServer/profiles/xxxxSTPPNProfilex/logs/STProxyServer
Log Levels by Component
|*=info ||Enabled by default. All SEVERE, WARNING, and INFO messages will be logged to Systemout.log and Systemerr.log.|
|Enables Sametime Proxy related logging to the FINEST level.|
|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.|
|Turns on all rtc4web logging to the FINEST level. In most cases, com.ibm.rtc.servlet.RTCServlet=fine should be sufficient.|