Troubleshooting Libraries Setup

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

Table 1. Potential problems with libraries and suggested solutions

This table shows possible issues that might occur with Libraries and provides ways to work around the problem.
Problem Solution

Problems using ACCE (Administration Console for Content Platform Engine).

ACCE does not support Firefox 3.5/3.6.

ACCE tested with: Firefox ESR 10, IE 9 and Safari 5.1.

When you log on to ACCE (Administration Console for Content Platform Engine) you encounter an error message and you see something similar to the following in the p8_server_error.log in ${USER_INSTALL_ROOT}\FileNet/<your_server_name>/p8_server_error.log; where <your_server_name> is the name of the server that hosts the Content Platform Engine application:

Caused by: com.ibm.connections.directory.services.exception.DSOutOfServiceException: CLFRK0004E: Directory Service Extension(DSX) received a HTTP response from URL 'https://conwas.dyn.webahead.ibm.com:9444/communities/dsx/membership.do?idKey=d964f35d-0183-4363-b566-94d94b41d4ad&role=3' with unexpected content-type 'text/html;charset=UTF-8'!
Check that the SSO domain name is set correctly for both the Connections and FileNet servers.
  1. Log in to the WebSphere Application Server Integrated Solutions Console and navigate to: Security > Global security > Web and SIP security > Single sign-on (SSO)
  2. Adjust the Domain name field. For example for the two servers connections.example.com and filenet.example.com, you would set the domain name to: .example.com.

Cannot add Library widget to a community and you see a message similar to the following in <profile_root>/log/<server>/SystemErr.log:

addWidgetActi E com.ibm.lconn.widgets.actions.AddWidgetAction execute CLFWZ0004E: Event 'widget.added' sent to remote lifecycle handler at https://<filenet_server>:<port>/dm/atom/communities/feed returned bad response: 501 - Not Implemented

The problem might be caused by incorrect input of Object store symbolic name during the rebuild and redeployment of FNCS. Rerun the Use automate tool to configure Libraries process and ensure that all inputs are correct.

CCM installation fails because realm name is not expected value.
  1. Log in to DM WebSphere Application Server Integrated Solutions Console.
  2. Navigate to: Security > Global security > Available realm definitions for federated repositories > configure .
  3. Set realm name to defaultWIMFileBasedRealm.
  4. Click OK and Save.
  5. Synchronize nodes.
  6. Restart all servers.
Note: The realm name might be changed back after the installation. This might break single sign-on temporarily with other applications. If you are installing with an existing FileNet, make sure the realm names match in the directory configuration.
After IBM Connections installation completes, the FileNet p8_server_error.log shows the following message and error:
2013-03-09T09:59:34.937 B0EFEFF7 GCD  FNRCE0000I - INFO Creating P8 Domain 'ICDomain' ...
Then the Creating P8 Domain activity does not complete and the following error message appears:
FNRCE0000E - ERROR The P8 domain does not exist. Create the P8 Domain and retry the request.
The error message is logged because installation has finished but you have not run the createGCD script yet.

You can continue the post-installation steps and ignore this error message in FileNet p8_server_error.log.
If you do not see FileNet events in the Connections ActivityStream you might have misconfigured FileNet to be an Activity Stream producer. When configuring FileNet to be an Activity Stream producer, make sure to set the Activity Stream Retrieval URL exactly as shown: {ecm_files}.
Note: If you enter an incorrect value in this field, events appear in the Activity Stream but the Embedded Experience does not load. In the Embedded Experience pop-up, users see the following error message: An error occurred retrieving the current user. Please try again. In the More Details message box, the following text is shown: 
{"error":{"code":"unknown","message":"unknown"},"request":{"handleAs":"text","url":"...

The URL that follows is also broken.

 Make sure {ecm_files} includes the braces {}.
If you do not see FileNet events in the Activity Stream you may have misconfigured FileNet to be an Activity Stream producer. An HTTP 500 error is received when trying to access a library anonymously in CCM. You access libraries anonymously by connecting to the library without logging on in either Connections or in the Desktop Plugin. You also see SECURITY_ANONYMOUS_DISALLOWED when viewing the FileNet status page at http://<server-host>/dm/.
Note: Do not enable anonymous access when external users are enabled and used.
 Configure CCM for anonymous access, for more information see Managing anonymous access for a FileNet deployment.
Failed in deploy Navigator/FNCS ear by configmgr tool. Error message:
ADMA5014E: The installation of application navigator failed.
WASX7017E: Exception received while running file "C:\IBM\Connections\addons\ccm\FNCS\configure\tmp/deployapplication.tcl"; exception information:
com.ibm.ws.scripting.ScriptingException: 
WASX7132E: Application install for C:\IBM\Connections\addons\ccm\FNCS\configure\deploy\navigatorEAR.ear failed: see previous messages for details.
Note: The path might be C:\IBM\Connections\FileNet\ContentEngine\FNCS...
Check the error in getTMInfor.log: 
WASX7209I: Connected to process "dmgr" on node BXV5V621CellManager01 using SOAP connector; The type of process is: DeploymentManager 
WASX7017E: Exception received while running file "C:\IBM\Connections\addons\ccm\FNCS\configure\tmp\getTMInfo.tcl"; exception information: com.ibm.ws.scripting.ScriptingException: 
WASX7077E: Incomplete config id: need closing parenthesis in ""
 Check the properties in Profile Properties in configmgr tool. For example, the Cell name is case sensitive. The wrong cell name causes the failure even if it gets success when clicking Test Connection.