+

Search Tips   |   Advanced Search

Install a fix pack in console mode


Overview

Use console mode to install a fix pack to update IBM Connections.

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.

(AIX and Linux) 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.

Run Installation Manager on the system where the dmgr is installed.

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 a fix pack in console mode

  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. Run...

      cd IM_root/eclipse/tools directory.
      ./imcl.sh -c

  4. In the console window:

    1. Choose P to edit preferences.

    2. Choose 1. Repositories.

    3. Choose D. Add Repository.

    4. Specify the fix pack repository location you have downloaded, such as...

        /opt/shared_disk/Connections/repository.config

    5. Choose A to apply these changes, and then return to the main menu.

  5. In the console main menu, choose Update and then select IBM Connections as the package group to update.

  6. Ensure all the applications are selected and enter N to proceed.

    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.

  7. Enter the administrative ID and password of the Deployment Manager.

    This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following Java EE roles:

    • dsx-admin
    • widget-admin
    • search-admin ,/ul>

      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 topic.

    • Configure the Connections Content Manager deployment option. This panel displays if you chose to install the Connections Content Manager feature while installing the fix pack.

      1. Select 1 to use a new FileNet deployment for Connections Content Manager.

      2. Enter the FileNet installer packages location. The three FileNet installers:

        • Content Platform Engine
        • FileNet Collaboration Services
        • Content Platform Engine Client

        ...need to be placed into the same folder. Press Enter to validate whether the correct installers could be found.

      3. Select 2 to use an existing FileNet deployment for Connections Content Manager.

      4. Enter the User Id for the FileNet Object Store administrator username.

      5. Enter a password for the FileNet Object Store administrator password.

      6. Enter the HTTP URL for the FileNet Collaboration Services server:

          http://fncs.myco.com:80/dm

      7. Enter the HTTPS URL for the FileNet Collaboration Services serve such as:

          https://fncs.myco.com:443/dm.

      8. Press Enter to validate.

      9. We can continue even if the validation failed. If we are sure the correct information has been entered, then it might be the FileNet server is not available. type N to continue; otherwise please type B to reenter the information.

    • Configure the topology.

      The panel described in this step appears only if you selected new applications to install.

      The Connections Content Manager applications do not display if you have chosen to use an existing FileNet deployment.

      • Small deployment:

        1. Type 1 to select the Small deployment topology.

        2. Enter a Cluster name for the topology.

        3. Select a Node.

        4. Enter a Server member name for the node.

        5. Type N to proceed.

      • Medium deployment:

        1. Type 2 to 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. The topology specified is displayed.

          To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.

        6. Type N to proceed.

      • Large deployment:

        1. Type 3 to 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. The topology specified is displayed.

          To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.

        6. Type N to proceed.

    • Specify the Cognos configuration :

      The IBM Cognos configuration panel appears only if you chose to install the Metrics application earlier in this task.

      1. Select when to configure Cognos application:

      2. Enter the LDAP user ID for the Cognos administrator.

      3. Password for the Cognos administrator.

      4. Select the node where the Cognos BI Server is installed.

      5. Enter the web context root.

      6. Press Enter to validate the configuration. If validation failed, type B to reenter the information.

      7. Type N to proceed.

    • 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 do not display if you have chosen to use an existing FileNet deployment.

      1. Specify whether the installed applications use the same database server or instance: Type 1 to specify the applications use same database server or instance; type 2 to specify they use different database servers or instances.

        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: If installing on Windows, Linux, or AIX:

        • 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.

      5. Enter the JDBC driver location. For example:

        • AIX:

          /usr/IBM/WebSphere/AppServer/lib

        • Linux:

          /opt/IBM/WebSphere/AppServer/lib

        • Windows:

          C:\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 2 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, confirm the Use the same password for all applications question 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. If make changes, type the number that corresponds to the application to change. Alternatively, type R to reset all the database specifications to their default values.

      9. Press Enter 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.

      10. If the verification check is successful, type N to proceed. If verification fails, press B to reenter the required information.

    • Review the information entered. To revise your selections, press B. To install the update, press U.

    • 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