17.7 Updating GroupWise WebAccess

After you’ve updated your domains and post offices, you can update GroupWise WebAccess. For information about update issues you should consider, see Section 15.6, Understanding WebAccess Updates.

For information about installing GroupWise 8 WebAccess, see Section 5.0, Installing GroupWise WebAccess.

After installing GroupWise 8 WebAccess, complete the following tasks as needed for your system:

17.7.1 Clearing Browser Caches

After you have updated the WebAccess software, notify your WebAccess client users that they should clear their browser caches before logging into their mailboxes with the updated WebAccess client. If old WebAccess files are pulled from users’ browser caches, they might not be compatible with the updated files pulled from the Web server. The results can be unpredictable and undesirable.

17.7.2 Handling New URLs for WebAccess and Monitor

Prior to GroupWise 7, users of WebAccess accessed the following URLs on NetWare and Windows Web servers:

Web Services page:

Default index.html file of the Web server





Starting with GroupWise 7, the WebAccess URLs on NetWare and Windows Web servers are the same as the URLs used on Linux:

GroupWise-specific Web Services page:






To keep users’ browser bookmarks from being broken when you update from a version of GroupWise earlier than GroupWise 7, you should redirect the old URLs to the new URLs. Follow the instructions below for your Web server.

Apache Web Server

  1. Change to the conf subdirectory of the Apache root directory (for example, \apache2\conf.

  2. Edit the Apache configuration file (gwapache2.conf) for GroupWise.

  3. Add the following line:

    redirect permanent /servlet/webacc http://web_server_address/
  4. If you use WebPublisher, add the following additional line:

    redirect permanent /servlet/webpub http://web_server_address/
  5. Save the file, then exit the editor.

  6. Restart Apache to put the redirections into effect.

Internet Information Server (IIS)

  1. Change to the inetpub\wwwroot subdirectory of the IIS root directory (for example, c:\inetpub\wwwroot)

  2. Create a subdirectory named servlet.

  3. Under the servlet subdirectory, create a subdirectory named webacc.

  4. If you use WebPublisher, create a second subdirectory named webpub.

  5. In IIS Manager, expand the tree in the left pane to display Default Web Site under Web Sites.

    Under Default Web Sites, you should see the servlet subdirectory you created in Step 2.

  6. Expand the servlet subdirectory to display the webacc subdirectory (and optionally, the webpub subdirectory) that you created in Step 3.

  7. Right-click the webacc subdirectory, then click Properties.

  8. Click Directory, select A Redirection to a URL, then type /gw/webacc in the associated field.

  9. Select A Permanent Redirection for This Resource, then click OK to save your changes.

  10. If you use WebPublisher, repeat Step 7 through Step 9, using webpub in place of webacc.

  11. Restart the IIS Web server to put the redirections into effect.

17.7.3 Cleaning Up Obsolete Web Server Files

As part of the change from /servlet/webacc to /gw/webacc in GroupWise 7, the WebAccess Installation program installs the WebAccess Application files into the servlet container (gw) but it does not remove old servlet and htdoc files located under the ROOT container of the servlet and the Web server. Therefore, you might want to manually delete the following directories and files if you are updating from a version of GroupWise earlier than GroupWise 7:

sys:\apache2\htdocs\index.html (if customized for GroupWise)
sys:\apache2\htdocs\novell.html (if index.html was not customized)

You should definitely delete web.xml, because it might cause the WebAccess, WebPublisher, and Monitor Applications to run in both the old and new locations. Also, if you have customized the GroupWise template files, you should copy the contents of the template subdirectories under:


to the corresponding templates subdirectories under:


17.7.4 Document Viewer Agent Cache Compatibility

The Document Viewer Agent was introduced in GroupWise 7. The cache created by the Document Viewer Agent is not compatible with the cache previously used with WebPublisher. If you are updating from a version earlier than GroupWise 7, old WebPublisher cache directories should be removed from servers where the Viewer Agent is installed.