Novell GROUPWISE 7 - WEB ACCESS Manual page 9

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
novell\webaccess\users
and
Windows:
Linux: /opt/novell/groupwise/webaccess/users
By default, only the GroupWise Provider object and the commgr.cfg file include a WebAccess
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
If no other WebAccess Agents are defined (as is the case by default), the WebAccess Application
directs all user requests to the WebAccess Agent (Agent 1) listed in the commgr.cfg file. This file
is located in the WebAccess Application's home directory on the Web server. The commgr.cfg
file contains the IP address and encryption key for the WebAccess Agent that was associated with
the WebAccess Application during the application's installation.
If Agent 1 is not available, the user receives an error message and cannot log in.
on the Web server
WebAccess Agent
No agent defined
No agent defined
No agent defined
Agent 1
Agent 1
Scaling Your WebAccess Installation 861