Installing The Bcc Patch On A Fully Patched Oes 2 Sp1 Linux Bcc Cluster; Installing The Bcc Patch Along With The Oes 2 Sp1 Linux Patches; Chapter 9, "Configuring The Identity Manager Drivers For Bcc," On - Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual

6.2 Installing the BCC Patch on a Fully Patched
OES 2 SP1 Linux BCC Cluster
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.
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:
2a (Optional) On one of the nodes in the cluster, migrate its cluster resources to another node
in the cluster.
2b 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.
2c If you migrated cluster resources in
2d Repeat
3 Repeat
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
page
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.
6.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.
62 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
Step 2a through Step 2c
Step 2 on one peer cluster at a time until the BCC 1.2.0 patch has been applied to each

Chapter 9, "Configuring the Identity Manager Drivers for BCC," on

71.
Step 2a, migrate them back to the updated node.
for the remaining nodes in the cluster.