Selecting The Webaccess Agent Partition And Secondary Ip Address; Determining An Appropriate Failover List For The Webaccess Agent; Determining Cluster Resource Information For The Webaccess Agent - Novell GROUPWISE 8 - INTEROPERABILITY Manual

16.2.2 Selecting the WebAccess Agent Partition and
Secondary IP Address
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
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
WebAccess Agent partition.
Under Item 5: MTA Network
Under Item 6: WebAccess Agent Network
16.2.3 Determining an Appropriate Failover List for the
WebAccess Agent
By default, a GroupWise partition
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
As with the MTA and the POA, you need to decide which nodes in the cluster are appropriate
locations for the WebAccess Agent partition
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
Agents," on page 132, which describes the issues in the context of planning MTA and POA
installations.
WEBACCESS AGENT CLUSTERING WORKSHEET
Under Item 3: WebAccess Agent Failover
partition failover list.
16.2.4 Determining Cluster Resource Information for the
WebAccess Agent
A cluster resource is a shared
that can function successfully anywhere in the cluster. Cluster resources include the GroupWise
agents and the Messenger agents. When using the Configure GroupWise for Clustering option, the
GroupWise Installation program needs to know the mount point for the
the WebAccess Agent domain is located.
where a domain or post office already reside, which means
Agent, specify the secondary IP address for the
Information, copy the same secondary IP address.
Information, copy the same secondary IP address.
is configured to have all nodes in the cluster in its failover list,
fan-out-failover
to fail over to. You must install the WebAccess Agent
Section 13.6.2, "Determining Appropriate Failover Lists for the
List, list the nodes that you want in the WebAccess Agent
partition, secondary IP address, application, service, Web server, etc.,
principle.
GroupWise partition
Implementing WebAccess in a Linux Cluster 183
where