System RequirementsSystem RequirementsSystemvoraussetzungenSystem RequirementsPré-requis SystèmeSystémové požadavky

    Documents

    Largely, the requirements for all versions of GWAVA are the same.

    System Requirements

    • GWAVA 4 can be deployed on multiple platforms. For NetWare, you must have NetWare 6.5 or later, plus the latest patches. For Linux, you must have SUSE Linux Enterprise Server 10 or OES Linux with the latest patches.
    • GWAVA 4 requires 500 MB on the server. Additional space may be allocated for the Auto-learning capabilities of SmartBlocker. We recommend additional storage space of 20-30 MB per user depending on quarantine settings.
    • Memory usage on the server is about 20 MB without the anti-spam engine, and 60 MB with SmartBlocker active.
    • GWAVA must be installed on the same server as one of the supported GroupWise Components.
    • For MTA Scanning, The GroupWise MTA must be running the latest patched version of GroupWise 7. The GroupWise MTA must be local to its domain. For MTA scanning of older versions of GroupWise (i.e. 5.5e, 6.0 & 6.5) please use GWAVA 3.x.
    • TCP/IP must be installed and configured on the servers running GWAVA even if the MTA is using UNC links to domains.
    • Long filename support must be enabled on NetWare servers with the GWAVA directories.


    We STRONGLY recommend the latest GroupWise patches are applied to your system.

    System Recommendations

    A.

    • 2.4 GHz Pentium 4 processor, 1 Gig RAM, 36Gb hard drive
    • 2,000 mail/hour + 100 concurrent Internet connections
    • 4,000 mail/hour
    • 400 concurrent Internet connections

     

    B.

    • 3.2 GHz Pentium 4 processor, 1. 5 Gb RAM, 40Gb hard drive
    • 4,000 mail/hour + 300 concurrent Internet connections
    • 7,000 mail/hour
    • 600 concurrent Internet connections

     

    C.

    • 3.6 GHz Pentium 4, 2Gb RAM, 60Gb hard drive
    • 8,000 mail/hour + 600 concurrent Internet connections
    • 10,000 mail/hour
    • 900 concurrent Internet connections

    Recommended Settings

    1. Internet Addressing should be enabled. This is set in the Internet Addressing options under GroupWise System Operations in NWADMIN or ConsoleOne. If this is not enabled, GWAVA may not be able to send notification messages to the system administrator (or to other notification recipients).
    2. Your GWIA or SMTP server should be configured to allow relaying of mail messages from the GWAVA server. If relaying is disabled, you can make an exception for GWAVA. Alternatively, GWAVA 2.1 and above support SMTP AUTH, which allows authenticated relaying with GroupWise 6.0 and above.
    3. Set GWAVA subdirectories, as well as all the GWVSCAN directories to Immediate Purge of Deleted Files (a general Novell recommendation for any GroupWise server). This will prevent your GWAVA server from becoming too busy with old files in temporary directories. If you experience an issue with NGW-VSCAN-CONTROLLER errors when unloading or restarting the MTA, this is the issue.
    4. Novell has recently identified a bug in a program file that is essential to GWAVA's functionality called GWMTAVS.NLM. Novell has updated the file; however, you must also apply the GroupWise 5.5 Service Pack FTF in order to take advantage of the updated NLM for GWAVA. GroupWise 6 and above do not require this procedure; the fix is already built in.

      Here is the GWMTAVS.NLM procedure:
      1. Unload the GroupWise agents (POA, MTA)
      2. Rename SYS:SYSTEM\GWMTAVS.NLM
      3. Download and install the following GroupWise 5.5 Agent FTF from Novell at: http://support.novell.com/servlet/tidfinder/2964030
      4. Download and install the Updated GWMTAVS.NLM from Novell at: http://support.novell.com/servlet/tidfinder/2963978
      5. Edit the MTA startup file for the domain and add the following switch indicating the TCP port on which you would like to have the MTA listen for communication from GWMTAVS. At the bottom of the startup file after the other vs switches, add /vsport=7108.
      6. Re-load the GroupWise agents
      7. NOTE: The Agent FTF (in step 3), for Support Pack 3 or later is required to be able to configure the MTA to work with the new virus scan NLM.