24
Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
Selecting the
Identity Manager Templates for Windows iManager Servers
installs the templates
on the local Windows server. You must have iManager installed on the Windows server before
installing the templates. The templates add functionality to iManager so you can manage your
business continuity cluster. You will be asked to specify the path to Tomcat (a default path is
provided) on the Windows server later in the installation.
The Business Continuity Cluster component contains the core software engine files that make
up the Business Continuity Cluster product. The Business Continuity Cluster software must be
installed on all nodes in each cluster that will be part of a Business Continuity Cluster.
4
Do one of the following:
If you chose to install the IDM iManager templates on a NetWare server, specify the name
of the eDirectory tree and the fully distinguished name for the server where you want to
install the templates. Then click
Next
.
If you don’t know the fully distinguished name for the server, you can browse and select
it.
If you chose to install the IDM iManager templates on a Windows server, specify the path
to Tomcat (a default path is provided) on the server. Then click
Next
.
You must have iManager installed on the Windows server before installing the templates.
5
Continue through the Upgrade Reminder screen and then specify the name of the eDirectory
tree and the fully distinguished name for the cluster where you want to install the core software
files.
If you don’t know the fully distinguished name for the cluster, you can browse and select it.
6
Select the servers in the cluster where you want to install the core software files for the
Business Continuity Cluster product.
All servers currently in the cluster you specified are listed and are selected by default.
You can choose to automatically start Business Continuity Cluster software on each selected
node after the installation is complete. If Business Continuity Cluster software is not started
automatically after the installation, you can start it manually later by rebooting the cluster
server or by entering
LDBCC
at the server console.
7
Enter the name and password of an eDirectory user (or browse and select one) with sufficient
rights to manage your BCC. This name should be entered in eDirectory dot format. For
example, admin.servers.novell.
This user should have at least Read and Write rights to the All Attribute Rights property on the
Cluster object of the remote cluster.
8
Continue through the final installation screen and then restart the cluster nodes where IDM is
running and where you have upgraded
libc.nlm
.
Restarting the cluster nodes can be performed in a rolling fashion in which one server is
restarted while the other servers in the cluster continue running. Then another server is
restarted, and then another, until all servers in the cluster have been restarted.
This lets you keep your cluster up and running and lets your users continue to access the
network while cluster nodes are being restarted.
9
Repeat the above procedure for each cluster that will be part of the business continuity cluster.
Содержание BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION
Страница 4: ...novdocx en 11 December 2007...
Страница 10: ...10 Novell Business Continuity Clustering 1 1 for NetWare Administration Guide novdocx en 11 December 2007...
Страница 72: ...72 Novell Business Continuity Clustering 1 1 for NetWare Administration Guide novdocx en 11 December 2007...
Страница 86: ...86 Novell Business Continuity Clustering 1 1 for NetWare Administration Guide novdocx en 11 December 2007...