Use the procedure in this section to apply the BCC 1.2.1 patch to a fully patched OES 2 SP2 Linux cluster.
IMPORTANT:In this scenario, it is recommended, but not required, that you migrate the cluster resources to a different node before installing the BCC patch. The BCC installation process does not affect the cluster resources that are already in place. It is not necessary to reboot the server in order for the BCC code changes to be applied.
On the Identity Manager node in every peer cluster, save the BCC driver configuration information, then stop the BCC drivers.
If you have not already done so, update the Identity Manager node in each peer cluster 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.
On one peer cluster, use a rolling update approach to install the BCC 1.2.1 patch:
(Optional) On one of the nodes in the cluster, migrate its cluster resources to another node in the cluster.
Install the BCC 1.2.1 patch files on the node (where cluster resources are not running).
It is not necessary to reboot the server in order for the BCC code changes to be applied.
If you migrated cluster resources in Step 3.a, migrate them back to the updated node.
Repeat Step 3 on one peer cluster at a time until the BCC 1.2.1 patch has been applied to each node in every peer cluster in the business continuity cluster.
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, 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), 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.
Restart Tomcat by entering the following command at a terminal console prompt:
Verify that BCC is working as expected by checking the BCC connection and resource status with iManager on every peer cluster.