Installing CR3 for IBM Connections 5.5

Use IBM® Installation Manager to install Cumulative Refresh 3 (CR3) for IBM Connections 5.5.

Before you begin

Take the following steps on the system where the Deployment Manager is installed:

  • Download and extract the CR3 package (5.5.0.0-IC-Multi-CR03-LO90858). For more information, see Downloading the latest Cumulative Refresh (CR) and related updates.
  • Verify that you are running IBM Installation Manager 1.8.4 or later.
  • Verify that WebSphere® Application Server 8.5.5.9 or later is installed and that you updated IBM HTTP Server 8.5 and web server plug-ins for IBM WebSphere Application Server 8.5.
  • Restart the Deployment Manager and start the HTTP services: IBM HTTP Administration for WebSphere Application Server V8.5 and IBM HTTP Server V8.5.

About this task

To install the Cumulative Refresh, complete the following steps:

Procedure

  1. Stop all clusters and node agents in your deployment but leave the Deployment Manager running.
  2. From the IBM Installation Manager menu, click File > Preferences.
    Note: Be sure that the Search service repositories during installation and updates option is cleared.
  3. Click Repositories > Add Repository.
  4. Enter the full path to the Cumulative Refresh package that you downloaded and then click OK.

    For example: C:\IBM\CONNECTIONS-CR3\IC-CR3\5.5.0.0-IC-Multi-CR03-LO90858\Updates\repository.config

    The IBM Installation Manager indicates whether it can connect to the repository.
  5. Click OK.
  6. Click Update.
  7. Select IBM Connections and click Next.
  8. Verify that the correct Cumulative Refresh version is displayed and click Next.
  9. Review and accept the license agreement by clicking I accept terms in the license agreements and then click Next.
  10. Ensure that all the IBM 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 are also installed. If you clear any of the selected applications, those applications are uninstalled.
  11. 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.
  12. Click OK > Next > Update > Finish.
  13. Close Installation Manager.
  14. There are changes to the Rich Content widget in IBM Connections Communities that require the creation of a new cluster level Dynacache instance. For more information on the manual steps to create the dynacache, see technote 2001580 .
  15. Delete the contents of the cache under the App Server C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp
  16. Start node agents, then perform a full synchronization to push the update to all nodes. Check the SystemOut.log of each node agent to ensure synchronization completes successfully.
  17. Start the cluster.

Results

Your IBM Connections deployment is updated. Check for updated version in the following locations:

  • Check version.txt in C:\IBM\Connections.
  • Check application.component and application.product in C:\IBM\Connections\version.

What to do next

Complete all of the Post-update tasks that are relevant to your deployment in the sequence they are listed.