WASP Interface Settings

Level 1

Bypass message scanning - Disable scanning of messages.

Maximum scan threads - The maximum number of threads that WASP will use to scan.

Scanner timeout - The timeout that WASP uses to talk to GWAVA.

GroupWise version - The version of GroupWise that WASP is configured to work with.

Advanced File System Options

Tomcat User - The user that tomcat uses to run Webaccess.

Tomcat Group - The group that tomcat is a part of.

Advanced Clustering Options

Server Address - The address of GWAVA when running in a clustered environment.

Level 2

Bypass message scanning - This is off by default.

Maximum scan threads - The default is set to 16, these can be increased if needed. Before increasing these make sure the server is able to handle the amount it is set to.

Scanner timeout - This is set to 3 by default.

Advanced File System Options

OES Linux users, need to set the proper Linux user and group for your version of Tomcat:

    (For OES this will need to be changed to novlwww.)
    (For OES2 this will need to be changed to wwwrun for the user and www for the group.) 

Instructions on how to restart Tomcat which will reload WebAccess:

    WebAccess NetWare Restart Instructions:
    To restart the WebAccess application, go to the console screen and type 'tc4stop.ncf'. Then to reload WebAccess type 'tomcat4.ncf'.

    WebAccess Linux Restart Instructions:
    To restart the WebAccess application, open a shell prompt with root privileges and type 'rctomcat restart' or 'rctomcat5 restart'. 
    For OES type 'rcnovell-tomcat4 restart', for OES2 type 'rcnovell-tomcat5 restart'.

    WebAccess Windows Restart Instructions:
    To restart the WebAccess application, run 'services.msc' and stop and start the Tomcat 5 service.