Installing IBM CMIS for CCM and HCL Docs integration

To integrate HCL Docs with CCM (Connections Content Manager), you must install IBM CMIS for FileNet Content Manager that ships with HCL Connections. Make sure you have installed HCL Connections 5.0 CR3 or Connections 5.5.

About this task

Currently, HCL Docs supports only CMIS 1.0.

Procedure

  1. Navigate to C:\IBM\Connections\addons\ccm\FNCS\configure(the path might vary depending on Connections versions and your HCL Connections installation path, for example, the path is C:\IBM\Connections\FNCS\configure for Connections 5.5). Run configmgr. The IBM Content Navigator Configuration and Deployment Tool opens.
    create a new deployment
  2. Click File > New Deployment.
  3. Type FNCMIS for the new deployment name, and then click Next.
    Type Profile name
  4. Select Websphere Application Sserver, and click Next.
    image03
  5. Specify the Application Server values:
    1. Select Application server version 8.5.
    2. Change the Installation directory according to your environment, and then the profile path will automatically change. For example, the installation directory is /opt/IBM/WebSphere/AppServer and the Profile path is /opt/IBM/WebSphere/AppServer/profiles/AppSrv01.
    3. Type wasadmin in the Administrator user name field and then type the password.
    4. Type 8879 for SOAP connector port.
    5. Set the Host name and select the proper cell for the deployment.
    6. Click Test Connection to see if you can connect to the WebSphere Application Server.
      Select IBM CMIS for FileNet Content Manager
  6. After the Successfully connected to the application server message displays, click Next.
  7. Select IBM CMIS for FileNet Content Manager, and then click Next.
    image05
  8. Click Advanced. And then click Yes to continue.
    image06
  9. On the first panel, type your server name and port for the Content Engine. If you use the IBM HTTP Server you can use port 80. Otherwise use a WebSphere port such as 9081. Then click Test Content Engine Connection.
    update the FileNet P8 Client Connector Files
  10. A message displays that you are connected to your Content Engine server. Click OK.
  11. Click the Save button and then the Run Task button.
    run task
  12. When you see the message that the task has run successfully, double-click the next item in the navigation panel.
    task running successful
  13. On the Configure the Connections to Your LDAP Server item, right-click, and disable it. It will then be displayed in italics.
  14. Do the same for Import Your Content Engine LTPA Keys. Right-click and disable it.
  15. On the Configure the IBM CMIS Client Authentication Method item, select the authentication method. In most cases it is HTTP Basic Authentication. Click Save and then Run Task.
    configure the IBM CMIS Client Authentication method
  16. Configure IBM CMIS for FileNet Content Manager. Specify the host name, the port number and the IBM CMIS URL. There is no need to specify the FileNet P8 domain name.
    Configure IBM CMIS for FileNet Content Manager
    Note: If you are unsure about the Port Number, you can look it up in the WebSphere Administration interface by going to Servers > Application Server > YourConnectionsServer and at the Communications tab, open the Ports section. The port that you are looking for is BOOTSTRAP_ADDRESS.
  17. Click Save and then Run Task.
  18. Proceed to the Build the Web Application item. Keep the default values. Click Save and then Run Task.
  19. On the Deploy the Web Application panel, select Cluster as the deployment type. Rename the Web application fncmis, and select your cluster from the Application server cluster list.
  20. Click Save and then Run Task.
    deploy the web application
  21. When it is done, you see a message that all of the tasks were successfully completed.
    all tasks are completed
  22. Restart the deployment manager.
  23. Map the new application to the IBM HTTP Server. Click the WebSphere Administrator web interface and go to Applications > Application Types > WebSphere enterprise applications. Click the fncmis application
  24. Under Modules, click the Manage Modules link.
    manage modules
  25. Select the CMIS for IBM FileNet Content Manager check box, and then select the cluster and the web server. Click Apply.
    manage modules settings
  26. Click OK.
    click OK for settings of Manage Module
  27. Click Save.
    Save message
  28. If you have automatic synchronization enabled, it will now sync the changes to all nodes. Click OK. If not, you will need to start the synchronization manually.
    synchronize changes with nodes
  29. Generate the HTTP Server Plug-in and deploy and restart the webserver. Go to Servers > Server Types > Web servers.
  30. Select the webserver1 check box and click Generate Plug-in.
    web server
  31. Select the webserver1 check box again and click Propagate Plug-in.
  32. Select the webserver1 check box again and click Stop.
  33. Select the webserver1 check box again and click Start.
  34. Configure IBM CMIS for HCL Docs:
    1. On the server where CMIS is installed, locate the folder ${WAS_ROOT}\profiles\AppSrv01\installedApps\${CellName}\fncmis.ear\fncmis.war\WEB-INF\classes and find thecmis.properties file. Add or revise the following properties: 
      enableTeamspaceAwareness=true
      Note: Make sure the following properties are set: 
      cmisURI=http://${CMIS_SERVER}:${CMIS_PORT}
      Where:
      • ${CMIS_SERVER} is the server name of the FNCMIS service. Usually it is the IHS.
      • ${CMIS_PORT} is the port of FNCMIS server. It can be ignored if ${CMIS_SERVER} is an IHS server.
    2. Repeat step 34a for all nodes.
    3. Restart the cluster of FNCMIS.