Difference between revisions of "VIBE Interface Settings"
(→Level 2) |
|||
| (2 intermediate revisions by one user not shown) | |||
| Line 12: | Line 12: | ||
== 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 20: | Line 22: | ||
| − | Here are instructions when doing a remote scanner: | + | '''Here are instructions when doing a remote scanner:''' |
| + | |||
| + | '''Configure Vibe''' | ||
| − | + | '''1.''' Download and copy the following file to the <tomcat>/lib/custom-ext/ folder: | |
| − | 1. Download and copy the following file to the <tomcat>/lib/custom-ext/ folder: | + | |
teamGwava.jar | teamGwava.jar | ||
| − | 2. Edit the <tomcat>/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties file and add the following lines to the end of the file. | + | '''2.''' Edit the <tomcat>/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties file and add the following lines to the end of the file. |
* These lines may already exist and should have the gwava entry inserted before the current value. | * These lines may already exist and should have the gwava entry inserted before the current value. | ||
# gwava.teaming interface settings | # gwava.teaming interface settings | ||
Latest revision as of 17:03, 19 June 2014
[edit] Level 1
Bypass message scanning - Bypass scanning of items that are created by Vibe.
Maximum scan threads - The number of threads to use to scan items sent by Vibe.
Scanner timeout - The timeout that will be used to connect to GWAVA.
[edit] Advanced Clustering Options
Server Address: - The address of GWAVA if 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.
Here are instructions when doing a remote scanner:
Configure Vibe
1. Download and copy the following file to the <tomcat>/lib/custom-ext/ folder:
teamGwava.jar
2. Edit the <tomcat>/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties file and add the following lines to the end of the file.
* These lines may already exist and should have the gwava entry inserted before the current value.
# gwava.teaming interface settings
file.content.filter.classes=com.gwava.teaming.GwavaContentFilter,org.kablink.teaming.module.file.impl.XSSContentFilter *
servlet.context.listener.classes=com.gwava.teaming.GwavaContextListener *
module.event.listeners.org.kablink.teaming.module.folder.FolderModule=com.gwava.teaming.GwavaModuleListener *
module.event.listeners.org.kablink.teaming.module.binder.BinderModule=com.gwava.teaming.GwavaModuleListener *
gwava.teaming.reference.id=19n6uhr.19pmbfu.103
# set username and password for gwava.teaming remote mode
gwava.teaming.gwavaman.address=10.1.1.109:49282
gwava.teaming.gwavaman.username=wsvibe_scann
gwava.teaming.gwavaman.password=EA60C92B90
gwava.teaming.tomcat.user=wwwrun
gwava.teaming.tomcat.group=www
