Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual page 60

2a2 Update the server to OES 2 SP2 Linux and apply the latest patches, then reboot the
2a3 Update iManager.
2b On one of the nodes in the cluster, migrate its cluster resources to another node in the
cluster.
2c On the node, install the OES 2 SP2 Linux and apply the latest patches.
2d If you are prompted to do so, reboot the updated node.
2e Install the BCC 1.2.1 patch files on the node
It is not necessary to reboot the server in order for the BCC code changes to be applied.
2f Migrate the cluster resources back to the updated node.
2g Repeat
3 Repeat
1.2.1 patch have been applied to each 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:
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
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.
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.
60 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
If you must rebuild the server to use a 64-bit platform, install OES 2 SP2 Linux on
the server and apply the latest SP2 patches before you install Identity Manager 3.6.1,
then skip Step 2a2 below.
server if you are prompted to do so.
Step 2b through Step 2f
Step 2 on one peer cluster at a time until the OES 2 SP2 Linux patches and the BCC
Step 2a1, or if you have not previously deleted and re-created the BCC
Chapter 9, "Configuring the Identity Manager Drivers for BCC," on
71.
for the remaining nodes in the cluster.
Step 2a1), and you deleted and re-created the BCC