You should have already reviewed Section 11.1, Planning Your Messenger System in a Cluster and filled out the Section 11.3, Messenger Clustering Worksheet and the Novell Messenger Worksheet
in the Novell Messenger 2.1 Installation Guide. Follow the instructions for the installation location you have chosen:
There are two methods of installing the Messenger agents to each node in the cluster:
Run the Messenger Installation program multiple times in order to install the agent software and to create the agent startup files on each node in the cluster.
Run the Messenger Installation program, then copy the Messenger agent software and startup files to each node in the cluster.
Use whichever method you prefer, following the steps provided in Starting the Messenger Installation Program
and Creating Your Messenger System
in Installing a Novell Messenger System
in the Novell Messenger 2.1 Installation Guide. Make each node in the cluster active to make sure that the Messenger agents start successfully.
Complete the following tasks to set up your Messenger system on a Messenger volume:
Cluster preparation for Messenger is the same as cluster preparation for GroupWise. Review Section 3.1, Preparing the Cluster for GroupWise before running the Messenger installation program.
The Messenger Installation program walks you through setting up your Messenger system and installing the Messenger agents.
If necessary, map a drive to the Messenger administration volume (Messenger Clustering Worksheet item 7).
Map a drive to the Messenger volume (Messenger Clustering Worksheet item 9).
The Messenger volume name will be cluster_volume. For assistance with mapping a drive to a cluster-enabled volume, see Configuring Short Name Resolution.
Run the Messenger Installation program at an administrator workstation to set up your Messenger system, following the steps provided in Starting the Messenger Installation Program
and Creating Your Messenger System
in Installing a Novell Messenger System
in the Novell Messenger 2.1 Installation Guide. Keep in mind the following cluster-specific details:
On the Start Copying Files page, the server object name should be the virtual server name, not a physical server name.
When you have finished creating your Messenger system, continue with Configuring the Messenger Volume Resource to Load and Unload the Messenger Agents.
The properties of the Volume Resource object define how the Messenger volume functions within the cluster, how the Messenger agents are loaded and unloaded, and how failover and failback situations are handled.
In ConsoleOne, browse to and select the Cluster object.
If necessary, click
to display its contents.Right-click the Volume Resource object (volume_SERVER), then click to display the default volume resource load script for the Messenger volume.
The volume resource load script executes whenever the Messenger volume comes online.
Add the following lines to the load script:
load volume:\novell\nm\ma\nmma.nlm @volume:novell\nm\ma\strtup.ma load volume:\novell\nm\aa\nmaa.nlm @volume:novell\nm\aa\strtup.aa
where volume is the name of the Messenger volume (Messenger Clustering Worksheet item 9).
For example:
load msgr:\novell\nm\ma\nmma.nlm @msgr:novell\nm\ma\strtup.ma load msgr:\novell\nm\aa\nmaa.nlm @msgr:novell\nm\aa\strtup.aa
As an alternative, you can start both Messenger agents with a single command:
volume:\novell\nm\nmstart.ncf
Click
to save the load script.Click
.Add the following lines to the unload script:
unload nmma.nlm unload nmaa.nlm
Click
to save the unload script.Click
to display the default failover path for the Messenger volume.Arrange the nodes in the cluster into the desired failover path for the Messenger volume (Messenger Clustering Worksheet item 10).
Click
to save the failover path.Click
to display the default start, failover, and failback policies.By default, a volume resource:
Fails over automatically if the node it is running on fails
Starts automatically on the net node in its failover path
Continues running at its failover location even after its most preferred node is again available
Change the policies if necessary, then click
.Continue with Copying LDAP and QuickFinder Files to the Messenger Volume.
During installation of the Messenger agents, some files were copied to sys:\system of the node where the Messenger volume was mounted. These files must be copied one time to the cluster volume that is hosting the Messenger agents.
From the node where the Messenger volume was mounted during installation, copy the following files to the cluster volume:
Table 11-2 LDAP and QuickFinder Files to Copy
Copy From: |
Copy To: |
---|---|
sys:\system\ldapsdk.nlm |
clustervol:\system\ma |
sys:\system\ldapssl.nlm |
clustervol:\system\ma |
sys:\system\ldapx.nlm |
clustervol:\system\ma |
sys:\system\qfind217.nlm |
clustervol:\system\aa |
If you are running in a language other than English, copy the following files from the appropriate numbered language subdirectory on the NetWare server to the cluster volume:
Table 11-3 Language-Specific Files to Copy
Copy From: |
Copy To: |
---|---|
sys:\system\nls\language_code\nmma.msg |
clustervol:\system\ma |
sys:\system\nls\language_code\nmaa.msg |
clustervol:\system\aa |
Continue with Testing Your Clustered Messenger System.
After you have configured the Messenger volume resource, you can test the load and unload scripts by bringing the Messenger volume online and taking it offline again.
In ConsoleOne, select the Cluster object, then click
.The new Messenger volume resource shows
in the column.Click the new Messenger volume resource, then click
.The
column for the volume resource now displays .Observe the server console where the Messenger agents are loading to see that they start and run correctly.
Click the new Messenger volume resource, then click
.The
column for the volume resource returns to .Observe the server console where the Messenger agents are unloading to see that they shut down correctly.
Repeat Step 2 whenever you are ready to bring the new Messenger volume resource online permanently.
On NetWare 6.5, these actions can also be performed from your Web browser. See Using Novell Remote Manager on NetWare 6.5.