Use IBM® Installation Manager to install Cumulative
Refresh 3 (CR3) on IBM Connections 5.0 CR2.
Before you begin
On the system where the Deployment Manager is installed, take the following actions:
- Download and extract the CR3 package (APAR LO84244). For more information, see Downloading
a Cumulative Refresh (CR).
- Verify that you are running IBM Installation Manager 1.8.0
or later.
- Verify that you installed WebSphere® Application
Server 8.5.5.4 (FP4) or later 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.
- For more information, see Update strategy for IBM Connections 5.0
About this task
To install the Cumulative Refresh, complete the following steps:
Procedure
- Stop all clusters and node agents in your deployment but leave the Deployment Manager
running.
- Go the directory where the zip file was downloaded
(C:\Install\CONNECTIONS-CR\IC-CR3) and unzip the file
5.0.0.0-IC-Multi-CR03-LO84244.zip into the same folder.
- From the IBM Installation Manager menu, click , then remove the existing repositories that were added for WebSphere Application
Server.
Note: Be sure that the Search service repositories during installation and
updates option is cleared.
- Click .
- Enter the full path to the Cumulative Refresh package that you downloaded and then click
OK.
For example:
C:\Install\CONNECTIONS-CR\IC-CR3\5.0.0.0-IC-Multi-CR03-LO84244\Updates\repository.config
The IBM Installation Manager indicates whether it
can connect to the repository.
- Click OK.
- Click Update.
- Select IBM Connections and click Next.
- Verify that the correct Cumulative Refresh version (Version 5.0.0.0_CR3)
is displayed and click Next.
- Review and accept the license agreement by clicking I accept terms in the license
agreements and then click Next.
- 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 installed. If you clear any of the selected applications, those
applications are uninstalled.
- 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.
- Click OK.
- Click Next.
- Click Update
- Click Finish.
- Close Installation Manager.
- When the installation is complete, restart the clusters and node agents and synchronize the
nodes. This action deploys the updated IBM Connections
applications.
Results
Your IBM Connections deployment is 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 IBM
Connections application. If you added new applications, check the
applicationInstall.log file as well.
What to do next
Complete all of the Post-update tasks that are relevant to your deployment in
the sequence they are listed.