Installing the GWAVA package
From GWAVA4
Contents |
System Requirements
GroupWise
The following GroupWise environments are supported:
- GroupWise 6.5.6, 7.0.1 [NetWare, Windows]
- GroupWise 7.0.1 with FTF or newer [Linux]
- NOTE: The FTF is needed for the MTA scanner. For other scanners, GroupWise 7.0.1 will be fine
Server Operating System
Any of the following operating systems are supported:
- NetWare 5.1 SP8
- NetWare 6.5 SP5
- SusE Linux Enterprise Server 9 SP3
- Open Enterprise Server (Linux) SP2
- Open Enterprise Server (NetWare) SP2
- Windows 2000 Server SP4
- Windows 2003 Server SP1
General Server Requirements:
- In addition to existing server memory requirements, an additional 512 MB is required. 1 GB preferred.
- CPU requirements depend on mail quantities. GWAVA requires the CPU to comfortably handle the existing mail flow prior to installation.
- Around 65 megabytes of disk space for initial install. Reserve at least an additional 200 megabytes for growth and diagnostic logs. and if using the QMS (Quarantine Management System) for quarantining, many gigabytes may be necessary depending on e-mail traffic.
Web Browsers
GWAVA 4 administration and usage is all web based. GWAVA 4 has been tested and is supported on the following web browsers:
- Internet Explorer 6.0, 7.0
- Firefox 1.5.x, 2.x
Other browsers may function correctly, but are currently unsupported.
Installation
Download and decompress your GWAVA package. For NetWare and Windows, this is provided as a self extracting EXE package. For Linux, a standard tarball (gzipped tar file) is provided. In both KDE and GNOME you can right click on the item and choose to extract the contents; or for command line purists, tar -xzf (tarballname) will do the trick
From KDE or GNOME, click on the GWAVAInstall.sh file. From the command line, ./menu.sh will achieve the same goal.
You'll be presented with a set of choices.
- Install/Uninstall the core GWAVA package - As the title implies, all of the core programs required to run GWAVA are (un)installed.
- Update KAV - Lets you manually configure the KAV (Kaspersky Antivirus) HTTP proxy settings, and force an automatic update of the signature files.
- View the installation log - Allows you to view the log of all installs/uninstalls.
You may use this system to upgrade an older GWAVA system. Uninstall and then install the core GWAVA package.
Core Package Installation
This consists of installing the gwavaman RPM package (rpm -i), which:
- Copies the GWAVA program files to /opt/beginfinite/gwava. (Whenever you see documentation referring to the productRoot, it is referring to this location).
- Installs the gwavaman INIT script to /etc/init.d, and modifies /etc/init.d/grpwise (if it exists) so gwavaman is preferentially loaded before GroupWise starts and unloaded after GroupWise ends.
- Updates the MTA scanner file, if an MTA scanner was already installed, and warns you to restart the MTA.
- Creates a CRON job in /etc/cron.hourly to run hourly to update KAV virus signatures.
- Starts (or restarts, if already running) the GWAVA program components
After the RPM runs, you will be prompted if you want to configure the KAV HTTP Proxy connection settings. Afterwards, the KAV update process will be started immediately to guarantee maximum protection. This is equivalent to choosing "Update KAV" from the menu system.
Once installation is complete, you can connect to the GWAVA manager (GWAVAMAN) via http://serveripaddress:49282
- TIP: Later, you'll learn how to secure the GWAVAMAN interface for HTTPS connections.
You may also verify that gwavaman and gwava (among other components) are loaded by typing ps -e | grep gw
Core Package Uninstallation
This consists of running the gwavaman RPM package (rpm -e), which:
- Removes most files from /opt/beginfinite/gwava
- Removes the gwavaman INIT script from /etc/init.d, and removes any prior modification to /etc/init.d/grpwise (if it exists). # Warns the administrator if an MTA scanner was previously installed, and instructs you how to remove the MTA component
- Removes the KAV update CRON job from /etc/cron.hourly,
- Stops the GWAVA program components
Note that some programs will be left behind. Specifically log files, or altered configuration files. This is for your convenience to allow easy upgrading. If you truly want a clean uninstall (losing all previous configuration information, data, etc), type rm -rf /opt/beginfinite/gwava from the command line at this point.
- The MTA scanner cannot be fully uninstalled from the command line. If you need to do this:
- Stop the MTA.
- Remove /lib/libgwvsmod.so' and /opt/novell/groupwise/agents/lib/libgwvsmod.so
- Find your startup file and remove the /vscan switch.
- Restart the MTA.
For more information, see Uninstalling GWAVA
Update Kaspersky AntiVirus (KAV)
Normally, it is unnecessary to choose this option, as it was run for you automatically when you installed GWAVA. This is provided as a diagnostic/corrective option if you initially had HTTP connectivity issues.
You are first prompted as to whether you want to change the HTTP Proxy Settings for KAV. Some networks restrict web access via HTTP proxies, and may also require authentication. If you administer one of these networks, answer YES to the next screen
You'll get to set the proxy address, username and password
Regardless of whether you answered Yes or No, the KAV updater is then run and tries to connect to the KAV server to download new updates.
- TIP: You can reconfigure the KAV Proxy Settings manually by typing /opt/beginfinite/gwava/services/kav/bin/configkav.sh.
- TIP: You can force a manual update of the virus signature files by typing /etc/init.d/cron.hourly/updatekav.sh.
- TIP: The log from the previous update attempt is kept in /opt/beginfinite/gwava/services/kav/logs
- TIP: An installation from the menu based system is equivalent to rpm -i gwavaman-<version>.rpm, followed by the manual configuration of KAV Proxy Settings, and a manual update of the KAV virus signatures, each as described in the above TIPS.
- NOTE: If you are clustering your GWAVA system, please see Clustering.
