Installing The Bcc Patch Along With The Oes 2 Sp2 Linux Patches - Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual

3c If you migrated cluster resources in
3d Repeat Step 3a
4 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.
5 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
drivers using the new template from the BCC 1.2.0 patch on OES 2 SP1 Linux.
For information, see
page 71.
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
drivers with the new template from the BCC 1.2.0 patch on the OES 2 SP1 Linux servers.
6 Restart Tomcat by entering the following command at a terminal console prompt:
rcnovell-tomcat5 restart
7 Verify that BCC is working as expected by checking the BCC connection and resource status
with iManager on every peer cluster.
5.4 Installing the BCC Patch Along With the OES
2 SP2 Linux Patches
Use the procedure in this section to apply the BCC patch along with the OES 2 SP2 Linux patches
during a rolling update of the cluster nodes from OES 2 SP1 Linux to OES 2 SP2 Linux.
In this scenario, it is required that you migrate the cluster resources to a different node before
installing the OES 2 SP2 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 SP2 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 update the server from OES 2 SP1 Linux
to OES 2 SP2 Linux, apply the latest OES 2 SP2 Linux patches, and install the BCC 1.2.1
patch:
2a On the Identity Manager node in the cluster:
2a1 If you have not already done so, update the Identity Manager node to use Identity
Manager 3.6.1, but do not restart or re-create the drivers at this time.
For instructions, see
Manager 3.6.1," on page
Step
through Step 3c for the remaining nodes in the cluster.
Step 2, or if you have not previously deleted and re-created the BCC
Chapter 9, "Configuring the Identity Manager Drivers for BCC," on
Step 2), and you deleted and re-created the BCC
Chapter 7, "Upgrading the Identity Manager Nodes to Identity
65.
3a, migrate them back to the updated node.
Updating (Patching) BCC 1.2.1 on OES 2 SP2 Linux 59