In a cluster, you need to create a separate domain to house each GroupWise gateway, including the WebAccess Agent.
Section 16.6, WebAccess Agent Clustering Worksheet lists the information you need as you 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:
Section 16.2.2, Selecting the WebAccess Agent Partition and Secondary IP Address
Section 16.2.3, Determining an Appropriate Failover List for the WebAccess Agent
Section 16.2.4, Determining Cluster Resource Information for the WebAccess Agent
Section 16.2.7, Planning the WebAccess Application Installation
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 GroupWise partition, not on the node where you running the GroupWise Installation program. This location is referred to as the WebAccess Agent partition because it is where the WebAccess Agent message queues are located.
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 1: GroupWise Partition for the WebAccess Agent, transfer the domain location to the WebAccess Agent Clustering Worksheet. Under Item 2: WebAccess Agent Domain Name, transfer the domain name and database 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 is running on. You can place the WebAccess Agent and its domain on a GroupWise partition 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 on its own GroupWise partition, which means that it has its own secondary IP address and fails over independently.
|
WEBACCESS AGENT CLUSTERING WORKSHEET |
|---|
|
Under Item 1: GroupWise Partition for WebAccess Agent, specify the secondary IP address for the WebAccess Agent partition. Under Item 5: MTA Network Information, copy the same secondary IP address. Under Item 6: WebAccess Agent Network Information, copy the same secondary IP address. |
By default, a GroupWise partition is configured to have all nodes in the cluster in its failover list, organized in ascending alphanumeric order. Only one node at a time can have a particular GroupWise partition mounted and active. If a GroupWise partition’s preferred node fails, the partition fails over to the next node in the failover list. You should customize the failover list for each GroupWise partition 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 for the WebAccess Agent partition to fail over to. 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 failover lists, 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 3: WebAccess Agent Failover List, list the nodes that you want in the WebAccess Agent partition failover list. |
A cluster resource is a shared partition, secondary IP address, application, service, Web server, etc., that can function successfully anywhere in the cluster. Cluster resources include the GroupWise agents and the Messenger agents. When using the option, the GroupWise Installation program needs to know the mount point for the GroupWise partition where the WebAccess Agent domain is located.
|
WEBACCESS AGENT CLUSTERING WORKSHEET |
|---|
|
Under Item 4: Cluster Resource Mount Point, list the mount point for the GroupWise partition where the WebAccess Agent domain is located. |
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 Agent 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 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.