GroupWise Webaccess/Monitor Application Setup Script to Assist in OES2 / SLES 10 upgrade

  • 3624780
  • 11-Jan-2008
  • 30-Apr-2012

Environment


Novell GroupWise WebAccess 7
Novell Open Enterprise Server (Linux based)
Novell SUSE Linux Enterprise Server 10

Situation

To assist in the setup of GroupWise 7.0 Webaccess and Monitor Applications on SLES 10 and OES2 for Linux, a script has been made available for download.

Resolution

When you upgrade your Linux operating system, OES 2 installs new versions of Apache and
Tomcat by default. SLES does not; you must install them manually by following the procedure in
this section. In addition, the GroupWise 7 installations of the WebAccess Application and the
Monitor Application must be modified to accommodate changes made in Apache and Tomcat. The
WebAccess/Monitor Update script takes care of this process for you.

1 If you have upgraded to SLES 10, use YaST to install Apache and Tomcat if they were not
already installed on SLES 9:

1a Start YaST, then provide the root password.
1b Click Software Management.
1c In the Search field, type Apache, click Search, then select apache2 from the list.
1d In the Search field, type Tomcat, click Search, then select tomcat5 from the list.

Apache 2 was part of your SLES 9 installation, so it should have been automatically
upgraded. Tomcat changed from Tomcat 4 to Tomcat 5, so unless Tomcat 5 was installed
on SLES 9, Tomcat 5 needs to be installed.

1e Click Accept.
1f Follow the prompts to install the needed packages to your SLES 10 server.
1g Exit YaST.

2 Download the WebAccess/Monitor Update script
3 Change to the directory where you downloaded the script file.
4 Give the script file execute permissions:
chmod +x fixgwweb.sh
5 Run the script.

The script makes some slight reconfigurations of GroupWise files and directories that were
originally set up when the WebAccess Application and the Monitor Application were installed
on your previous version of Linux.

*Apache 2: On OES 1 and SLES 9, Apache 2 used the mod_jk connector to facilitate
communication between Apache and Tomcat. On OES 2 and SLES 10, Apache 2 uses the
mod_proxy module instead. The WebAccess/Monitor Update script modifies the
gw.conf file with this change. On SLES 10, the script also creates a symbolic link from
/etc/opt/novell/gw/gw.conf to the new Apache 2 location of /etc/
apache2/conf.d/gw.conf.

*Tomcat 5: On OES 1 and SLES 9, the WebAccess /var/opt/novell/gw directory
was linked to /var/opt/novell/tomcat4/webapps/gw. The script changes this
link to /var/opt/novell/tomcat5/webapps/gw. For Monitor, the /var/opt/
novell/gwmon directory now links to/var/opt/novell/tomcat5/webapps/
gwmon.

6 Start or restart Tomcat.
7 Start or restart Apache.
8 If you are upgrading to OES 2:
You might receive the following message when starting Apache 2:
Module "Jk" is not installed, ignoring.
You can safely ignore this message, but if you want to eliminate it:

8a Start YaST, then provide the root password.
8b Click NetWork Services > HTTP Server.
8c On the Server Modules tab, select the jk module in the list of services, then toggle the
status to Off.
8d Click Finish to save your change.
8e Exit YaST.

You should now be able to run WebAccess and Monitor successfully on your upgraded Linux
operating system.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.