Novell GROUPWISE 7 - INTEROPERABILITY GUIDE, Руководство пользователя

Страница: 345 / 485

Implementing WebAccess in a Heartbeat Cluster 345
n
ov
do
cx (e
n)
11
Ju
ly 20
08
When you have completed the Domain Worksheet, transfer the key information from the Domain
Worksheet 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,” on page 191 .
34.2.3 Recording the WebAccess 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 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.
34.2.4 Determining Appropriate Heartbeat Constraints for the
WebAccess Agent
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,” on page 138 , which describes the issues in
the context of planning MTA and POA installations.
WEBACCESS AGENT CLUSTERING WORKSHEET
Under Item 6: WebAccess Agent Domain Name , transfer the domain name and domain directory to the
WebAccess Agent Clustering Worksheet.
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.
WEBACCESS AGENT CLUSTERING WORKSHEET
Under Item 5: WebAccess Agent Resource Group Constraints , list the nodes where you want the
WebAccess Agent to fail over.