Novell GROUPWISE 7 - WEB ACCESS User manual

WebAccess
XII
novdocx (en) 11 December 2007
853
XII
WebAccess
Chapter 53, “Scaling Your WebAccess Installation,” on page 855
Chapter 54, “Configuring WebAccess Components,” on page 869
Chapter 55, “Managing User Access,” on page 915
Chapter 56, “Monitoring WebAccess Operations,” on page 925
Chapter 57, “Using WebAccess Startup Switches,” on page 945

854 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007

Scaling Your WebAccess Installation
53
novdocx (en) 11 December 2007
855
53
Scaling Your WebAccess
Installation
If your GroupWise®system is relatively small (one domain and a few post offices) and all post
offices reside in the same location, a basic installation of GroupWise WebAccess might very well
meet your needs. However, if your GroupWise system is large, spans multiple locations, or requires
failover support, you might need to scale your GroupWise WebAccess installation to better meet the
reliability, performance, and availability needs of your users.
The following sections provide information about the various configurations you can implement and
instructions to help you create the configuration you choose:
Section 53.1, “WebAccess Configurations,” on page 855
Section 53.2, “Installing Additional WebAccess Components,” on page 858
Section 53.3, “Configuring Redirection and Failover Support,” on page 860
For information about creating a basic GroupWise WebAccess installation, see “Installing
GroupWise WebAccess” in the GroupWise 7 Installation Guide.
53.1 WebAccess Configurations
A basic installation of GroupWise WebAccess requires the WebAccess Agent and the WebAccess
Application, as shown in the following diagram. The WebPublisher Application is also required if
you plan to use GroupWise WebPublisher.
Figure 53-1 A Basic Installation of GroupWise WebAccess
Depending on your needs, it might be necessary for you to add additional WebAccess Agents or to
have multiple Web servers running the WebAccess Application and WebPublisher Application.
Section 53.1.1, “Multiple WebAccess Agents,” on page 855
Section 53.1.2, “Multiple WebAccess and WebPublisher Applications,” on page 856
53.1.1 Multiple WebAccess Agents
GroupWise WebAccess is designed to allow one installation of the WebAccess Application and
WebPublisher Application to support multiple WebAccess Agents, as shown in the following
diagram.
Domain
Post Office
Post Office
WebAccess
Agent
Web Server with
WebAccess and
WebPublisher Applications

856 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Figure 53-2 Multiple WebAccess Agents
There are various reasons why you might want to add additional WebAccess Agents, including:
Improving reliability: One WebAccess Agent might provide sufficient access and
performance, but you want to protect against downtime that would occur if the WebAccess
Agent became unavailable because of server failure or some other reason. Installing more than
one WebAccess Agent enables you to set up failover support to make your system more
reliable.
Improving performance: The WebAccess Agent is designed to be close to the GroupWise
databases. It requires direct access to a domain database and either direct access to post office
databases or TCP/IP access to the Post Office Agents. For best performance, you should ensure
that the WebAccess Agent is on the same local area network as the domain and post offices it
needs access to. For example, in most cases you would not want a WebAccess Agent in Los
Angeles accessing a post office in London.
Improving availability: The WebAccess Agent has 12 threads assigned to process user
requests, which means that it can process only 12 requests at one time regardless of the number
of users logged in. If necessary, you can increase the number of threads allocated to the
WebAccess Agent, but each thread requires additional server memory. If you reach a point
where WebAccess is unavailable to users because thread utilization is at a peak and all server
memory is being used, you might need to have several WebAccess Agents, installed on
different network servers, servicing your post offices. For information about changing the
number of allocated threads, see Section 54.1, “Configuring the WebAccess Agent,” on
page 870.
53.1.2 Multiple WebAccess and WebPublisher Applications
As with the WebAccess Agent, you can also install the WebAccess Application and WebPublisher
Application to multiple Web servers, as shown in the following diagram.
Web Server with
WebAccess and
WebPublisher Applications
Domain
Post Office
Post Office
WebAccess
Agent
Domain
Post Office
Post Office
WebAccess
Agent
Domain
Post Office
Post Office
WebAccess
Agent

Scaling Your WebAccess Installation 857
novdocx (en) 11 December 2007
Figure 53-3 The WebAccess Application and WebPublisher Application Installed to Multiple Web Servers
Some reasons for wanting to use this type of configuration include:
Enabling WebAccess users on an intranet to access GroupWise through an internal Web server
and WebAccess users on the Internet to access GroupWise through an exposed Web server.
Increasing Web server performance by balancing the workload among several Web servers,
especially if you are using the Web server for other purposes in addition to GroupWise
WebAccess.
Hosting WebAccess (the WebAccess Application) on one Web server for your GroupWise
users and WebPublisher (the WebPublisher Application) on another Web server for public
Internet use.
If necessary, you can use multiple WebAccess Agents in this configuration, as shown below.
Figure 53-4 The WebAccess Application on One Web Server, and the WebPublisher Application on Another
Web Server with
WebAccess and
WebPublisher A
pp
lications
Domain
Post Office
Post Office
WebAccess
Agent
Web Server with
WebAccess and
WebPublisher Applications
Web Server with
WebAccess and
WebPublisher Applications
Domain
Post Office
Post Office
WebAccess
Agent
Domain
Post Office
Post Office
WebAccess
Agent
Domain
Post Office
Post Office
WebAccess
Agent
Web Server with
WebAccess and
WebPublisher Applications

858 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
53.2 Installing Additional WebAccess
Components
The following sections assume that you have installed at least one WebAccess Agent and one
WebAccess Application (or WebPublisher Application) and now need to install additional agents or
applications.
Section 53.2.1, “Installing Additional Components on NetWare or Windows,” on page 858
Section 53.2.2, “Installing Additional Components on Linux,” on page 859
53.2.1 Installing Additional Components on NetWare or
Windows
“Installing a NetWare or Windows WebAccess Agent” on page 858
“Installing a NetWare or Windows WebAccess or WebPublisher Application” on page 858
For more information, see “NetWare and Windows: Setting Up GroupWise WebAccess” in the
GroupWise 7 Installation Guide.
Installing a NetWare or Windows WebAccess Agent
1Insert the GroupWise 7 Administrator for NetWare/Windows CD into the CD drive to start the
Installation program, click Install Products, click GroupWise WebAccess, then click Install
GroupWise WebAccess. If the Installation program does not start automatically, run
setup.exe from the root of the CD.
or
If you’ve already copied the GroupWise WebAccess software to a software distribution
directory, run setup.exe from the internet\webacces directory.
2Click Yes to accept the license agreement and display the Select Components dialog box.
3Deselect all components except the GroupWise WebAccess Agent, then click Next.
4Follow the prompts to create the WebAccess Agent’s gateway directory, install the WebAccess
Agent software, and create the WebAccess Agent’s object in Novell®eDirectoryTM.
If you are installing to a domain where another WebAccess Agent already exists, you must use
a different directory and object name than the one used for the existing WebAccess Agent.
5When installation is complete, you need to configure your system so that the WebAccess and
WebPublisher Applications know about the WebAccess Agent and can direct the appropriate
user requests to it. For information, see Section 53.3, “Configuring Redirection and Failover
Support,” on page 860.
Installing a NetWare or Windows WebAccess or WebPublisher Application
To install a WebAccess Application or a WebPublisher Application to a Web server:
1Insert the GroupWise 7 Administrator for NetWare/Windows CD into the CD drive to start the
installation program, click Install Products, click Groupwise WebAccess, then click Install
GroupWise WebAccess. If the installation program does not start automatically, run
setup.exe from the root of the CD.

Scaling Your WebAccess Installation 859
novdocx (en) 11 December 2007
or
If you’ve already copied the Groupwise WebAccess software to a software distribution
directory, run setup.exe from the internet/webacces directory.
2Click Yes to accept the license agreement and display the Select Components dialog box.
3Deselect all components except the GroupWise WebAccess application and/or the Groupwise
WebPublisher Application, then click Next.
The WebAccess Application and WebPublisher Application must be associated with a
WebAccess Agent. For information on configuring a WebAccess or WebPublisher Application
to connect to other WebAccess Agents, see Section 53.3, “Configuring Redirection and
Failover Support,” on page 860.
4Specify the path for the WebAccess Agent’s gateway directory.
5Follow the prompts to install the files to the Web server. Restart the Web server.
53.2.2 Installing Additional Components on Linux
“Installing a Linux WebAccess Agent” on page 859
“Installing a Linux WebAccess and WebPublisher Application” on page 860
For more information, see “Linux: Setting Up GroupWise WebAccess” in the GroupWise 7
Installation Guide.
Installing a Linux WebAccess Agent
1Make sure that LDAP is running on your eDirectory server and that it is configured to accept
login from the WebAccess Agent Installation program.
2In a terminal window, become root by entering sux and the root password.
The sux command enables the X Window System, which is required for running the GUI
GroupWise Installation program, Installation Advisor, and the Setup Advisor. If you do not
want to use the X Window System, you can install GroupWise components individually, as
described in “Installing the GroupWise Agents Using the Text-Based Installation Program” in
“Installing GroupWise Agents” in the GroupWise 7 Installation Guide.
3Change to the root of the GroupWise 7 Administrator for Linux CD.
4Enter ./install.
5Select the language in which you want to run the Installation program and install the
WebAccess software, then click Next.
6In the Installation program, click Install Products > GroupWise WebAccess > Install
WebAccess Agent.
7When the installation is complete, click OK.
8Click Configure WebAccess Agent.
9Follow the prompts to configure the Linux WebAccess Agent.
10 When installation and configuration is complete, you need to configure your GroupWise
system so that the WebAccess and WebPublisher Applications know about this instance of the
WebAccess Agent and can direct the appropriate user requests to it. For instructions, see
Section 53.3, “Configuring Redirection and Failover Support,” on page 860.

860 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Installing a Linux WebAccess and WebPublisher Application
To install a WebAccess Application and a WebPublisher Application to a Web server:
1After installing and configuring the WebAccess Agent, if you want to use an existing Apache
and Tomcat installations, click Install GroupWise WebAccess Application.
or
Click Install GroupWise WebAccess Application with Apache and Tomcat.
This installs a version of Apache and Tomcat specifically for use with GroupWise. Apache files
are installed under /var/opt/novell/http and /etc/opt/novell/http. Tomcat
files are installed under /var/opt/novell/tomcat4 and /etc/opt/novell/
tomcat4.
In addition, a self-signed certificate is generated, enabling users to use WebAccess and
WebPublisher using an SSL connection.
NOTE: The option to install Apache and Tomcat along with the WebAccess Application is not
available if you are installing to Novell Open Enterprise Server Linux because Apache and
Tomcat are already installed and configured correctly in that environment.
2When the installation is complete, click OK.
3Click Configure WebAccess Application.
4Follow the prompts to configure the Linux WebAccess Application.
5When the installation and configuration is complete, start or restart the Web server.
53.3 Configuring Redirection and Failover
Support
Redirection enables the WebAccess Application to direct user requests to specific WebAccess
Agents. For example, you might want WebAccess Agent 1 to process all requests from users on Post
Office 1 and WebAccess Agent 2 to process all requests from users on Post Office 2.
Failover support enables the WebAccess Application to contact a second WebAccess Agent if the
first WebAccess Agent is unavailable. For example, if the WebAccess Application receives a user
request that should be processed by WebAccess Agent 1 but it is unavailable, the WebAccess
Application can route the user request to WebAccess Agent 2 instead.
The following sections provide information to help you successfully configure redirection and
failover support:
Section 53.3.1, “How the WebAccess Application Knows Which WebAccess Agents to Use,”
on page 861
Section 53.3.2, “Synchronizing the Encryption Key,” on page 863
Section 53.3.3, “Specifying a WebAccess Agent in the WebAccess URL,” on page 864
Section 53.3.4, “Assigning a Default WebAccess Agent to a Post Office,” on page 865
Section 53.3.5, “Assigning a Default WebAccess Agent to a Domain,” on page 866
Section 53.3.6, “Adding WebAccess Agents to the GroupWise Service Provider’s List,” on
page 867

Scaling Your WebAccess Installation 861
novdocx (en) 11 December 2007
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.
By default, only the GroupWise Provider object and the commgr.cfg file include a WebAccess
Agent definition, as shown in the following table:
Table 53-1 WebAccess Agent Default Locations
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.
NetWare
and
Windows:
novell\webaccess\users on the Web server
Linux: /opt/novell/groupwise/webaccess/users
Location WebAccess Agent
WebAccess URL No agent defined
Post office No agent defined
Domain No agent defined
GroupWise service provider Agent 1
Commgr.cfg Agent 1

862 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Redirection/Failover List: Example 1
Assume that the WebAccess Agents are defined as follows:
Using this information, the WebAccess Application would create the following redirection/failover
list:
Because there is no WebAccess Agent defined in the WebAccess URL, the WebAccess Application
redirects the user’s request to the default WebAccess Agent (Agent 1) assigned to the user’s post
office. If Agent 1 is unavailable, the WebAccess Application fails over to the domain’s default
WebAccess Agent (Agent 4). If Agent 4 is unavailable, the WebAccess Application fails over to
Agent 2 and then Agent 3, both of which are defined in the GroupWise service provider’s list.
Redirection/Failover List: Example 2
Assume that the WebAccess Agents are defined as follows:
Using this information, the WebAccess Application would create the following redirection/failover
list:
Location WebAccess Agent
WebAccess URL No agent defined
Post office Agent 1
Domain Agent 4
GroupWise service provider Agent 2
Agent 3
Commgr.cfg Agent 4
List Entry Taken From
Agent 1 Post office
Agent 4 Domain
Agent 2 GroupWise service provider
Agent 3 GroupWise service provider
Location WebAccess Agent
WebAccess URL No agent defined
Post office No agent defined
Domain No agent defined
GroupWise service provider Agent 1
Agent 2
Agent 3
Commgr.cfg Agent 2

Scaling Your WebAccess Installation 863
novdocx (en) 11 December 2007
Because there is no WebAccess Agent defined in the WebAccess URL, user’s post office, or user’s
domain, the WebAccess Application redirects the user’s request to the first WebAccess Agent
(Agent 1) in the GroupWise service provider’s list. If Agent 1 is unavailable, the WebAccess
Application fails over to Agent 2 and then Agent 3.
53.3.2 Synchronizing the Encryption Key
Every WebAccess Agent has an encryption key. In order to communicate with a WebAccess Agent,
the WebAccess Application must know the agent’s encryption key. The encryption key is randomly
generated when the WebAccess Agent object is created in eDirectory, which means that every
WebAccess Agent has a unique encryption key.
If a WebAccess Application communicates with more than one WebAccess Agent, all the
WebAccess Agents must use the same encryption key.
To modify a WebAccess Agents encryption key:
1In ConsoleOne®, right-click the WebAccess Agent object, then click Properties.
2Click WebAccess to display the WebAccess Settings page.
3Make the encryption key the same as the key for any other WebAccess Agents with which the
WebAccess Application communicates.
4Click OK to save the changes.
List Entry Taken From
Agent 1 GroupWise service provider
Agent 2 GroupWise service provider
Agent 3 GroupWise service provider

864 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
53.3.3 Specifying a WebAccess Agent in the WebAccess URL
To have the WebAccess Application connect to a WebAccess Agent other than the one specified in
the commgr.cfg file, you can add the WebAccess Agent’s IP address and port number to the URL
that calls the WebAccess Application. For example, the default WebAccess Application URL is:
http://web_server_ip_address/gw/webacc
This URL causes the WebAccess Application to use the IP address and port number that is listed in
the commgr.cfg file. To redirect the WebAccess Application to another WebAccess Agent, you
would use the following URLs:
http://web_server_ip_address/gw/webacc
?GWAP.ip=agent_ip_address&GWAP.port=port_number
For example:
http://172.16.5.18/gw/webacc
?GWAP.ip=172.16.6.10&GWAP.port=7204
In this example, the WebAccess Application redirects its requests to the WebAccess Agent at IP
address 172.16.6.10 and port number 7204. If the WebAccess Agent is using the same port number
that is listed in the commgr.cfg file, you do not need to include the GWAP.port parameter. Or, if
the WebAccess Agent is using the same IP address that is listed in the commgr.cfg file, you do
not need to include the GWAP.ip parameter.
If you want, you can use the WebAccess Agent’s DNS hostname in the URL rather than its IP
address.
You can also specify the user interface language by adding the &User.lang option. This allows you
to bypass the initial WebAccess language page. For example:
http://172.16.5.18/gw/webpub
?GWAP.ip=172.16.6.10&GWAP.port=7204&User.lang=en
You can use the language codes listed below with the &User.lang parameter in the WebAccess URL.
Table 53-2 Language Codes
Language Code Language Code
Arabic ar Hebrew iw
Brazilian Portuguese pt Hungarian hu
Chinese Simplified cs Italian it
Chinese Traditional ct Japanese jp
Czechoslovakian cz Korean kr
Danish da Norwegian no
Dutch nl Polish pl
English us Russian ru
Finnish su Spanish es
French fr Swedish sv

Scaling Your WebAccess Installation 865
novdocx (en) 11 December 2007
You can add the URL to any Web page. For example, if you are using the Web Services page as your
initial WebAccess page, you could add the URL to that page. You should add one URL for each
WebAccess Agent.
For example, suppose you had offices in three different locations and installed a WebAccess Agent
at each location to service the post offices at those locations. To enable the WebAccess Application
to redirect requests to the WebAccess Agent at the appropriate location, you could modify the Web
Services page to display a list of the locations. The modified page would include the following
HTML code (if WebAccess is running on NetWare or Windows):
<UL>
<LI><A HREF="http://172.16.5.18/gw/
webacc?GWAP.ip=172.16.6.10&GWAP.port=7204>San Francisco
</A></LI>
<LI><A HREF="http://172.16.5.18/gw/webacc?GWAP.ip=172.16.6.12>New York
</A></LI>
<LI><A HREF="http://172.16.5.18/gw/
webacc?GWAP.ip=172.16.6.33&GWAP.port=7203>London
</A></LI>
</UL>
The displayed HTML page would contain the following list of locations:
San Francisco
New York
London
When a user selects a location, the WebAccess Application routes all requests to the WebAccess
Agent at the selected location.
53.3.4 Assigning a Default WebAccess Agent to a Post Office
The WebAccess Application uses the post office’s default WebAccess Agent if no WebAccess Agent
has been specified in the WebAccess URL (see Section 53.3.3, “Specifying a WebAccess Agent in
the WebAccess URL,” on page 864) or if that WebAccess Agent is unavailable. This applies only if
you have multiple WebAccess Agents installed in your GroupWise system. If you have only one
WebAccess Agent, it services all post offices.
To assign a default WebAccess Agent to a post office:
1In ConsoleOne, right-click the Post Office object, then click Properties.
2Click GroupWise > Default WebAccess to display the Default WebAccess page.
German de
Language Code Language Code

866 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
3Select the Override box to turn on the option.
4In the Default WebAccess Gateway box, browse for and select the WebAccess Agent that you
want to assign as the default agent.
When you have multiple WebAccess Agents and a user logs in to GroupWise WebAccess, the
GroupWise Application running on the Web server checks to see if a default WebAccess Agent
has been assigned to the user’s post office. If so, the WebAccess Application connects to the
assigned WebAccess Agent. If not, it connects to the default WebAccess Agent assigned to the
post office’s domain, as described in Section 53.3.5, “Assigning a Default WebAccess Agent to
a Domain,” on page 866 or to one of the WebAccess Agents in its service provider list, as
described in Section 53.3.6, “Adding WebAccess Agents to the GroupWise Service Provider’s
List,” on page 867. If possible, select a WebAccess Agent that has good access to the post
office to ensure the best performance.
5Click OK to save the changes.
53.3.5 Assigning a Default WebAccess Agent to a Domain
The WebAccess Application uses the domain’s default WebAccess Agent if 1) no WebAccess Agent
has been specified in the WebAccess URL (see Section 53.3.3, “Specifying a WebAccess Agent in
the WebAccess URL,” on page 864), 2) no default WebAccess Agent has been defined for the user’s
post office, or 3) neither of those WebAccess Agents are available. This applies only if you have
multiple WebAccess Agents installed in your GroupWise system. If you have only one WebAccess
Agent, it services users in all domains.
To assign a default WebAccess Agent to a domain:
1In ConsoleOne, right-click the Domain object, then click Properties.
2Click GroupWise > Default WebAccess to display the Default WebAccess page.

Scaling Your WebAccess Installation 867
novdocx (en) 11 December 2007
3Select the Override box to turn on the option.
4In the Default WebAccess Gateway box, browse for and select the WebAccess Agent that you
want to assign as the default agent.
When you have multiple WebAccess Agents and a user logs in to GroupWise WebAccess, the
GroupWise Application running on the Web server checks to see if a default WebAccess Agent
has been assigned to the user’s post office, as described in Section 53.3.4, “Assigning a Default
WebAccess Agent to a Post Office,” on page 865. If so, the WebAccess Application connects to
the assigned WebAccess Agent. If not, it connects to the default WebAccess Agent assigned to
the post office’s domain or to one of the WebAccess Agents in its service provider list, as
described in Section 53.3.6, “Adding WebAccess Agents to the GroupWise Service Provider’s
List,” on page 867. If possible, you should select a WebAccess Agent that has good access to
the domain’s post offices to ensure the best performance. Each post office uses the domain’s
default WebAccess Agent unless you override the default at the post office level.
5Click OK to save the changes.
53.3.6 Adding WebAccess Agents to the GroupWise Service
Provider’s List
1In ConsoleOne, right-click the GroupWise service provider object (GroupWiseProvider), then
click Properties.
2Click Provider to display the Environment page.

868 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
The GroupWise WebAccess Agents list displays the WebAccess Agents the GroupWise service
provider can communicate with when attempting to complete a request. By default, the list
includes the WebAccess Agent that is defined in the commgr.cfg file (listed in the
Configuration File field). If the first WebAccess Agent is unavailable, the GroupWise service
provider attempts to use the second, third, fourth, and so on until it is successful.
3Click Add, select the WebAccess Agent you want to add to the list, then click OK.
4Repeat Step 3 for each WebAccess Agent you want to add to the list, then click OK to save the
changes.

Configuring WebAccess Components
54
novdocx (en) 11 December 2007
869
54
Configuring WebAccess
Components
GroupWise®WebAccess consists of a number of components. The GroupWise 7 Installation Guide
presented a simple overview of those components:
Figure 54-1 WebAccess Components: Simplified
This section of the GroupWise 7 Administration Guide provides additional details about those and
additional components:
Figure 54-2 WebAccess Components: Complete
Each component can be configured to meet the specific needs of your GroupWise system:
Section 54.1, “Configuring the WebAccess Agent,” on page 870
Section 54.2, “Configuring the WebAccess Application,” on page 879
Section 54.3, “Configuring the Novell Speller Application,” on page 892
Section 54.4, “Configuring the WebPublisher Application,” on page 894
Section 54.5, “Configuring the GroupWise Service Provider,” on page 903
Section 54.6, “Configuring the LDAP Service Provider,” on page 905
Section 54.7, “Configuring the GroupWise Document Service Provider,” on page 907
Section 54.8, “Configuring the Document Viewer Agent,” on page 909
Section 54.9, “Enabling Web Server Data Compression,” on page 913
WebAccess
Agent
Web
Browser
Web
Server WebPublisher
Application
WebAccess
Application
Viewer
Agent
Post Office
Library
WebAccess
Agent
Web
Browser
Web
Server
Viewer
Agent
Document
Service Provider
WebPublisher
Application
WebAccess
Application
LDAP Provider
GroupWise Provider
Speller
Application
LDAP
Server
Post Office
Library

870 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
54.1 Configuring the WebAccess Agent
The WebAccess Agent receives user requests from the WebAccess Application and WebPublisher
Application, accesses post offices and libraries to process the requests, and then passes information
back to the applications.
Figure 54-3 WebAccess Agent
During installation, the GroupWise®WebAccess Agent is set up with a default configuration.
However, you can use the information in the following sections to optimize the WebAccess Agent
for your environment:
Section 54.1.1, “Modifying WebAccess Settings,” on page 870
Section 54.1.2, “Modifying WebPublisher Settings,” on page 871
Section 54.1.3, “Managing Access to Post Offices,” on page 873
Section 54.1.4, “Securing WebAccess Agent Connections with SSL,” on page 875
Section 54.1.5, “Changing the WebAccess Agent’s Network Address or Port Numbers,” on
page 877
Section 54.1.6, “Binding the WebAccess Agent to a Specific IP Address,” on page 878
54.1.1 Modifying WebAccess Settings
Using ConsoleOne®, you can configure the following GroupWise WebAccess settings for the
WebAccess Agent:
The maximum number of threads the agent uses to process WebAccess messages
The key used to encrypt information sent between the agent and the WebAccess Application
To modify the configuration information:
1In ConsoleOne, right-click the WebAccess Agent object, then click Properties.
2Click WebAccess > Settings to display the WebAccess Settings page.
WebAccess
Agent
Web
Browser
Web
Server
Viewer
Agent
Document
Service Provider
WebPublisher
Application
WebAccess
Application
LDAP Provider
GroupWise Provider
Speller
Application
LDAP
Server
Post Office
Library

Configuring WebAccess Components 871
novdocx (en) 11 December 2007
3Modify any of the following fields:
Maximum Threads: This is the maximum number of threads the agent uses at one time to
process requests. The default (12) enables the agent to process 12 requests at one time, which is
usually sufficient. If the agent regularly receives more requests than it has threads, you might
want to increase the maximum number of threads. Increasing the threads increases the amount
of server memory used by the agent.
To determine the maximum number of threads that have been in use at one time (for example, 8
of the 12 threads), you can view the WebAccess Agent server console on NetWare®or you can
view the status information displayed through the WebAccess Agent Web console on any
platform. See Section 56.1, “Monitoring the WebAccess Agent,” on page 925.
Encryption Key: The encryption key is used to encrypt and decrypt the information sent
between the WebAccess Agent and the WebAccess Application. If you do not want to use the
default encryption key, you can type your own key. The encryption key must be identical to the
encryption keys of any other WebAccess Agents that the WebAccess Application
communicates with. For more information, see Section 53.3, “Configuring Redirection and
Failover Support,” on page 860.
4Click OK to save the changes.
54.1.2 Modifying WebPublisher Settings
Using ConsoleOne, you can configure the following WebPublisher settings for the WebAccess
Agent:
The GroupWise account used by the WebAccess Agent to retrieve documents for WebPublisher
users
The GroupWise libraries where the WebAccess Agent looks for documents that have been
shared with GroupWise WebPublisher users
Whether the WebPublisher user has General User Access to documents
To modify the configuration information:
1In ConsoleOne, right-click the WebAccess Agent object, then click Properties.

872 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
2Click WebPublisher > Settings to display the WebPublisher Settings page.
3Modify any of the following fields:
GroupWise Mailbox ID: The WebPublisher proxy user serves two purposes: 1) GroupWise
users make documents available to GroupWise WebPublisher users by sharing the documents
with the WebPublisher proxy user and 2) the WebAccess Agent logs in to GroupWise through
the WebPublisher proxy user. This enables the WebAccess Agent to search for and retrieve
documents that have been shared with the WebPublisher proxy user. Specify the ID for the
GroupWise mailbox you want to use.
Password: Click Set Password to specify the mailbox password.
Allow Access to These Libraries: This list displays the libraries that the WebAccess Agent
has access to. If a library is not in the list, WebPublisher users cannot see the library’s
documents. If a library is listed, WebPublisher users can view any of the library’s documents
that have been shared (by the document owner) with the WebPublisher proxy user.
To add a library to the list, click Add, then browse for and select the library.
To change the display name or description for the library, select the library, then click
Properties. By default, the library’s Novell®eDirectoryTM object name is used for the display
name.
To remove a library from the list, select the library, then click Remove.
Assign General User Access to WebPublisher Users: When sharing documents with
GroupWise users, a document’s owner can assign individual access rights and general access
rights (through the General User Access option). The General User Access rights determine the
access for all GroupWise users who do not receive individual access rights. For example, if a
document’s owner sets the General User Access to View, all GroupWise users with access to
that library can view the document.
This option lets you determine whether or not you, as the GroupWise system administrator,
want to give General User Access rights to WebPublisher users. For example, with this option
enabled, WebPublisher users can view any documents that have General User Access set to
View.
4Click OK to save the changes.