Use the procedure in this section to apply the BCC patch to a fully patched OES 2 SP1 Linux BCC cluster. 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.
On one peer cluster, use a rolling update approach to install the BCC 1.2.0 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.0 patch 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 2.a, migrate them back to the updated node.
Repeat Step 2 on one peer cluster at a time until the BCC 1.2.0 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:
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 9.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.
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.