After you have upgraded a domain and a post office to GroupWise 18, you can upgrade WebAccess for that domain and post office. For information about upgrade issues that you should consider, see WebAccess Upgrades.
The POA that the GroupWise WebAccess Application communicates with must be configured for SOAP. A secure TLS connection between the POA and the WebAccess Application is highly recommended.
IMPORTANT:Before you upgrade your WebAccess Application, you must upgrade all post offices that connect to your WebAccess Application or users can have issues logging in.
GroupWise 18 requires WebAccess to use TLS. Before you upgrade, you must configure Apache with TLS or WebAccess will not run. After doing that, you can upgrade your WebAccess software whenever it is convenient as you upgrade your GroupWise system. However, in order to use the WebAccess Application console, you must change the way it is configured. For instructions, see Using the WebAccess Application Console
in the GroupWise 18 Administration Guide.
IMPORTANT:If you are upgrading from GroupWise 8 directly to GroupWise 18, you need to understand that the WebAccess Agent is no longer part of GroupWise. See Understanding WebAccess Updates
and Updating GroupWise WebAccess
in the GroupWise 2012 Installation Guide18 before you upgrade WebAccess from GroupWise 8 directly to GroupWise.
(Conditional) If you are upgrading from GroupWise 8:
Prepare the POA to work successfully with the WebAccess Application, as described in the following sections in Post Office Agent
in the GroupWise 18 Administration Guide:
Stop the existing WebAccess Agent.
(Conditional) On Linux, stop Tomcat.
|
|
On Windows, the Installation Wizard does this for you.
To upgrade WebAccess to GroupWise 18, follow the standard installation instructions in Setting Up GroupWise WebAccess (Legacy).
IMPORTANT:If more than one web-based GroupWise component (WebAccess, Calendar Publishing Host, and/or Monitor) is installed on the same server, you must upgrade all web-based GroupWise components at the same time. After one existing web-based component has been upgraded to GroupWise 18, other web-based components on the server do not work until they also are upgraded to GroupWise 18.
Reconfigure the WebAccess Application console.
For instructions, see Enabling the WebAccess Application Console
in the GroupWise 18 Administration Guide.
(Conditional) If you are upgrading from GroupWise 8, complete the steps in Cleaning Up the WebAccess Server after Updating to GroupWise 2012
and Updating Access Control for WebAccess Users
in the GroupWise 2012 Installation Guide.
Continue with Clearing User Browser Caches to Display GroupWise 18 WebAccess Correctly.
After you have upgraded the WebAccess Application to GroupWise 18, notify your GroupWise WebAccess users that they should clear their browser caches before logging into their mailboxes with the upgraded version of GroupWise WebAccess. If old GroupWise WebAccess files are used from users’ browser caches, they might not be compatible with the upgraded files from the web server. The results can be unpredictable and undesirable.