To set up the load script:

1. In ConsoleOne, browse to and select the Cluster object.

   If necessary, click View > Console View to display its contents.

2. Right-click the Volume Resource object (volume_SERVER), then click Properties > Load to display the default volume resource load script for the WebAccess Agent volume.

   The next step assumes that this is the first time you have edited the load script. If other GroupWise agents are already running from this volume, some of the modifications have already been made.

3. Make the following changes to the default load script:

   • Remove the trustmig command. It is not necessary to migrate trustees for the WebAccess Agent volume. Removing this line helps the load script to execute faster.

   • If you selected vol:\system on WebAccess Agent volume as the installation location (WebAccess Clustering Worksheet items 5 and 7), add a search add command to add the new vol:\system directory to the server search path.

     search add volume:\system
     

   • If you selected sys:\system on each node as the installation location (WebAccess Clustering Worksheet items 5 and 7) but you are storing the MTA startup file on the WebAccess Agent volume, add that location to the server search path.

   • If you marked No under Load WebAccess Agent and Its MTA in Protected Memory? (WebAccess Clustering Worksheet item 9), add the following abend recovery options:

     set auto restart after abend = 2
     set auto restart after abend delay time = 0
     set auto restart down timeout = 60
     set developer option = off
     

     These settings provide the best possible handling of GroupWise databases in the event that an abend should occur within the cluster.

   • Transfer the MTA load command from the grpwise.ncf file located in the vol:\system directory into the load script. Use Ctrl+C and Ctrl+V to copy and paste text into the load script page. Then delete or rename the grpwise.ncf file to avoid future confusion.

     load volume:\system\gwmta.nlm @domain.mta
     

   • Add a delay so that the MTA is fully loaded before the WebAccess Agent starts to load:

     load delay 
     delay 10
     

     The length of the delay varies from system to system; ten seconds is a good starting place.

   • Transfer the WebAccess Agent load command from the strtweb.ncf file located in the vol:\system directory into the load script. Use Ctrl+C and Ctrl+V to copy and paste text into the load script page.

     load volume:\system\gwinter.nlm 
          /ph=volume:\domain\wpgate\webac80a
          /user=username /PASSWORD=password
     

   • If you marked Yes under Load WebAccess Agent and Its MTA in Protected Memory? (WebAccess Clustering Worksheet item 9), add the address space parameter to the load commands to specify the protected address space where the WebAccess Agent and its MTA will run. Add a protection restart command for the address space name.

     load address space=addr_space_name
          volume:\system\gwmta.nlm @domain.mta
     load address space=addr_space_name
          volume:\system\gwinter.nlm 
          /ph=volume:\domain\wpgate\webac80a
          /user=username /password=password
     protection restart addr_space_name
     

   The result would look similar to the following example:

   

   NOTE:The set commands are needed only when the MTA and the WebAccess Agent are not running in protected memory. The address space parameters are needed in the load commands only when the MTA and the WebAccess Agent are running in protected memory.

   For another example of a load script, see TID 7006193: Running the GroupWise Agents in a Non-Protected Address Space on a NetWare Cluster in the Novell Knowledgebase.

4. Click Apply to save the load script.

5. If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect.

6. Continue with Modifying the Volume Resource Unload Script for the WebAccess Agent.

To set up the unload script:

1. In ConsoleOne, in the properties pages for the Volume Resource object (volume_SERVER), click Unload to display the default volume resource unload script.

   The next step assumes that this is the first time you have edited the unload script. If other GroupWise agents are already running from this volume, some of the modifications have already been made.

2. Make the following changes to the default unload script:

   • If you marked Yes under Load WebAccess Agent and Its MTA in Protected Memory? (WebAccess Clustering Worksheet item 9), add an unload address space command and an unload kill address space command to ensure that the address space is completely cleaned up.

     unload address space=addr_space_name
     unload kill address space=addr_space_name
     

     If your system seems to be trying to kill the address space before the WebAccess Agent and its MTA have been completely unloaded, resulting in the agents hanging in the unloading state, set a delay of several seconds before issuing the unload kill address space command to allow the WebAccess Agent and its MTA adequate time to unload completely. The length of the delay varies from system to system; ten seconds is a good starting place.

     unload address space=addr_space_name
     delay 10
     unload kill address space=addr_space_name
     

   • If you marked No under Load WebAccess Agent and Its MTA in Protected Memory? (WebAccess Clustering Worksheet items 9), create an unload command parallel to each load command that you placed in the load script.

     unload gwinter.nlm
     unload gwmta.nlm
     

   • Remove the trustmig command just like you did in the load script.

   The result would look similar to the following example:

   

3. Click Apply to save the unload script.

4. If necessary, click OK to confirm that you must offline and then online the volume resource in order for the changes to take effect.

5. Continue with Setting the Failover Path and Policies for the WebAccess Agent.

To modify the failover path and policies for the WebAccess Agent volume resource:

1. In ConsoleOne, in the properties pages for the Volume Resource object (volume_SERVER), click Nodes to display the default failover path for the WebAccess Agent volume resource.

   

2. Arrange the nodes in the cluster into the desired failover path for the WebAccess Agent volume (WebAccess Clustering Worksheet item 4).

3. Click Apply to save the failover path.

4. Click Policies to display the default start, failover, and failback policies.

   

   The default policy settings are often appropriate. By default, a volume resource:

   • Fails over automatically if the node it is running on fails

   • Starts automatically on the next node in its failover path

   • Continues running at its failover location, even after its most preferred node is again available

   If you are considering changing these defaults, see the section about failover and failback mode modes in the clustering documentation for your version of NetWare, as listed in Section 1.0, Introduction to GroupWise 8 and Novell Cluster Services on NetWare.

5. Click OK when you are finished editing the WebAccess Agent volume resource properties.

6. Continue with Installing and Configuring the WebAccess Agent in a Cluster.