MustGather: Lotus Connections Profiles 3.0

Collecting Data for problems with Lotus Connections Profiles 3.0 Component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.

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, LDAP type and version, SSO?, Proxy?)

3. Systemout.log and systemerr.log located in %WAS_HOME%\profiles\(your profile)\logs\<connections_server> is the primary logging file for the Lotus Connections Profiles 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. Collect the following files:
LotusConnections-config.xml
Directory-profile.xml
wimconfig.xml
profiles-policy.xml

located in directory %WAS_HOME%\profiles\(your profile)\config\cells\(your cell)\LotusConnections-config stores properties that control common Lotus Connections features,

5. Notifications-config.xml located in %WAS_HOME%\profiles\(your profile)\config\cells\(your cell)\LotusConnections-config directory stores properties that control e-mail notifications across all of the features. This is a file to collect if e-mail notifications are not working in one or more components.

6. Proxy-config.xml located in %WAS_HOME%\profiles\(your profile)\config\cells\(your cell)\LotusConnections-config directory defines proxy server redirects for specific URL patterns. Using redirects, you can allow connections to web sites that you deem to be safe or block
connections to Web sites that you deem to be dangerous. This configuration file also defines also defines rewrite rules that specify aliases for Web addresses.

7. Proxy-profiles-config.xml located in %WAS_HOME%\profiles\(your profile)\config\cells\(your cell)\LotusConnections-config directory
defines proxy server redirects that apply to the Profiles page specifically and supersede the redirects defined in the proxy-config.xml file.

8. Profiles-config.xml located in %WAS_HOME%\profiles\(your profile)\config\cells\(your cell)\LotusConnections-config directory stores properties that control the behavior of the Profiles feature.

9. TDI related files
map_dbrepos_to_source.properties
map_dbrepos_from_source.properties
profiles_tdi.xml
profiles_tdi.properties
located under directoryC:\IBM\TDI\V7.0\TDISOL\TDI

10. TDI logs
ibmdi.log
populateDBfromDNfile.log
ProcessTDSChanges.log
ProcessADChanges.log
MonitorDraftUpdates.log
Collect.dns located under directory %TDI_HOME%\V7.0\TDISOL\TDI

11. lcwizard_0.log
located under, example directory
$(userhome)/lcwizard/log/lcwizard_0.log

Historical logs saved as lcwizard_n.log

12 .ffdc logs. located under directory
%WAS_HOME%\Profiles\AppSrv01\logs\ffdc
zip up all logs

Profiles Tracing:

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:

*=info:com.ibm.lconn.*=finest:com.ibm.connections.*=
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:com.ibm.
peoplepages.internal.service.*=finest:com
.ibm.lconn.profiles.internal.service.*=finest:com.ibm.
connections.directory.services.*=all

3. Shut down the WAS Server and move to another directory (or delete) Systemout.log and systemerr.log 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 along with configuration Files to Collect section above.

Refer to the detailed instructions in the Technote "Exchanging information with IBM Technical Support for problem determination" to make the information available and to update your problem record:

Title: Exchanging information with IBM Technical Support for problem determination
Doc #: 1201571
URL: http://www.ibm.com/support/docview.wss?rs=899&uid=swg21201571

For tdi population issues please add the following trace:
Please enable all of the following in the tdi/profiles_tdi.properties
source_ldap_debug=true
tds_changelog_debug=true
sync_updates_clean_temp_files= false

In the Wizards\TDIPopulation\TDISOL\win\etc\log4j.properties directory:
look for
log4j.rootCategory=INFO, Default

change it to
log4j.rootCategory=DEBUG, Default