Installing CR1 for HCL Connections 6.5

Install a Cumulative Refresh (CR) for HCL Connections 6.5.

Before you begin

On the system where the Deployment Manager is installed, prepare the supporting software for the update, Download and extract the CR1 update installation package Refer to Downloading the latest Cumulative Refresh (CR) and related updates for more information.

About this task

If you are updating a newly installed or migrated deployment, you only need to update with the newest Cumulative Refresh, because it contains all of the updates from previous refreshes.


  1. Update databases for Connections as explained in Updating HCL Connections databases for 6.5 CR1.
  2. Stop all clusters and node agents in your deployment but leave the Deployment Manager running.
  3. Start Installation Manager.
  4. From the Installation Manager menu, click File > Preferences.
    Note: Be sure that the Search service repositories during installation and updates option is deselected.
  5. Click Repositories > Add Repository.
  6. Enter the full path to the Cumulative Refresh package that you downloaded and then click OK.

    For example: C:\HCL\CONNECTIONS-CR\HC6.5_CR1\Updates\repository.config.

    Verify that Installation Manager can connect to the repository.
  7. Click OK.
  8. Click Update.
  9. Select Connections 6.5 and click Next.
  10. Verify that the correct Cumulative Refresh version is displayed and click Next.
  11. Review and accept the license agreement by clicking I accept terms in the license agreements and then click Next.
  12. Ensure that all the Connections applications are selected and click Next.
    Note: All of the installed applications are selected by default. If you add any of the non-selected applications, those applications will be installed. If you clear any of the selected applications, those applications will be uninstalled.
  13. Enter the administrative ID and password of the Deployment Manager and click Validate.
    Note: This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following Java™ EE roles: dsx-admin, widget-admin, and search-admin. It is also used by the service integration bus. If you plan to use security management software such as Tivoli® Access Manager or SiteMinder, the ID that you specify here must exist in the LDAP directory. For more information, see the Switching to unique administrator IDs for system level communication topic.
  14. Click OK > Next > Update > Finish.
  15. Close Installation Manager.
  16. When the installation is complete, start the node agent to deploy the updated Connections applications.
  17. Stop the node agent so the temp directory can be cleaned out in the next step.
  18. Delete the contents of the cache under the App Server (for example, C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp).
  19. Start the node agents, then perform a full synchronization to push the update to all nodes.

    Check the SystemOut.log of each nodeagent to ensure synchronization completed successfully.

  20. Post Installation Task - End users may experience issues such as the Community Catalog not correctly displaying after a Connections CR deployment. This can be prevented by following the instructions in the Article, Refreshing the browser cache for the end users after Connections 6.5 Cx deployment.
  21. Start the Connections server


Your Connections deployment has been updated. To check the logs, go to the connections_root/logs directory and open the applicationUpdate.log file, where application is the name of an Connections application. If you added new applications, check the applicationInstall.log file as well.

Note: If your deployment includes Component Pack, complete the steps in Upgrading Component Pack Services.