Install a fix pack in interactive mode

Overview

Install a fix pack to update IBM Connections.

For AIX and Linux:

• Use the same operating system user account to install this fix pack that was used to install Connections 5.0. If that account is no longer available, recreate it with the same user name and password and use it to install the fix pack.

• If we installed IBM Connections 5.0 as a root user, we cannot install this fix pack as a non-root user.

Windows:

Use an operating system user account that is in the same Administrators group as the account that was used to install Connections 5.0.

If an error occurs during installation, Installation Manager cancels the installation and rolls back the installation files.

Installation errors are usually caused by environment problems such as insufficient disk space, privilege issues, or corruption of a WebSphere profile. If wer installation is cancelled:

1. Identify and resolve the error that caused the cancellation. After cancelling the installation, Installation Manager displays an error message with an error code. We can look up the error code in the Installation error messages topic or check the log files.

2. Start this task again.

Install the fix pack

1. Download and extract the latest fix pack.

2. Stop all clusters and node agents in the deployment but leave the Deployment Manager running.

3. From the DMGR IM_root directory, run the file to start the Installation Manager:
   ./launcher

4. From the Installation Manager menu, click...
   File | Preferences | Repositories | Add Repository

5. Enter the full path to the fix pack that you downloaded and then click OK.

   For example: C:\IBM\Connections\update\fixes\LC_version_Fixpack\repository.config

   The Installation Manager indicates if it can connect to the repository.

6. Click OK to save the new repository.

7. Click Update.

8. The package group panel appears. Click Next to continue.

9. Select the fix packs to install 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 all the applications are selected and click Next.

    All of the installed applications are selected by default. If add any of the non-selected applications, those applications will be installed. If we clear any of the selected applications, those applications will be uninstalled.

12. Enter the administrative ID and password of the dmgr.

    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. To use security management software such as Tivoli Access Manager or SiteMinder, the ID specified here must exist in the LDAP directory. See Switch to unique administrator IDs for system level communication.

13. Configure Connections Content Manager deployment option. This panel displays if you chose to install the Connections Content Manager feature.

    • Select Existing Deployment to use an existing FileNet deployment with Connections Content Manager:

      1. Enter the FileNet Object Store administrator username and password the next two URLs will point to:

      2. Enter the HTTP URL for the FileNet Collaboration Services server: http://fncs.myco.com:80/dm.

      3. Enter the HTTPS URL for the FileNet Collaboration Services serve such as: https://fncs.myco.com:443/dm.

    • Select New Deployment to install a new FileNet deployment to use with Connections Content Manager.

      1. Enter the FileNet installer packages location. The three FileNet installers: Content Platform Engine, FileNet Collaboration Services, and Content Platform Engine Client need to be placed into the same folder.

14. Configure your topology:
    • The panel described in this step appears only if you selected new applications to install.
    • The applications for Connections Content Manager will not be shown if you have chosen to use an existing FileNet deployment.
    • If we select an existing cluster on which to deploy applications, the nodes in that cluster are fixed and cannot be modified.

    • Small deployment:
      1. Select the Small deployment topology.
      2. Enter a Cluster name for the topology.
      3. Select a Node.
      4. Click Next.

    • Medium deployment:

      1. Select the Medium deployment topology.

      2. Select the default value or enter a Cluster name for each application or for groups of applications. For example, use Cluster1 for Activities, Communities, and Forums.

         Installation Manager creates servers and clusters when required.

      3. Select a Node for each cluster. Accept the predefined node or select a different node.

         These nodes host application server instances that serve Connections applications. We can assign multiple nodes to a cluster, where each node is a server member of that cluster.

      4. Enter a Server member name for the selected node.

         The name must be unique across all nodes in the deployment.

      5. Click Next.

    • Large deployment:

      1. Select the Large deployment topology.

      2. Enter a Cluster name for each application.

         Installation Manager creates servers and clusters when required.

      3. Select a Node for each cluster. Accept the predefined node or select a different node.

         These nodes host application server instances that serve Connections applications. We can assign multiple nodes to a cluster, where each node is a server member of that cluster.

      4. Enter a Server member name for the selected node.

         The name must be unique across all nodes in the deployment.

      5. Click Next.

15. Enter the database information.

    The panel described in this step appears only if you selected new applications to install and if the new applications require database configuration.

    The Connections Content Manager databases will not be shown if you have chosen to use an existing FileNet deployment.

    Database information for Global Configuration Data and Object Store must be set correctly or installation will fail.

    1. Specify whether the installed applications use the same database server or instance: Select Yes or No.

       If allowed by the database configuration, we can select multiple database instances as well as different database servers.

    2. Select a Database type from one of the following options:
       • IBM DB2 Universal Database
       • Oracle Enterprise Edition
       • Microsoft SQL Server Enterprise Edition

    3. Enter the Database server host name. For example: appserver.enterprise.myco.com

       If the installed applications use different database servers, enter the database host name for each application.

    4. Enter the Port number of the database server. The default values are: 50000 for DB2 , 1521 for Oracle, and 1433 for SQL Server.

       If wer installed applications use different database servers or instances, enter the port number for each database server or instance.

    5. Enter the JDBC driver location. For example:
       /opt/IBM/WebSphere/AppServer/lib

    6. Ensure the following JDBC driver libraries are present in the JDBC directory:

       DB2

       db2jcc4.jar and db2jcc_license_cu.jar

       Ensure the user account has the necessary permissions to access the DB2 JDBC files.

       Oracle

       ojdbc6.jar

       SQL Server

       Download the SQL Server JDBC 4 driver from the Microsoft website to a local directory, and enter that directory name in the JDBC driver library field.

       The directory must not contain the sqljdbc.jar file, only the sqljdbc4.jar file. Even though the data source is configured to use the sqljdbc4.jar file, an exception occurs if both files are present in the same directory.

    7. Enter the User ID and Password for each database. If each database uses the same user credentials, select the Use the same password for all applications check box and then enter the user ID and password for the first database in the list.

       If the database type is Oracle, we must connect to the database with the user ID used when we created the application database.

    8. Click Validate to verify the database settings. If the validation fails, check the database settings. When the validation succeeds, click Next.

       Installation Manager tests the database connection with the database values that you supplied. We can change the database configuration later in the WAS console.

       Usually we can continue even if the validation failed because we can change the database settings from WAS console afterwards. However, we cannot continue if you have entered incorrect information for the Connections Content Manager database, because there are database operations during installation. Incorrect database information will cause installation to fail. So use correct information for Connections Content Manager database.

16. Review the summary information. Click Back to change the information or click Update to install the selected fix packs.

17. When the installation is complete, restart the clusters and node agents and synchronize the nodes.

Results

Your IBM 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 a Connections application. If we added new applications, check the applicationInstall.log file as well.

Parent topic:
Install fix packs

Related:
Update 4.0 and 4.5 databases to 5.0
Switch to unique administrator IDs for system level communication
Download fixes
Installation error messages