Use the procedure in this section to upgrade BCC 1.2.2 on a fully patched OES 2 SP3 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 one peer cluster, use a rolling upgrade approach to install the BCC software:
(Optional) On one of the nodes in the cluster, migrate its cluster resources to another node in the cluster.
Install the BCC software 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 1.a, migrate them back to the updated node.
Repeat Step 1 on one peer cluster at a time until the BCC software has been reinstalled on 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 Section 5.3, Upgrading to 64-Bit Identity Manager 3.6.1.
For information, see Section 8.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 SP2 nodes before upgrading to OES 2 SP3, and you did not change architectures from 32-bit to 64-bit.
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.