Determining An Appropriate Failover Path For The Webaccess Agent Volume; Planning A Secondary Ip Address And Cluster-Unique Port Numbers For The Webaccess Agent And Its Mta; Deciding Where To Install The Webaccess Agent And Its Mta - Novell GROUPWISE 8 - INTEROPERABILITY Manual

Cluster-enabling relies on successful short name resolution throughout your system. Review
Section 2.7, "Ensuring Successful Name Resolution for GroupWise Volumes," on page
describes the issues in the context of planning MTA and POA installations.
5.2.3 Determining an Appropriate Failover Path for the
WebAccess Agent Volume
As with the MTA and the POA, you need to decide which nodes in the cluster are appropriate
locations where the WebAccess Agent volume could fail over. For a review of failover paths, see
"Determining Appropriate Failover Paths for the Agents" on page
the context of planning MTA and POA installations.
WEBACCESS CLUSTERING WORKSHEET
Under Item 4: WebAccess Agent Failover
WebAccess Agent volume failover path.
5.2.4 Planning a Secondary IP Address and Cluster-Unique
Port Numbers for the WebAccess Agent and Its MTA
As with the MTA and the POA, the WebAccess Agent needs a secondary IP address and cluster-
unique port numbers. As part of planning to install the MTA and POA, you should already have
determined the secondary IP address and cluster-unique port numbers for the WebAccess Agent and
its MTA as you filled out the
copy of this worksheet for your system, print it now and fill in current system information.
WEBACCESS CLUSTERING WORKSHEET
Under Item 6: MTA Network
port numbers from the WebAccess section the IP Address Worksheet to the WebAccess Clustering
Worksheet.
Under Item 1: Shared Volume for WebAccess
Cluster Volume IP Address as well, because they are the same.
Under Item 8: WebAccess Agent Network
address (the same as for its MTA) and the cluster-unique WebAccess Agent port number from the
WebAccess section of the IP Address Worksheet to the WebAccess Clustering Worksheet.
5.2.5 Deciding Where to Install the WebAccess Agent and Its
MTA
As with the MTA and the POA, you can choose to install the WebAccess Agent and its MTA to the
directory of each node or to a
sys:\system
volume. For a discussion of these alternatives, see
on page 31, which describes the issues in the context of planning MTA and POA installations. If you
only have one WebAccess Agent for your GroupWise system with several nodes in its failover path,
it is an easy choice.
Path, list the nodes that you want to have in the
"IP Address Worksheet" on page
Information, transfer the MTA secondary IP address and cluster-unique
Agent, copy the MTA secondary IP address under
Information, transfer the WebAccess Agent secondary IP
vol:\system
"Deciding Where to Install the Agent Software"
31, which describes the issues in
37. If you do not have a filled-out
directory on the WebAccess Agent
Implementing WebAccess in a NetWare Cluster
27, which
87