Novell GroupWise 7.0x
OES Linux 2.0
your OES server, you encounter package conflicts that must be resolved. In addition, when you
upgrade from OES 1 to OES 2 to on a server where GroupWise WebAccess is installed, the
WebAccess Application must be reinstalled and reconfigured for use on OES 2. After upgrading
from OES 1 to OES 2, the stand-along GroupWise Check (GWCheck) program cannot be run on the
same server where ConsoleOne runs because they use different versions of the JRE.
Resolving Conflicts During the Upgrade Process
When you upgrade from Open Enterprise Server (OES) 1 to OES 2 with GroupWise installed on
your OES server, a pop-up message appears right before the Installation Settings screen. The pop-up informs you that the Delete Unmaintained Packages option is selected. OES 2 considers GroupWise an "unmaintained package.â This means that, by default, your GroupWise software will be deleted as part of the upgrade process, unless you follow the instructions below.
1 Read the pop-up warning carefully, then click OK to close the pop-up.
The pop-up describes three possible actions you can take to resolve the fact that GroupWise is
an unmaintained package. This procedure steps you through the second of the three possible
actions. This alternative works most efficiently for preserving your GroupWise installation.
2 If ConsoleOne is installed on the server: The following message displays below the Packages link on the Installation Settings screen:
Cannot solve all conflicts. Manual intervention is required.
2a Click the Packages link.
The upgrade process checks for package conflicts, then lists one or more package-related
error messages, providing you with alternatives of how to handle each conflict. The
specific messages you receive depend on the the packages installed on the server you are
upgrading. Therefore, messages vary. Here are some examples:
NOVLc1-1.3.6-1.i386 is locked and cannot be uninstalled.
NOVLc1-1.3.6-1.i386 cannot be installed due to missing dependencies.
novell-eguide-2.1.32.noarch cannot be installed due to missing dependencies.
The messages fall into three basic categories of problems:
A locked package
Missing dependencies for ConsoleOne (the NOVLc1 pachage)
Missing dependencies for some other product package besides ConsoleOne
The following steps help you decide which action to take for each type of message.
2b If the message indicates a locked package, select Unlock All Resolvables.
2c If the message indicates missing dependencies for ConsoleOne (NOVLc1), select Ignore
This Requirement Just Here.
2d If the message indicates missing dependencies for some other product package besides
ConsoleOne, and you are sure that you do not want that product package, select Delete
NOTE: How to handle packages besides ConsoleOne that you want to keep are beyond
the scope of these instructions.
2e When you have selected an action for each conflict message, click OK - Try Again.
The upgrade process checks again for conflicts for NOVLc1. Additional messages might
be displayed for you to select actions to resolve the conflicts. This cycle repeats until all
conflicts have been resolved, then you successfully reach the Packages page.
3 On the Packages page, select Search in the Filter field.
4 Search for the GroupWise packages that are installed on the server by typing the following in
the Search field:
then click Search.
Depending on what GroupWise components are installed on the server, the search results
include some of the following packages:
5 Right-click the first GroupWise package in the list, then click All in This List > Keep.
This changes the status of each GroupWise package from Delete to Keep.
6 Search for the NOVLc1 package, then set its status to Keep.
7 If the NOVLc1Linuxjre package is listed along with the NOVLc1 package, set its status to
NOTE: Deleting this JRE package enables ConsoleOne to run on OES 2. However, it also
prevents GroupWise Check from running on the same server where ConsoleOne runs. This
discrepancy will be corrected in the next release of GroupWise.
8 Click Accept on the Packages page.
9 If you are presented with a font License Agreement, click Accept.
10 Click Continue to return to the Install Settings page.
11 Verify that the package conflict message is now gone from under the Packages link, then
continue with the upgrade process.
Reinstalling the WebAccess Application after the Upgrade Process
When you upgrade from OES 1 to OES 2, new versions of Apache and Tomcat are installed.
Therefore, you must reinstall and reconfigure the WebAccess Application. However, you do not
need to reinstall the WebAccess Agent.
GroupWise Check (GWCheck)
After upgrading to OES 2, GroupWise Check cannot be run on the same server where ConsoleOne
runs due to conflicting JRE requirements. This discrepancy will be corrected in the next release of
GroupWise. As a workaround, you can use the Mailbox/Library Maintenance feature of ConsoleOne
to perform the same database maintenance activities.