How The Webaccess Application Knows Which Webaccess Agents To Use - Novell GROUPWISE 8 - ADMINISTRATION Administration Manual

Section 53.3.4, "Assigning a Default WebAccess Agent to a Post Office," on page 887
Section 53.3.5, "Assigning a Default WebAccess Agent to a Domain," on page 888
Section 53.3.6, "Adding WebAccess Agents to the GroupWise Service Provider's List," on
page 889
53.3.1 How the WebAccess Application Knows Which
WebAccess Agents to Use
To redirect user requests or to fail over to a second WebAccess Agent, the WebAccess Application
needs to know which WebAccess Agents you want it to use. This might be all of the WebAccess
Agents in your system, or only specific WebAccess Agents.
Each time a user logs in, the WebAccess Application compiles a list, referred to as a redirection/
failover list, of the WebAccess Agents defined in the locations listed below.
The WebAccess URL. The standard URL does not contain a WebAccess Agent, but you can
modify the URL to point to a specific agent.
The user's Post Office object. You can assign a default WebAccess Agent to the post office to
handle requests from the post office's users.
The user's Domain object. You can assign a default WebAccess Agent to the domain to
handle requests from the domain's users.
The GroupWiseProvider object. This is the service provider used by the WebAccess
Application to connect to WebAccess Agents.
The commgr.cfg file. This file located in the WebAccess Application's home directory, which
varies by platform.
NetWare: sys:\Novell\GroupWise\WebAccess
OES Linux: /var/opt/novell/groupwise/webaccess
SLES:
/var/opt/novell/groupwise/webaccess
Windows:
c:\Novell\GroupWise\WebAccess
By default, only the GroupWise Provider object and the
Agent definition, as shown in the following table:
WebAccess Agent Default Locations
Table 53-1
Location
WebAccess URL
Post office
Domain
GroupWise service provider
commgr.cfg
on the Web server
on the Web server
commgr.cfg
WebAccess Agent
No agent defined
No agent defined
No agent defined
Agent 1
Agent 1
file include a WebAccess
Scaling Your WebAccess Installation 883