Difference between revisions of "WASP Interface Settings"
(→Level 2) |
|||
| (One intermediate revision by one user not shown) | |||
| Line 20: | Line 20: | ||
== Level 2 == | == Level 2 == | ||
| + | |||
| + | '''''A separate license is required to use this interface.''''' | ||
'''Bypass message scanning''' - This is off by default. | '''Bypass message scanning''' - This is off by default. | ||
| Line 72: | Line 74: | ||
'''Install WASP Application''' | '''Install WASP Application''' | ||
| + | |||
'''1.''' Copy the following files to both the <tomcat>/webapps/gw/WEB-INF/lib and <tomcat>/common/lib (if present on Tomcat version 5 and earlier) folders (refer to the “Tomcat Folder” section below): | '''1.''' Copy the following files to both the <tomcat>/webapps/gw/WEB-INF/lib and <tomcat>/common/lib (if present on Tomcat version 5 and earlier) folders (refer to the “Tomcat Folder” section below): | ||
mail.jar, activation.jar | mail.jar, activation.jar | ||
Latest revision as of 17:04, 19 June 2014
Contents |
[edit] 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.
[edit] Advanced File System Options
Tomcat User - The user that tomcat uses to run Webaccess.
Tomcat Group - The group that tomcat is a part of.
[edit] Advanced Clustering Options
Server Address - The address of GWAVA when running in a clustered environment.
[edit] Level 2
A separate license is required to use this interface.
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.
[edit] 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.
Here are instructions when doing a remote scanner:
GroupWise® 2012
Install WASP Application
1. Copy the following file to the <tomcat>/webapps/gw/WEB-INF/lib folder (refer to the “Tomcat Folder” section below):
wasp2.jar
2. On Linux, set the file permissions for that file to “644” and ownership so that it matches the other WebAccess files in that folder. Configure WASP Application 3. Create a folder named “gwava” in the WebAccess Application home folder (refer to the “WebAccess Application Home Folder” section below). 4. On Linux, set the permissions for that folder to “755” and ownership so that it matches the “logs” folder in that same location. 5. Create a file named “wasp.cfg” in the new gwava folder that contains the following:
WebAcc.Plugin.wasp=com.gwava.wa.provider.wasp.WaspProvider
Provider.Wasp.gwavaman.address=10.1.1.109:49282 Provider.Wasp.gwavaman.username=wswasp_scan Provider.Wasp.gwavaman.password=EA61C235A5 Provider.Wasp.reference.id=19n6uhr.19pmbfu.1ee 6. On Linux, set the permissions for that file to “644” and ownership so that it matches the new “gwava” folder. Restart WebAccess 7. The GroupWise WebAccess application needs to be restarted for the WASP scanner to become active.
GroupWise® 8
Install WASP Application
1. Copy the following files to both the <tomcat>/webapps/gw/WEB-INF/lib and <tomcat>/common/lib (if present on Tomcat version 5 and earlier) folders (refer to the “Tomcat Folder” section below):
mail.jar, activation.jar
2. Copy the following files to the <tomcat>/webapps/gw/WEB-INF/lib folder:
gwava.jar, wasp.jar
3. On Linux, set the file permissions for those files to “644” and ownership so that they match the other WebAccess files in those folders. Configure WASP Application 4. Create a folder named “gwava” in the WebAccess Application home folder (refer to the “WebAccess Application Home Folder” section below). 5. On Linux, set the permissions for that folder to “755” and ownership so that it matches the “logs” folder in that same location. 6. Create a file named “wasp.cfg” in the new gwava folder that contains the following:
Provider.GWAP.class=com.gwava.wa.provider.gwava.GwavaProvider
Provider.Wasp.gwavaman.address=10.1.1.109:49282 Provider.Wasp.gwavaman.username=wswasp_scan Provider.Wasp.gwavaman.password=EA61C235A5 Provider.Wasp.reference.id=19n6uhr.19pmbfu.1ee 7. On Linux, set the permissions for that file to “644” and ownership so that it matches the new “gwava” folder. 8. Rename the file install_top_n.png in the <tomcat>/webapps/gw/webaccess/<build>/images folder to “install_top_n.png.bak”. 9. Copy the file install_top_n.png to that folder. 10. On Linux, set the permissions for that file to “644” and ownership so that it matches the other files in that folder. Restart WebAccess 11. The GroupWise WebAccess application needs to be restarted for the WASP scanner to become active.
GroupWise® 7
Install WASP Application
1. Copy the following files to both the <tomcat>/webapps/gw/WEB-INF/lib and <tomcat>/common/lib (if present on Tomcat version 5 and earlier) folders (refer to the “Tomcat Folder” section below):
mail.jar, activation.jar
2. Copy the following files to the <tomcat>/webapps/gw/WEB-INF/lib folder:
gwava.jar, wasp.jar
3. On Linux, set the file permissions for those files to “744” and ownership so that they match the other WebAccess files in those folders. Configure WASP Application 4. Edit the WebAccess configuration file (webacc.cfg) on the WebAccess server (refer to the “WebAccess Application Home Folder” section below):
a. Insert a “#” character at the beginning of the line:
“Provider.GWAP.class=com.novell.webaccess.providers.gwap.XGWAP”
b. Add a new line:
“Provider.GWAP.class=com.gwava.wa.provider.gwava.GwavaProvider”
c. Add the following lines to the bottom of the file:
Provider.Wasp.gwavaman.address= Provider.Wasp.gwavaman.username= Provider.Wasp.gwavaman.password= Provider.Wasp.reference.id= 5. Rename the files splash.png and splash-02.png in the <tomcat>/webapps/gw/com/novell/webaccess/images folder to “splash.png.bak” and “splash-02.png.bak” 6. Copy the files splash.png and splash-02.gif to that folder. Restart WebAccess 7. The GroupWise WebAccess application needs to be restarted for the WASP scanner to become active.
Tomcat Folder Default locations are: Linux Tomcat 6 on SLES 10/11 /usr/share/tomcat6 Tomcat 6 on OES 11 /var/opt/novell/tomcat6 Tomcat 5 on SLES 10 /usr/share/tomcat5 Tomcat 4 on OES 2 /var/opt/novell/tomcat4 Tomcat 4 on SLES 9/OES /srv/www/tomcat NetWare SYS:\tomcat\5.0 SYS:\tomcat\4 Windows GroupWise 2012 C:\Novell\tomcat6 GroupWise 8 C:\Novell\GroupWise\tomcat5.5 GroupWise 7 C:\Novell\tomcat5.5
WebAccess Application Home Folder: This is where the WebAccess configuration file, webacc.cfg, is located. The default locations are: Linux GroupWise 8/2012 /var/opt/novell/groupwise/webaccess GroupWise 7 /opt/novell/groupwise/webaccess NetWare GroupWise 8 SYS:\novell\groupwise\webaccess GroupWise 7 SYS:\novell\webaccess Windows GroupWise 8/2012 C:\Novell\GroupWise\WebAccess GroupWise 7 C:\Novell\WebAccess
