Troubleshooting Connections Content Manager (CCM)

If we experience problems when we are installing, configuring, or using IBM Connections Content Manager, use this information to help resolve the problem.

Diagnostic information from other Connections components and FileNet core logging can help in problem determination and troubleshooting. During library creation and when retrieving or modifying content, calls are made between Communities, Profiles, and FileNet, so problems with Profile or Community configuration can adversely affect access to Libraries and FileNet.

Refer to this technote for information on collecting diagnostic information from Communities.

For FileNet core logging, refer to the following logs:

• app_server_root/profiles/<profile-name>/FileNet/<server_name>/p8_server_error.log

• app_server_root/profiles/<profile-name>/FileNet/<server_name>/p8_server_trace.log

Refer to Collecting data for Content Platform Engine for complete information on collecting diagnostic information for FileNet core components.

FileNet Collaboration Services and FileNet Content Engine include the following configuration status pages that can be checked to gather information on the status of a deployment:

• For status about FileNet Collaboration Services, check the status page at http://host/dm/.

• For status about FileNet Content Engine, check the status page at http://host/FileNet/Engine.

• For status about FileNet Content Engine Domain and Object Store, check the status page at http://host/P8CE/Health

• For status about FileNet Content Engine Domain and Object Store Upgrade, check the status page at http://host/FileNet/AutomaticUpgradeStatus

• For status about FileNet Collaboration Services seedlist URL, check the status page at http://host/dm/atom/seedlist/myserver

• We can also use theFNCE ACCE tool to check whether FileNet Content Engine can authenticate using Connections, and inspect other data in case of errors:

  http://host/acce

• Troubleshooting Libraries Setup
  Review issues that might occur with Libraries and ways to work around the problem.

• Troubleshooting the ccmDomainTool
  Review possible issues that might occur when we run the ccmDomain tool and ways to work around the problem. These errors can appear in the command prompt window or the log file for debugging problems. There is also a logging capability to the ccmDomainTool. If we have ongoing troubleshooting issues, send the ccmDomainTool.log to IBM support

• Enable Waltz and Sonata traces
  We need to enable Waltz and Sonata on both the WAS and the FileNet server to see logs for these applications.

Parent topic:
Troubleshooting tips