Troubleshooting Connections Content Manager (CCM)
If you experience problems when you 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 Connections 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 Connections Communities.
- 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.
- For status about FileNet Collaboration Services, check the status page at http://<hostname>/dm/.
- For status about FileNet Content Engine, check the status page at http://<hostname>/FileNet/Engine.
- For status about FileNet Content Engine Domain and Object Store, check the status page at http://<hostname>/P8CE/Health
- For status about FileNet Content Engine Domain and Object Store Upgrade, check the status page at http://<hostname>/FileNet/AutomaticUpgradeStatus
- For status about FileNet Collaboration Services seedlist URL, check the status page at http://<hostname>/dm/atom/seedlist/myserver
- You 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://<hostname>/acce