5.4 Installing the BCC Patch Along With the OES 2 SP2 Linux Patches

Use the procedure in this section to apply the BCC patch along with the OES 2 SP2 Linux patches during a rolling update of the cluster nodes from OES 2 SP1 Linux to OES 2 SP2 Linux.

In this scenario, it is required that you migrate the cluster resources to a different node before installing the OES 2 SP2 Linux patches and the BCC patch. Although it is not necessary to reboot the server in order for the BCC changes to be applied, other OES 2 SP2 Linux patches might require the server to be rebooted.

  1. On the Identity Manager node in every peer cluster, save the BCC driver configuration information, then stop the BCC drivers.

  2. On one peer cluster, use a rolling update approach to update the server from OES 2 SP1 Linux to OES 2 SP2 Linux, apply the latest OES 2 SP2 Linux patches, and install the BCC 1.2.1 patch:

    1. On the Identity Manager node in the cluster:

      1. If you have not already done so, update the Identity Manager node to use Identity Manager 3.6.1, but do not restart or re-create the drivers at this time.

        For instructions, see Section 7.0, Upgrading the Identity Manager Nodes to Identity Manager 3.6.1.

        If you must rebuild the server to use a 64-bit platform, install OES 2 SP2 Linux on the server and apply the latest SP2 patches before you install Identity Manager 3.6.1, then skip Step 2.a.b below.

      2. Update the server to OES 2 SP2 Linux and apply the latest patches, then reboot the server if you are prompted to do so.

      3. Update iManager.

    2. On one of the nodes in the cluster, migrate its cluster resources to another node in the cluster.

    3. On the node, install the OES 2 SP2 Linux and apply the latest patches.

    4. If you are prompted to do so, reboot the updated node.

    5. Install the BCC 1.2.1 patch files on the node

      It is not necessary to reboot the server in order for the BCC code changes to be applied.

    6. Migrate the cluster resources back to the updated node.

    7. Repeat Step 2.b through Step 2.f for the remaining nodes in the cluster.

  3. Repeat Step 2 on one peer cluster at a time until the OES 2 SP2 Linux patches and the BCC 1.2.1 patch have been applied to each node in every peer cluster in the business continuity cluster.

  4. After all nodes in every peer cluster are updated, do one of the following for the BCC drivers for Identity Manager:

    • Delete and Re-Create BCC Drivers: On the Identity Manager node in every peer cluster, delete the old BCC drivers, then re-create the BCC drivers with the new BCC template.

      Choose this option if you upgraded from 32-bit Identity Manager 3.6 to 64-bit Identity Manager 3.6.1 in Step 2.a.a, or if you have not previously deleted and re-created the BCC drivers using the new template from the BCC 1.2.0 patch on OES 2 SP1 Linux.

      For information, see Section 9.0, Configuring the Identity Manager Drivers for BCC.

    • Restart the Existing BCC Drivers: In the Identity Manager node in every peer cluster, restart the BCC drivers with the new BCC template.

      Choose this option if you were already using Identity Manager 3.6.1 on the OES 2 SP1 Linux servers (that is, you skipped Step 2.a.a), and you deleted and re-created the BCC drivers with the new template from the BCC 1.2.0 patch on the OES 2 SP1 Linux servers.

  5. Restart Tomcat by entering the following command at a terminal console prompt:

    rcnovell-tomcat5 restart

  6. Verify that BCC is working as expected by checking the BCC connection and resource status with iManager on every peer cluster.