You should already have reviewed Planning GroupWise in a Microsoft Cluster and filled out the WebAccess Clustering Worksheet. You are now ready to complete the following tasks to set up the WebAccess Agent in a clustering environment:
Create the WebAccess resource group and agent services resources (WebAccess Clustering Worksheet item 1), as planned in Planning the WebAccess Resource Group.
To ensure successful short name resolution, add entries for the WebAccess Agent network name to support your preferred methods of short name resolution, as described in Configuring Short Name Resolution.
Continue with Creating a Domain for the WebAccess Agent.
The WebAccess Agent domain will be a secondary domain. To create it, follow the instructions in Creating a New Secondary Domain in a Cluster, taking your information from the WebAccess Clustering Worksheet, rather than the System Clustering Worksheet, then return to this point.
Do not create any post offices in the WebAccess Agent domain.
Continue with Installing the MTA for the WebAccess Agent Domain.
The MTA for the WebAccess Agent domain can be installed just like any other MTA in your clustered GroupWise system. Follow the instructions in Installing the Agent Software in a Cluster, then return to this point.
You do not need to edit the MTA startup file.
Continue with Installing the WebAccess Agent in a Cluster.
After you have created a domain for the WebAccess Agent and installed the MTA for that domain, you are ready to install and configure the WebAccess Agent. The WebAccess Agent is the component of your WebAccess installation that accesses post offices and libraries to retrieve information for WebAccess client users.
Map a drive to the shared disk of the WebAccess resource group (WebAccess Clustering Worksheet item 1).
Map a drive to c:\ on the first node in the cluster where you will set up the WebAccess Agent as a Windows service (System Clustering Worksheet item 2).
If you plan to install the WebAccess Agent software to the shared disk of the WebAccess resource group (WebAccess Clustering Worksheet item 5), create the drive:\grpwise\webacc directory on the WebAccess shared disk accessed in Step 1.
or
If you plan to install the WebAccess Agent software to each node in the cluster, create the c:\grpwise\webacc directory on the drive accessed in Step 2.
Start the WebAccess Installation program, following the steps provided in "Installing the WebAccess Agent" in "Installing GroupWise WebAccess" in the GroupWise 6.5 Installation Guide.
Install the Windows WebAccess Agent, keeping in mind the following cluster-specific details:
Do not install the WebAccess Application at this time.
Repeat Step 4 and Step 5, mapping a drive to each node in the cluster.
Even if you installed the WebAccess Agent software to a shared disk, you need to repeat the installation process for each node so that the Internet Agent gets set up as a Windows service on each node.
Make sure you have completed all the WebAccess Agent tasks described in "Setting Up GroupWise WebAccess on NetWare or Windows" in "Installing GroupWise WebAccess" in the GroupWise 6.5 Installation Guide, but do not start the WebAccess Agent at this time.
Continue with Installing and Configuring the WebAccess Application in a Cluster.
Recall that the WebAccess Agent is the component of your WebAccess installation that accesses post offices and libraries to retrieve information for WebAccess client users. The WebAccess Application provides the link between the WebAccess Agent and the WebAccess clients' Web browsers.
To install the WebAccess Application:
Map a drive to the shared disk of the WebAccess resource group (WebAccess Clustering Worksheet item 1) where the WebAccess domain is located.
Map a drive to the first Web server node where you want to install the WebAccess Application (WebAccess Clustering Worksheet item 7).
If the Web server node where you are going to install the WebAccess Application is currently running any applications that rely on Java or on the Web server, migrate those applications to another node in the cluster. If any GroupWise agents are running on the node, migrate the agents.
Stop the Web server.
Start the WebAccess Installation program as you did when you installed the WebAccess Agent (Step 5). Keep in mind the following cluster-specific details:
Make sure you have completed all the WebAccess Application tasks described in "Setting Up GroupWise WebAccess on NetWare or Windows" in "Installing GroupWise WebAccess" in the GroupWise 6.5 Installation Guide.
Copy the directory\docs\com directory from the server where you just installed the WebAccess Application to the document root directory of the Web server (WebAccess Clustering Worksheet item 13).
Restart the Web server.
Offline and then online the Web server to reestablish its resource group IP address.
Repeat Step 2 through Step 9 for each Web server node in the Web server resource group possible owners list (WebAccess Clustering Worksheet item 1).
Continue with Testing Your Clustered WebAccess Installation.
Remember that the WebAccess resource group and the Web server resource group are separate resource groups that could fail over to different nodes at different times.
To thoroughly test your WebAccess installation:
Make sure the initial combination of WebAccess resource group and Web server resource group is functioning properly.
Migrate the WebAccess resource group to each node in its possible owners list, making sure it functions with the initial Web server node.
Migrate the Web server to a different node, migrate the WebAccess resource group to each node in its possible owners list, then make sure each combination works.
Repeat Step 3 for each Web server resource group.
Continue with Managing WebAccess in a Cluster.