MustGather: Lotus Connections Bookmarks 3.0

Do you want to automate the collection of MustGather data?

Collecting the following 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
URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg24025198


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, steps to reproduce, browser version
and relevant environment setup (e.g. WAS/LC point releases,, SSO?, Proxy?)

Important Note: If an error message is displayed: a copy of the entire contents shown when the “show details” or “show error details” link is clicked (if the link is provided).

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 Bookmarks 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:

notification-config.xml
events-config.xml
proxy-config.xml


How to enable tracing manually:
If not using ISA Lite, support may instruct to enable tracing and provide a tracing data set for analysis. The following are instructions on how to implement Lotus Bookmarks Tracing:

1. Log on to the WebSphere Application Server (WAS) integrated solutions console using an administrator ID
2. Go to Troubleshooting -> Logs and Trace -> Logging and Tracing -> Server 1 (or server Bookmarks is installed on) -> Diagnostic Trace Server -> Change Log Detail Levels -> please add the following *string and click Apply -> OK

Tracing Strings:

General Bookmarks issue
com.ibm.bl.servlet.*=all: com.ibm.dogear.*=all: com.ibm.bl.data.*=all

Search
com.ibm.ilel.seedlist.retriever.connections.dogear.*=all: com.ibm.ilel.seedlist.retriever.connections.dogear.data.*=all: com.ibm.ilel.seedlist.retriever.connections.dogear.ibatis.*=all

LDAP
com.ibm.ws.security.*=all:com.ibm.websphere.wim.*=all:com.ibm.wsspi.wim.*=all:com.ibm.ws.wim.*=all

3. 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

4. Start the server and reproduce the problem.

5. 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.


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 Bookmarks. Due to the AJAX nature Bookmarks, 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 such as creating an bookmark. Fiddler can be downloaded from http://www.fiddler2.com . It must be installed on the system is accessing Lotus Connections.

Have the user log into connections. Run the fiddler application. Have the user perform the operation that is causing the error. When the action has been completed, save the results in fiddler by choosing “File”->”Save”->”All Sessions”.



NOTE: Fiddler will capture all browser traffic on the user's system. Users should be advised to close all other browser windows before opening fiddler. If the user does not close other browser windows, requests made in those browser windows will also be recorded by fiddler.