5.3 Installing the BCC Patch Along With the OES 2 SP1 Linux Patches

Use the procedure in this section to apply the BCC patch along with the OES 2 SP1 Linux patches during a rolling upgrade of the cluster nodes. In this scenario, it is required that you migrate the cluster resources to a different node before installing the OES 2 SP1 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 SP1 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 install the BCC 1.2.0 patch:

    1. On the Identity Manager node in the cluster, apply the OES 2 SP1 Linux patches, then reboot the server if you are prompted to do so.

    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 SP1 Linux patches.

    4. On the node, install the BCC 1.2.0 patch.

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

    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 SP1 Linux patches and the BCC 1.2.0 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:

    • Re-Create BCC Drivers (Recommended): 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.

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

    • Use the Old BCC Drivers: On the Identity Manager node in every peer cluster, start the old BCC drivers. The new feature and bug fixes for the template will not be available.

  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.