In a cluster, you need to create a separate domain to house each GroupWise gateway, including the WebAccess Agent.
The WebAccess Agent Clustering Worksheet lists the information you need to set up the WebAccess Agent in a clustering environment. You should print the worksheet and fill it out as you complete the tasks listed below:
As with the MTA and the POA, the WebAccess Agent needs cluster nodes, native Heartbeat resources, GroupWise resources, and a cluster resource group in order to function in your Heartbeat cluster. For a review of these cluster components, see Section 13.1, Installing Novell Cluster Services on Linux.
|
WEBACCESS AGENT CLUSTERING WORKSHEET |
|---|
|
Under Item 1: WebAccess Agent Nodes, list the nodes that you want to use for the WebAccess Agent. Identify each node by its DNS hostname and the IP address that it is physically configured with. Under Item 2: WebAccess Agent Cluster Resource Group, specify the name of the cluster resource group to hold the native Heartbeat and GroupWise resources associated with the WebAccess Agent. Under Item 3: Native Heartbeat Resources, list the native resource names and parameter values for the EVMS shared storage partition, the file system, and the secondary IP address that you want to use for the WebAccess Agent and its domain. Under Item 4: GroupWise Resources, list the resource names and parameter values for the WebAccess Agent and the MTA. |
The considerations involved in planning a domain for the WebAccess Agent are much the same as planning any other domain. In preparation, review Planning a New Domain
, then print and fill out the Domain Worksheet
in Domains
in the GroupWise 7 Administration Guide.
Keep in mind the following cluster-specific details:
When you specify the location for the domain directory on the Domain Worksheet, remember that it is on a shared storage partition, not on the node where you run the GroupWise Installation program.
Do not concern yourself with the GroupWise agent information on the Domain Worksheet. You can stop with item 10. You will plan the MTA installation later.
When you have completed the Domain Worksheet, transfer the key information from the Domain Worksheet to the WebAccess Agent Clustering Worksheet.
|
WEBACCESS AGENT CLUSTERING WORKSHEET |
|---|
|
Under Item 6: WebAccess Agent Domain Name, transfer the domain name and domain directory to the WebAccess Agent Clustering Worksheet. |
IMPORTANT:Do not create the new domain until you are instructed to do so in Section 16.3.1, Creating a Domain for the WebAccess Agent.
As with the MTA and the POA, the WebAccess Agent needs a secondary IP address that remains the same no matter which node in the cluster it runs on. You can place the WebAccess Agent and its domain in a cluster resource group where a domain or post office already reside, which means that the WebAccess Agent shares the same secondary IP address as that domain or post office and fails over along with that domain or post office. Or you can place the WebAccess Agent and its domain in its own cluster resource group, which means that it has its own secondary IP address and fails over independently.
|
WEBACCESS AGENT CLUSTERING WORKSHEET |
|---|
|
Under Item 7: MTA Network Information, select an IP address resource from the Heartbeat Clustering Worksheet (item 5) and record the secondary IP address associated with the resource on the WebAccess Agent Clustering Worksheet. Under Item 8: WebAccess Agent Network Information, copy the same secondary IP address. |
By default, a Heartbeat cluster is configured to have all nodes in the cluster available for failover. Only one node at a time can have a particular cluster resource group mounted and active. If a cluster resource group’s initial node fails, the resource group fails over to another node in the cluster.
You should customize the Heartbeat constraints for each GroupWise cluster resource group based on the fan-out-failover principle. As with the MTA and the POA, you need to decide which nodes in the cluster are appropriate locations where the WebAccess Agent cluster resource group can fail over. You must install the WebAccess Agent software on all of the nodes where you want the WebAccess Agent to be able to fail over. For a review of the fan-out-failover principle, see Section 13.6.2, Determining Appropriate Failover Lists for the Agents, which describes the issues in the context of planning MTA and POA installations.
|
WEBACCESS AGENT CLUSTERING WORKSHEET |
|---|
|
Under Item 5: WebAccess Agent Resource Group Constraints, list the nodes where you want the WebAccess Agent to fail over. |
Follow the instructions in Section 13.6.4, Planning the Linux Agent Installation, then return to this point. After you follow the instructions, you have a filled-out System Clustering Worksheet to use when you install the MTA.
IMPORTANT:Do not install the Linux MTA until you are instructed to do so in Section 16.3, Setting Up the WebAccess Agent in a Linux Cluster.
Aside from the cluster-specific issues discussed in the preceding sections, the considerations involved in planning to install the WebAccess Agent are the same in a clustering environment as for any other environment. Review the installation instructions in Installing the Linux WebAccess Agent
in Installing GroupWise WebAccess
in the GroupWise 7 Installation Guide. Use the GroupWise WebAccess Installation Worksheet
to record the planning information you will need as you install the WebAccess Agent in your cluster.
IMPORTANT:Do not install the WebAccess Agent software until you are instructed to do so in Section 16.3, Setting Up the WebAccess Agent in a Linux Cluster.
The WebAccess Application must be installed on a non-clustered Web server. For WebAccess Application planning information, see Determining the WebAccess and WebPublisher Applications’ Configuration
in Installing GroupWise WebAccess
in the GroupWise 7 Installation Guide.