|
There are a few options when turning on tracing and logging. You can get severe errors and system errors as well as package specific tracing (if enabled). Logging/tracing usually found in /WebSphere/AppServer/profiles//logs/. See ... |
|
==Where to look for exceptions or errors==
db2diag.log About DB2 diagnostic log (db2diag.log) files: [[http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.pd.doc/doc/t0020814.htm|Setting the diagnostic log file error capture level] Related ... |
|
Using the Information Center, there is a page about http:publib.boulder.ibm.cominfocenterwmbhelpv6r0m0topiccom.ibm.support.core.doctopicsgettingfixes.htmGetting Fixes. A product fix might be available to resolve your problem. Is it running
Make sure the Event Broker is started, ... |
|
Where to look for errors (SystemOut, SystemErr, ffdc)
Loggingtracing usually found in WebSphereAppServerprofilesprofilenamelogs. See Logging and tracing at the Info Center. Server logs: Look in system error logs, found in ... |
|
For debugging the Sametime 8.0 Client, we have two options. Help Support View Log
Help Support View Trace How to turn the log level up By default, the Logging and Trace is set to only capture Severe errors. You can change this setting by changing the following file: ... |
|
Use the following articles to help you troubleshoot Sametime Advanced client, WebSphere Application Server, Event Broker, and DB2 components. http:www10.lotus.comlddstwiki.nsfdxHowtoturntheloglevelupTroubleshooting the Sametime Advanced 8 Client ... |
|
|
|
This article needs to describe Location Services and how this functionality works. It should include: 1. Correct configuration of the Sametime Connect client, including whether or not the following two lines are required in the plugincustomization.ini file: ... |
|
Troubleshooting Event Broker password changes
If you have changed the password that is used either as the password for the ServiceUserId or DataSourceUserId for any of the IBM® WebSphere® Event Broker components, for example a remote DB2® server, you might find these components have access ... |
|
Troubleshooting authentication
If users are having difficulties authenticating, check their browser settings for cookies and language
Authenticated users cannot enter chat rooms unless they accept cookies. If a user logs in to IBM® Lotus® Sametime® Advanced and cannot enter a chat room where the ... |
|
Troubleshooting a failed WebSphere Application Startup
In the event that a change is made to a WebSphere® Application Server component of IBM® Lotus® Sametime® Advanced, WebSphere Application Server could fail to start. 1. Use a text editor to open the WebSphere Application Server file here: ... |
|
Troubleshooting using JVM logs
To start troubleshooting a problem, check the JVM log files first. These log files collect output for the System.out and System.err output streams for the application server process. One log file is specified for the SystemOut.log output stream and one file ... |
|
Logging and tracing
The Integrated Solutions Console provides logs to collect logging messages. System messages for IBM Lotus Sametime Advanced are written to the IBM service log. The IBM service log can be helpful in monitoring the health of the application server, however, the problem ... |
|
Troubleshooting Sametime Advanced
Here are some steps for checking your IBM Lotus Sametime Advanced Server deployment(s). 1. Identify the deployment scenario (ISMP/Archive installer, clustered, etc.). 2. ISMP - Make sure you have installed and configured Prereqs first. 3. Simple techniques to ... |