Chapter 1: Plan GroupWise WebAccess

GroupWise* WebAccess lets users access their GroupWise mailboxes through a Web browser to send and read messages, appointments, tasks, and notes, and to view and modify their GroupWise calendars.

The GroupWise WebAccess Install program (SETUP.EXE) helps you install the WebAccess files to the appropriate locations. Before running the Install program, you should complete the tasks listed below to plan your WebAccess installation. You can use the installation worksheet at the end of this chapter to record the information that the Install program will prompt you for. If you print this chapter, the worksheet will be printed with it. To print the worksheet only, see Appendix A: Installation Worksheet.

• Understand the GroupWise WebAccess Components
  
  
• Meet the GroupWise System Requirements
  
  
• Decide Where to Install the WebAccess CGI Extension and WebAccess Agent
  
  
• Select a Domain in Which to Install WebAccess
  
  
• Decide Which HTML Page to Use as the Default
  
  
• Decide Which Languages to Install
  
  
• Establish the WebAccess Agent's Network Access

Understand the GroupWise WebAccess Components

GroupWise WebAccess consists of two main components: the GroupWise WebAccess CGI Extension and the GroupWise WebAccess Agent. These components work in conjunction with users' Web browsers, a CGI-compatible HTTP Server, and the GroupWise system to enable users to access their GroupWise mailboxes.

GroupWise WebAccess CGI Extension Module
The GroupWise WebAccess CGI Extension module consists of the CGI Extension (GWWEB), HTML template files, and Java** applets. The CGI Extension merges GroupWise system information into the HTML template files and Java applets to display GroupWise information in the users' Web browsers.

For example, when a user clicks the GroupWise mailbox button in his or her Web browser, the CGI Extension receives a request (through the HTTP Server) to list the user's mailbox messages. The CGI Extension encrypts the request and passes it to the GroupWise WebAccess Agent. The GroupWise WebAccess Agent returns the requested information (in this case, the message list) to the CGI Extension, which merges the information into the mailbox HTML template and updates the mailbox page in the user's browser.

GroupWise WebAccess Agent Module
The GroupWise WebAccess Agent (GWINTER) receives WebAccess user requests from the CGI Extension (GWWEB), converts the request from HTML format to the GroupWise format, and then accesses the user's post office to complete the request. If the request requires information to be displayed in user's browser (such as the list of messages in the user's mailbox) the GroupWise WebAccess Agent converts the information to HTML, encrypts it, and sends it to the CGI Extension.

Java Spell Check Server
The Java Spell Check Server is an optional component that is installed with the GroupWise WebAccess CGI Extension module. The Java Spell Check Server enables WebAccess users to spell check their messages before sending them. Only users who are using the Java-enhanced version of GroupWise WebAccess can use the Java Spell Check Server. The Spell Check Server does not work with the HTML 3 version of GroupWise WebAccess.

Web Browser Support
GroupWise WebAccess requires an HTML 3 compatible Web browser (to support frames). In addition to standard sending and receiving of mail and appointments, GroupWise WebAccess provides the following:

• Busy search (searching of other GroupWise users' Calendars for free appointment times)
• Document management library search and file downloads
• File attachments
• Shared folder viewing
• Query folder viewing

GroupWise WebAccess also uses Java technology. Users who have a Java-enabled Web browser can take advantage of the following additional functionality:

• Spell check
• Address Book accumulator for convenience in addressing multiple recipients
• Calendar month view
• Appointment scheduling through the Calendar day view
• Internet location sending and viewing

Meet GroupWise System Requirements

Your GroupWise system must meet the following requirements:

• It must consist of at least one domain and post office.
• The domain in which you install GroupWise WebAccess must be running the GroupWise agents, version 5.2.

Decide Where to Install the WebAccess Agent and CGI Extension

The primary configuration for GroupWise WebAccess involves two network servers, one for the HTTP Server, GroupWise WebAccess CGI Extensions, and Java Spell Checker Server, and a second for the GroupWise WebAccess Agent. The two-server configuration can support enhanced data security by means of a firewall located between the two servers. The following diagram shows this configuration.

If GroupWise WebAccess will be used on an intranet only, or if security is not a concern, you can use a one-server configuration, as shown below.

The one-server configuration requires a NetWare* server or a Windows NT** server. You cannot use a UNIX** server in a one-server configuration because the WebAccess Agent is available for NetWare and Windows NT only.

WebAccess Agent Requirements
The WebAccess Agent is available as a NetWare NLM* or a Windows NT executable. It must be run on a network server that meets the following requirements:

WebAccess CGI Extension Requirements
The WebAccess CGI Extension is available as a NetWare NLM, Windows NT executable, or UNIX executable. It must be run on a network server that meets the following requirements:

Select a Domain in Which to Install WebAccess

GroupWise WebAccess uses a domain directory for its administration files and message processing directories.

If you have a multiple domain system, you need to decide which domain you want to install WebAccess in. With most GroupWise gateways, it is usually best to install the gateway in the domain where it will be most used. Doing so reduces the amount of cross-domain traffic the Message Transfer Agent has to handle.

Because the WebAccess Agent accesses each post office itself rather than routing requests through the Message Transfer Agent, additional workload for the Message Transfer Agent is not an issue. The main consideration is the WebAccess Agent's network access to the domain directory. The WebAccess Agent requires direct access (UNC path or mapped drive) to the domain directory.

WebAccess Gateway Home Directory

The WebAccess Install program creates a subdirectory in the <DOMAIN>\WPGATE directory. This subdirectory, called the WebAccess gateway home directory, contains the WebAccess administration files, message processing directories, work directories, and log file directories. For example, using the default directory name, the Install program would create the <DOMAIN>\WPGATE\WEBACC5 directory.

Decide Which HTML Page to Use as the Default

The GroupWise Install program installs the GroupWise WebAccess home page. You can choose to have this page replace your HTTP Server's current default HTML page, or you can retain your current page and create a link to the WebAccess page.

On a NetWare HTTP Server, the WebAccess page is named INDEX.HTM. If you choose to use the WebAccess page as the default HTML page, the Install program replaces the current INDEX.HTM file in the <WEB>\DOCS directory with the WebAccess INDEX.HTM file. The old INDEX.HTM is copied to INDEX.001.

If you choose to retain your current INDEX.HTM file, the WebAccess page (INDEX.HTM) is copied to the <WEB> directory.

On a Windows NT HTTP Server, the WebAccess page is named DEFAULT.HTM. If you choose to use the WebAccess page as the default HTML page, the Install program replaces the current DEFAULT.HTM file in the WWWROOT directory with the WebAccess DEFAULT.HTM file. The old DEFAULT.HTM is copied to DEFAULT.001.

If you choose to retain your current DEFAULT.HTM file, the WebAccess page (INDEX.HTM) is copied to the WWWROOT directory.

On a UNIX HTTP Server, the WebAccess page is named index.html. If you choose to use the WebAccess page as the default HTML page, the Install program replaces the current index.html file in the docs (or htdocs) directory with the WebAccess index.html file. The old index.html is copied to index.001.

If you choose to retain your current index.html file, the WebAccess page (INDEX.HTM) is copied to the docs (or htdocs) directory.

Decide Which Languages to Install

The GroupWise CD contains multiple language versions of WebAccess. If you have users who need to use different languages, you can install multiple languages. When you install multiple languages, the GroupWise WebAccess page displays the available languages. Users then select the language in which they want to view the WebAccess client.

The languages you can install depend on which language version of the GroupWise CD you have.

Note: The NLM WebAccess CGI Extension supports a maximum of four languages. Do not install more than four languages.

Establish the WebAccess Agents Network Access

The WebAccess Agent requires network access to the following locations:

• The domain directory for the domain where you will install the GroupWise WebAccess administration files.
• The post office directory (or Post Office Agent) for each post office that contains users who will use GroupWise WebAccess.
• The server where the WebAccess CGI Extension are located.

The following diagram illustrates the required network access.

Domain Directory
The WebAccess Agent needs direct access (UNC path or mapped drive) to the domain directory. The domain directory contains the domain database from which the WebAccess Agent reads the GroupWise system information it needs. The domain directory also contains the subdirectories that the WebAccess Agent uses for message processing.

You should create a network account that provides the WebAccess Agent with access to the domain directory and its subdirectories. The account must provide the following rights (or equivalent rights) to the directories:

• Read
• Write
• Create
• Modify
• Erase
• File Scan

If you are using the NetWare NLM WebAccess Agent, you should create one account that gives it rights to the domain directory and to the post office directories discussed below.

If you are using the Windows NT WebAccess Agent, the account you use to log in from the Windows NT server should provide the WebAccess Agent with the rights to the domain directory and to the post office directories discussed below.

Post Office Directories
The WebAccess Agent needs direct access (UNC path or mapped drive) or client/server access (TCP/IP) to each post office that contains users who will use GroupWise WebAccess.

If you want the WebAccess Agent to use direct access to a post office, you should make sure the network account used to access the domain directory also provides the WebAccess Agent with access to the post office directory and its subdirectories. The account should provide the following rights to the post office directories:

• Read
• Write
• Create
• Modify
• Erase
• File Scan

With client/server, the WebAccess Agent communicates with the Post Office Agent running against the post office. The Post Office Agent then accesses the post office directory. If you want the WebAccess Agent to use client/server to access a post office, the server on which the Post Office Agent is running must support TCP/IP.

IMPORTANT: By default, the WebAccess Agent looks for the NGWNAMESERVER host in DNS to find the IP address of the Post Office Agent. If you are running the WebAccess Agent on a NetWare server and have defined a NGWNAMESERVER host in DNS, you must have NETDB.NLM loaded on the NetWare server. NETDB.NLM enables the WebAccess Agent to access DNS and resolve the address. For information about setting up the NGWNAMESERVER host in DNS, search for name server (GroupWise POA) in NetWare Administrator Help.

If you are not using a NGWNAMESERVER and want the WebAccess Agent to use client/server to access a post office, you can edit the post office link (once you have installed GroupWise WebAccess) and enter the IP address of the Post Office Agent (or the host name if you have defined them in the SYS:ETC\HOSTS file). For information, see Modify the WebAccess Agent's Links to Post Offices in Chapter 4: Maintain the WebAccess Agent.

You can use a combination of direct access and client/server access. The WebAccess Agent may use direct access for some post offices and client/server access for others. In addition, the WebAccess Agent supports the use of both access methods for the same post office. If both access methods are enabled, the WebAccess Agent first tries client/server access. If client/server access is not available, it then tries direct access.

Installation Worksheet

The GroupWise WebAccess Install program installs the GroupWise WebAccess CGI Extension and GroupWise WebAccess Agent to the appropriate locations. To do so, it prompts you for the information listed in the following worksheet (in the order listed). Use the worksheet to prepare for the installation.

* Novell trademark. **Third-party trademark. For more information, see Trademarks.