Knowing What To Expect In A Webaccess Agent Failover Situation; Webaccess Agent Clustering Worksheet - Novell GROUPWISE 8 - INTEROPERABILITY Manual

This information appears on the MTA console, no matter which node in the cluster it is
currently running on.
7 Click OK to save the MTA description.
8 Continue with
Recording Cluster-Specific Information about the WebAccess
Recording Cluster-Specific Information about the WebAccess Agent
With the contents of the WebAccess Agent domain still displayed:
1 Right-click the WebAccess Agent object, then click Properties.
2 Click GroupWise, then click Identification.
3 In the Description field, record the secondary IP address of the
WebAccess Agent domain is located.
This information appears on the WebAccess Agent console, no matter which node in the cluster
it is currently running on.
4 Click OK to save the WebAccess Agent information.
5 Continue with
Knowing What to Expect in an Internet Agent Failover
16.5.2 Knowing What to Expect in a WebAccess Agent Failover
Situation
The failover behavior of the MTA for the WebAccess Agent domain is the same as for an MTA in a
regular domain. See Section 14.6.2, "Knowing What to Expect in MTA and POA Failover
Situations," on page 157.
When the WebAccess Agent fails over, the WebAccess client user sees the following message:
Unable to communicate with the GroupWise WebAccess Agent
The user just needs to be patient. When the WebAccess Agent comes up on the next node, the user
can continue working without logging in again.
If the POA for the user's post office fails over, the WebAccess client becomes unresponsive, but
there is no error message. Again, the user should be patient until the POA comes up on the next
node. Then the user can continue working without logging in again.
As with the MTA and the POA, migration of the WebAccess Agent takes longer than failover. In
fact, the WebAccess Agent can seem especially slow to shut down properly as it finishes its normal
processing, stops its threads, and stops the Document Viewer Agent. For a busy WebAccess Agent,
you might need to wait several minutes for it to shut down properly.

16.6 WebAccess Agent Clustering Worksheet

Item
1) GroupWise Partition for the
WebAccess Agent:
Secondary IP Address:
Explanation
Specify the GroupWise partition where the WebAccess Agent domain
will be created, along with its secondary IP address.
For more information, see
Agent Partition and Secondary IP Address," on page
Agent.
GroupWise partition
Situation.
Section 16.2.2, "Selecting the WebAccess
Implementing WebAccess in a Linux Cluster 197
where the
183.