MustGather: Lotus Connections Activities 3.0

Technote (FAQ)


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\ (or .tar if unix/linux)

Alternatively, For more information about automating data collection, download the ISA lite for LC:

New Tech note to come
Title: Download IBM Support Assistant (ISA) Lite for Lotus Connections
Doc #: 4025198

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


In some troubleshooting scenarios support may instruct to enable tracing and provide a tracing data set for analysis. The following are instructions on how to implement Lotus Communities 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 Activities is installed on) -> Diagnostic Trace Server -> Change Log Detail Levels -> please add the following *string and click Apply -> OK oc/info/ae/ae/ttrb_trcover.html

Activities specific trace strings.*=all

(traces Activities interaction with the directory)*=all

(traces Activities service layer)

com.ibatis=finest: com.ibatis.common.jdbc.SimpleDataSource=finest: com.ibatis.common.jdbc.ScriptRunner=finest: com.ibatis.sqlmap.engine.impl.SqlMapClientDelegate=finest: java.sql.Connection=finest: java.sql.Statement=finest: java.sql.PreparedStatement=finest: java.sql.ResultSet=finest:

(traces Activities interaction with the database)*=all

(traces Activities interaction with the event infrastructure)*=all

(traces Activities interaction with the notification infrastructure)

Database tracing (very verbose)

**Note:** The DB trace settings are very verbose and are only really useful if you can limit server activity to reproducing a problem.

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.

**Note:** By default, when Activities is installed in a deployment that also has Profiles, user information is retrieved from Activities from Profiles. In such a deployment, if Profiles is unavailable, Activities will not function properly. Before reporting an issue with Activities where users cannot access Activities, customers should ensure that Profiles is available

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

Document information

More support for:

IBM Connections

Software version:


Operating system(s):

AIX, Linux, Windows

Reference #:


Modified date:


Translate my page

Content navigation