Updating Groupwise Objects With Cluster-Specific Descriptions; Knowing What To Expect In A Webaccess Agent Failover Situation - Novell GROUPWISE 7 - INTEROPERABILITY GUIDE Manual

34.5.1 Updating GroupWise Objects with Cluster-Specific
Descriptions
After installing the WebAccess Agent in your clustered GroupWise system, while the cluster-
specific information is fresh in your mind, you should record the cluster-specific information as part
of the GroupWise objects in ConsoleOne so that you can easily refer to it later. Be sure to update the
information in the GroupWise objects if the configuration of your system changes.
"Recording Cluster-Specific Information about the WebAccess Agent Domain and Its MTA"
on page 357
"Recording Cluster-Specific Information about the WebAccess Agent" on page 357
Recording Cluster-Specific Information about the WebAccess Agent Domain and Its
MTA
To permanently record important cluster-specific information for the WebAccess Agent domain:
1 In ConsoleOne, browse to and right-click the Domain object, then click Properties.
2 In the Description field of the WebAccess Agent domain Identification page, provide a cluster-
specific description of the WebAccess Agent domain, including the cluster resource group and
shared storage partition where the domain is located.
3 Click OK to save the WebAccess Agent domain description.
4 Select the WebAccess Agent Domain object to display its contents.
5 Right-click the MTA object, then click Properties.
6 In the Description field of the MTA Identification page, record the secondary IP address of the
cluster resource group.
When the MTA runs with a user interface, this information appears on the MTA server console.
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 > Identification.
3 In the Description field, record the secondary IP address of the cluster resource group.
4 Click OK to save the WebAccess Agent information.
5 Continue with Knowing What to Expect in a WebAccess Agent Failover
34.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 163.
Situation.
Implementing WebAccess in a Heartbeat Cluster 357
Agent.