What data can you gather to troubleshoot problems with Lotus Connections Wikis?
Diagnosing the problem
Do you want to automate the collection of MustGather data?
Log information has now been automated in the IBM Support Assistant Lite for Lotus Connections tool, which is included with the Connections product..
It can be found in <LC program dir>\data\shared\tools\isa\LC3.0_ISA_Lite.zip (or .tar if unix/linux)
Alternatively, For more information about automating data collection, download the ISA lite for LC:
Title: Download IBM Support Assistant (ISA) Lite for Lotus Connections
Doc #: 4025198
Manual Files to collect (if not using ISA lite)
Collecting the following data before contacting support will help expedite problem determination and resolution of the problem:
1. Provide a precise description of the issue, error message, and steps to reproduce.
2. Provide any applicable screen shots.
3. Systemout.log and systemerr.log located in %WAS_HOME%\profiles\(your profile)\logs\server1 is the primary logging file for the Lotus Connections Wikis component.
When collecting this file and sending to support be sure to:
a. Reproduce the problem
b. Specify the time the problem was reproduced
4. LotusConnections-config.xml located in directory %WAS_HOME%\profiles\(your profile)\config\cells\(your cell)\LotusConnections-config stores properties that control common Lotus Connections features, such as the navigation bar links. This is a file to collect if navigation is not working correctly while navigating the various Lotus Connections Components
Also in that directory are the following files to provide:
1. The application server's SystemOut.log (note time issue was reproduced)
2. The application server's ffdc log
3. The application server's trace.log
When running the ISALite Collector, you can edit or modify the trace setting.
When the particular function of a Connections App is isolated, support may ask for a specific trace setting to be applied, other than the default trace setting entered by ISALite, in order to get obtain data for the reported problem and also to minimize the amount of data collected.
|General Wikis issue
com.ibm.quickr.share.services.*=all: com.ibm.quickr.share.platform.*=all: com.ibm.lconn.wikis.*=all
(will get all SQL queries along with tracing exceptions)
(for the SQL queries if you don't want any additional trace)
1. Shut down the WAS Server and move to another directory (or delete) Systemout.log and systemerr.log, trace.log and all FFDC logs so a new set of clean logs with tracing can be created
2. Start the server and reproduce the problem.
3. The tracing will be recorded to trace file located in %WAS_HOME%/profiles/appSrv01/logs/server1/trace.log
6. Provide support the trace.log, systemout.log, systemerr.log and FFDC logs along with configuration files from the Files to Collect section above.
Note: The ISALite tool will collect the Files mentioned above. However, if at some point support asks for them separately, they are listed.
Collect a Fiddler Trace
Fiddler is a tool for monitoring requests made and received by a web browser. This information is often invaluable when troubleshooting a problem with Activities. Due to the AJAX nature Activities, an error message may not always display the true cause of the error. A fiddler trace helps show all of the requests that were made, and any requests or responses that may have been made.
A fiddler trace may be required when there is an error performing an action that results in a request to the server – creating an Wiki, saving a page, adding a member to a Wiki.
Fiddler can be downloaded from http://www.fiddler2.com