Upgrading to HCL Connections 7.0

Upgrading to HCL Connections 7.0.

Before you begin

Before you begin upgrading to a HCL Connections 7.0 deployment,

Download Connections 7.0 Server Update, including Component Pack, from the HCL License & Delivery Portal and review the following:

Note: Previous configurations for IBM FileNet and Metrics deployments will be retained in Connections 7.0 going forward.
Important: If you have previously installed ICXT then deselect the Feature Foundation check box when upgrading to Connections 7.0 and contact HCL Support to acquire the new ICXT upgrade package. After downloading the ICXT package follow the ICXT installation guidelines.
  • The HCL Connections 7.0 database wizard does not create the database for the Community Highlights / Connections Engagement Center (CEC) or Feature Foundation | Export entries to PDF and provides support for Tailored Experience. The Community Highlights database scripts are located in the folder - /Wizards/connections.sql/icec. The Feature Foundation database scripts are located in the folder - /Wizards/connections.sql/ic360. Refer to the procedure in this section to create the databases. You will need to manually run the SQL scripts that are provided with HCL Connections. See Creating databases for more information.
  • Required database update to Homepage: Deployments that upgrade from Connections 6.5 CR1 are required to manually run the Homepage database schema located in the folder: \Wizards\connections.sql\homepage\<backend>\upgrade-60CR4-70.sql.
  1. On the system where the Deployment Manager is installed, prepare the supporting software for the update:

About this task

The only supported migration strategy is a multi-stage process that requires setting up a new environment that mirrors production, upgrading and validating that environment, and migrating production data before routing client traffic to the new environment. Specifically, administrators will need to:
  • Set up a new production staging environment that mirrors the live production environment. Ensure that the environment is sized appropriately as this will be the new production deployment, and adjust resources as needed. Specifically, all product versions need to initially be the same as production.
  • Perform an in-place upgrade of the new production staging environment.
  • Implement any configuration changes and customizations.
  • Validate product functionality.
  • Take the live production deployment offline to migrate data during a scheduled maintenance window.
  • Migrate data to the new environment and perform any necessary database updates.
  • Evaluate data integrity in the new environment now that production data is migrated.
  • Complete any remaining post-migration tasks.
Refer to the Knowledege Article, Road map for Upgrading Connections for additional information.


  1. Stop all clusters and node agents in your deployment but leave the Deployment Manager running.
  2. Start Installation Manager.
  3. From the Installation Manager menu, click File > Preferences.
    Note: Be sure that the Search service repositories during installation and updates option is deselected.
  4. Click Repositories > Add Repository.
  5. Enter the full path to the Connections 7 install package that you downloaded and then click OK.
    Verify that Installation Manager can connect to the repository. For example: ..\HCL_Connections_Install\HCLConnections\repository.xml.
  6. Click OK.
  7. Click Update.
  8. Select HCL Connections and click Next.
  9. From the Update Packages screen select Version and click Next.
  10. Review and accept the license agreement by clicking I accept terms in the license agreements and then click Next.
  11. Ensure that all the Connections applications are selected and click Next.
    Note: All of the installed applications are selected by default. All of the installed applications are typically selected by default. If you clear any of the selected applications, those applications will be uninstalled. If there are any non-selected applications, and you select those applications, they will be installed.
  12. 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.
  13. In the Topology panel, select the topology that matches the deployment
  14. Validate the Feature Foundation database
  15. Click OK > Next > Update > Finish.
  16. Close Installation Manager.
  17. When the installation is complete, start the node agent to deploy the updated Connections applications.
  18. Generate a new plug-in (to include the new Highlights app) by completing the following steps.
    1. Still in the Integrated Solutions Console, click Servers > Server Types > Webservers.
    2. Select the Webserver, click Generate Plug-in, and wait for the plug-in to be generated.
    3. Select the Webserver again and click Propagate Plug-in.
  19. Stop the node agent so the temp directory can be cleaned out in the next step.
  20. Delete the contents of the cache under the App Server.
  21. 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.

  22. Start the Connections server.

What to do next

  • A Connections 7.0 upgrade deployment updates a number of web services and other artifacts that require an end user to clear the browser cache to get the updates.
  • Alternatively, you can allow user's browsers to load new web services and artifacts by updating the <versionStamp value="####"/> in the LotusConnections-config.xml so users will see the changes the next time they log in, without having to clear their web browser cache. See Post-customization step after a Connections 7.0 upgrade is deployed so users will receive changes the next time they log in without having to clear their web browser cache. If the browser cache is not updated problems such as the Community Catalog not displaying correctly may occur.