Upgrading a standard multi-server installation

You can upgrade an existing standard multi-server installation of IBM® Intelligent Operations Center to incorporate the latest updates. However, you cannot upgrade an existing installation on Linux to IBM Intelligent Operations Center V5.2.1. Instead, you must do a new installation of IBM Intelligent Operations Center V5.2.1 on an environment that is running Red Hat Enterprise Linux V7.6 or later. And, before migrating your data to your new installation of IBM Intelligent Operations Center V5.2.1, upgrade your existing environment to IBM Intelligent Operations Center V5.2.0.

Before you begin

  • Prepare your servers for the upgrade. For information, see Preparing the servers.

  • Provide the installation media and scripts to each server that hosts an IBM Intelligent Operations Center component. Follow the instructions in Extracting the installation media and scripts.

  • Back up the installation files that are in each server's installation directory at either /opt/IBM/ioc51install or /opt/IBM/ioc_install. On each server, enter the following commands as a root user. Depending on the version of IBM Intelligent Operations Center that you are upgrading from, the installation package file name might contain either a version number, or an underscore symbol (_), which is indicated by XXXX.
    mv  /opt/IBM/iocXXXXplatform.tar.gz  /opt/IBM/iocXXXXplatform.tar.gz.bak
mv  /opt/IBM/iocXXXXinstall  /opt/IBM/iocXXXXinstall.bak

  • If you are upgrading onto snapshots of virtual machines that are in a stopped state, see Starting the solution for information about starting servers and components before you do the upgrade.

  • If you want to install the optional Device Management Enablement component, ensure that you have the prerequisite products. You must have the following licenses:
    • WebSphere® MQ
      • For IBM Intelligent Operations Center V5.2.1, you must have the license for WebSphere MQ V9.1.0.1 for Linux on X86 64 Multilingual
      • For IBM Intelligent Operations Center V5.2.0, you must have the license for WebSphere MQ V8.0 for Linux on X86 64 Multilingual
    • IBM Integration Bus
      • For IBM Intelligent Operations Center V5.2.1, you must have the license for IBM Integration Bus V10.0.0.16 Linux x86-64 including Toolkit Multilingual
      • For IBM Intelligent Operations Center V5.2.0, you must have the license for IBM Integration Bus V10.0.0.3 Linux x86-64 including Toolkit Multilingual
    Also, ensure that the IBM Integration Bus installation files and the WebSphere MQ installation files are in the /installmedia/linux_x64 directory.

  • To use Device Management Enablement, you must also configure an LDAP user registry, and add the IBM Intelligent Operations Center users and groups to the registry. For more information, see Configuring an LDAP user registry.

About this task

Configure and install the four servers in the following order:
  1. Data server
  2. Web server
  3. Analytics server
  4. Application server
Note:
  • Complete steps 1-7 to configure each of the four servers before you begin step 8.
  • Wait for each installation script to complete before you start the installation steps on the next server.

Procedure

Configuring the servers

Note: Complete steps 1-7 on each server in turn, unless indicated otherwise.

  1. On the server that you are upgrading, copy the ioc_platform.tar.gz file from the interim fix package to the /opt/IBM installation directory.
    Note: Ensure that you have backed up the installation files from the previous IBM Intelligent Operations Center installation. See the Before you begin section.
    1. Open a terminal window and log on as the root user.
    2. Enter the following command to copy the ioc_platform.tar.gz installation file from the /installmedia directory to the base IBM Intelligent Operations Center installation directory: 
      cp /installmedia/ioc_platform.tar.gz /opt/IBM/
  2. Enter the following command to go to the /opt/IBM installation directory: 
    cd /opt/IBM
  3. Enter the following command to extract the ioc_platform.tar.gz file to the /opt/IBM directory: 
    tar -zxvf ioc_platform.tar.gz
  4. Before you configure the installation properties file, enter the following commands to change from a root user to the ioc_installer user that was used during the previous installation, and go to the installation directory: 
    su - ioc_installer
cd /opt/IBM/ioc_install/bin
    Note: To find the ioc_installer user, see the value of the ioc.install.user property in the installation properties file that was used for the previous installation.
  5. Configure the installation properties in the ioc.install.properties file:
    1. To edit the ioc.install.properties file, enter the following command: 
      sudo vi ../cfg/ioc.install.properties
    2. Configure each of the following installation server host name properties with the fully qualified host name of the corresponding server in the installation environment: 
      ana.server.hostname
app.server.hostname
db.server.hostname
ihs.server.hostname
ldap.hostname
      To obtain the fully qualified host name of a server, open a terminal window on the server and enter the following command: 
      hostname -f
    3. On the analytics server, the application server, and the web server, configure the values of the liberty.instance.name properties with the appropriate values for each server, as shown in the following table: For example, the default value used in previous installations is iocsvr1.
      Table 1. Values for liberty.instance.name properties on each server
      Server Property name Property value
      Analytics server liberty.instance.name Value for liberty.instance.name in the installation properties file from the previous analytics server installation
      liberty.instance.name.ana Value for liberty.instance.name in the installation properties file from the previous analytics server installation
      liberty.instance.name.app Value for liberty.instance.name in the installation properties file from the previous application server installation
      Application server liberty.instance.name Value for liberty.instance.name in the installation properties file from the previous application server installation
      liberty.instance.name.app Value for liberty.instance.name in the installation properties file from the previous application server installation
      liberty.instance.name.ana Value for liberty.instance.name in the installation properties file from the previous analytics server installation
      Web server liberty.instance.name.ana Value for liberty.instance.name in the installation properties file from the previous analytics server installation
      liberty.instance.name.app Value for liberty.instance.name in the installation properties file from the previous application server installation
  6. On only the data server, update the DB2® user ID and group ID properties in the installation properties file to match the user ID and group ID properties of existing DB2 users. The default DB2 instance user is db2i1own, and the default DB2 fence user is db2i1fnc.
    1. To find the user IDs of the DB2 instance and fence users, on the data server, enter the following commands as a root user: 
      id -u db2i1own
id -u db2i1fnc
    2. To find the group IDs of the DB2 instance and fence users, on the data server, enter the following commands as a root user: 
      id -g db2i1own
id -g db2i1fnc
    3. Configure the following properties in the ioc.install.properties file with the values that the previous commands returned: 
      db2.instance.uid = DB2_instance_user_ID
db2.instance.gid = DB2_instance_group_ID
db2.fence.uid = DB2_fence_user_ID
db2.fence.gid = DB2_fence_group_ID
  7. Required: Edit the password property values in the installation properties file to match the most recently updated password property values that are configured in the IBM Intelligent Operations Center installation that you are upgrading:
    • If you have not changed a password manually since you previously installed IBM Intelligent Operations Center, use the password value that is configured in the backup of the previous installation's installation properties file.
    • If you have changed a password manually since you previously installed IBM Intelligent Operations Center, for example, by using the Linux passwd command, use the password value from the manual change.
    Each password property name has the suffix .pwd.

Running the installation

Note: The preceding steps to configure the four servers must be completed before you begin step 8.

  1. On only the data server, run the following license script, read the license agreement, and enter Y to accept the agreement: 
    sudo ./ioc.accept.license.sh
  2. To run the installation script, choose one of the following options.
    Note: You must run the installation script on the servers in the order that is indicated in About this task.
    In the command, substitute a value for server_initials depending on the server that you are installing:
    • dat for the data server.
    • web for the web server.
    • ana for the analytics server.
    • app for the application server.
    • To install only IBM Intelligent Operations Center, enter the following command: 
      sudo ./ioc.server.install.sh -p 4.server_initials
    • To install IBM Intelligent Operations Center and the Device Management Enablement component, enter the following command: 
      sudo ./ioc.server.install.sh -p 4.server_initials.ioc.dme
      The script first installs IBM Intelligent Operations Center, and then the script installs Device Management Enablement.

What to do next

The installation log files are saved to the /tmp directory. To prevent the log files from being deleted by automated system maintenance tasks, copy the log files from the /tmp directory to another location.

The naming convention for the log files is:
ioc.install.short_host_name.yymmdd-hhmm_timestamp.three_random_alphanumeric_characters