102 GroupWise 7 Interoperability Guidenovdocx (en) 11 July 2008Recording Cluster-Specific Information about the WebAccess AgentWith the contents of the WebAccess Agent domain still displayed:1 Right-click the WEBAC70A object, then click Properties.2 Click GroupWise, then click Identification.3 In the Description field, record the secondary IP address of the cluster-enabled WebAccessAgent domain volume and the cluster-unique port numbers used by the WebAccess Agent.This information appears on the WebAccess Agent console, no matter which node in the clusterit is currently running on.4 Click OK to save the WebAccess Agent information.5 Continue with Knowing What to Expect in MTA and POA Failover Situations.5.4.2 Knowing What to Expect in WebAccess FailoverSituationsThe failover behavior of the MTA for the WebAccess Agent domain is the same as for an MTA in aregular domain. See “Knowing What to Expect in MTA and POA Failover Situations” on page 64.The WebAccess Application caches users’ credentials on the node where it is running. Therefore, ifthat node fails, or if the WebAccess Application migrates to a different node, the cached credentialsare lost. Consequently, the user needs to restart the WebAccess client in order to re-authenticate andre-establish the credentials.If the WebAccess Agent fails over or migrates, the user receives an error message that theWebAccess Agent is no longer available. However, after the WebAccess Agent starts in its newlocation, the WebAccess Application passes the cached user credentials to the WebAccess Agentand the user reconnects automatically without having to re-authenticate.As with the MTA and the POA, migration of the WebAccess Agent takes longer than failover.However, the WebAccess Agent restarts quickly so that users are able to reconnect quickly.5.4.3 Updating the WebAccess Agent Configuration File(commgr.cfg)As part of installing WebAccess, the WebAccess Agent configuration file (commgr.cfg) iscreated in the following subdirectory:domain\wpgate\webac70aIt is also automatically copied to the following Web server subdirectory:sys:\novell\webaccessIf you change WebAccess agent configuration information (for example, if you change its ipaddress), the information is changed in the following file:domain\wpgate\webac70a\commgr.cfgbecause the domain is on a cluster-enabled volume, and it is changed in the following file:sys:\novell\webaccess\commgr.cfg
