Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION, Руководство администратора

Страница: 63 / 184

Updating (Patching) BCC 1.2.0 on OES 2 SP1 Linux 63
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
2 On one peer cluster, use a rolling update approach to install the BCC 1.2.0 patch:
2a On the Identity Manager node in the cluster, apply the OES 2 SP1 Linux patches, then
reboot the server if you are prompted to do so.
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 SP1 Linux patches.
2d On the node, install the BCC 1.2.0 patch.
2e If you are prompted to do so, reboot the updated node.
2f Migrate the cluster resources back to the updated node.
2g Repeat Step 2b through Step 2f for the remaining nodes in the cluster.
3 Repeat Step 2 on one peer cluster at a time until the OES 2 SP1 Linux patches and the BCC
1.2.0 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:
Š
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
Chapter 9, “Configuring the Identity Manager Drivers for BCC,” on
page 71 .
Š
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.