Difference between revisions of "GMS Interface Settings"
(Created page with "'''Interface ID''' - Database Interface ID. '''Username''' - The Username that is used to authenticate to GWAVAMAN. '''Password''' - The password for the Username that is us...") |
|||
(One intermediate revision by one user not shown) | |||
Line 1: | Line 1: | ||
+ | == Level 1 == | ||
+ | |||
'''Interface ID''' - Database Interface ID. | '''Interface ID''' - Database Interface ID. | ||
Line 12: | Line 14: | ||
The bottom of this page also include the instructions on setting up GMS to integrate with GWAVA. | The bottom of this page also include the instructions on setting up GMS to integrate with GWAVA. | ||
+ | |||
+ | == Level 2 == | ||
+ | |||
+ | '''''A separate license is required to use this interface.''''' | ||
+ | |||
+ | '''Prerequisites:''' | ||
+ | |||
+ | Novell GroupWise Mobility Service 2.0.1 or above | ||
+ | |||
+ | |||
+ | '''Post install:''' | ||
+ | |||
+ | Enable and configure Novell GroupWise Mobility Service | ||
+ | |||
+ | '''To enable scanning integration with the Novell GroupWise Mobility Service, perform the following three steps on the GMS server:''' | ||
+ | |||
+ | '''1. Enable GWAVA scanning integration within the Novell GroupWise Mobility Service''' | ||
+ | |||
+ | Currently the GWAVA scanning integration is available as a preview feature. To enable this feature you must do the following: | ||
+ | |||
+ | Change to the /opt/novell/datasync directory and execute this command: | ||
+ | |||
+ | ./previewfeature.sh -a enable --gwava | ||
+ | |||
+ | '''2. Configure GroupWise Mobility Service to connect to GWAVA for message scanning''' | ||
+ | |||
+ | The GroupWise Mobility Service settings that need to be set are: | ||
+ | |||
+ | <gwava_enable> (1 enables Gwava Scanning integration, 0 disables it) | ||
+ | <gwava_url> (the URI to connect to the GWVAPI service) | ||
+ | <gwava_user> (the login name used to authenticate to the GWVAPI service) | ||
+ | <gwava_pass> (the password used to authenticate to the GWVAPI service) | ||
+ | <gwava_realm> (the realm used to authenticate to the GWVAPI service) | ||
+ | <gwava_interface> (the ID of the interface to be used for the scanning service) | ||
+ | |||
+ | Edit the following GroupWise Mobility Service configuration file: | ||
+ | |||
+ | /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/mobility/connector.xml | ||
+ | |||
+ | Add or replace the following entries: | ||
+ | |||
+ | <gwava_enable>1</gwava_enable> | ||
+ | <gwava_url>http://0.0.0.0/GwavaAPI/v1/scanner/</gwava_url> | ||
+ | <gwava_user>apigms_scan</gwava_user> | ||
+ | <gwava_pass>D13AA10E81</gwava_pass> | ||
+ | <gwava_realm>GWAVA Console</gwava_realm> | ||
+ | <gwava_interface>19n6uhr.19pmbfu.1ss</gwava_interface> | ||
+ | |||
+ | '''3. Finally, save the file and restart the GMS service to load the new configuration settings''' | ||
+ | |||
+ | '''Now Novell GroupWise Mobility Service can connect to the GWAVA system for scanning.''' | ||
+ | |||
+ | '''WARNING! There can only be one instance of each of these settings in the connector.xml file! The connector.xml file can have the order scrambled. If this file has been modified previously with GWAVA information, ensure that only one instance of each of the settings exists.''' |
Latest revision as of 17:10, 19 June 2014
[edit] Level 1
Interface ID - Database Interface ID.
Username - The Username that is used to authenticate to GWAVAMAN.
Password - The password for the Username that is used to authenticate to GWAVAMAN.
Realm - The Realm that GWAVA will use to communicate with GMS.
Scan Inbound Traffic - Scan mail sent to a device.
Scan Outbound Traffic - Scan mail sent from a device.
The bottom of this page also include the instructions on setting up GMS to integrate with GWAVA.
[edit] Level 2
A separate license is required to use this interface.
Prerequisites:
Novell GroupWise Mobility Service 2.0.1 or above
Post install:
Enable and configure Novell GroupWise Mobility Service
To enable scanning integration with the Novell GroupWise Mobility Service, perform the following three steps on the GMS server:
1. Enable GWAVA scanning integration within the Novell GroupWise Mobility Service
Currently the GWAVA scanning integration is available as a preview feature. To enable this feature you must do the following:
Change to the /opt/novell/datasync directory and execute this command:
./previewfeature.sh -a enable --gwava
2. Configure GroupWise Mobility Service to connect to GWAVA for message scanning
The GroupWise Mobility Service settings that need to be set are:
<gwava_enable> (1 enables Gwava Scanning integration, 0 disables it) <gwava_url> (the URI to connect to the GWVAPI service) <gwava_user> (the login name used to authenticate to the GWVAPI service) <gwava_pass> (the password used to authenticate to the GWVAPI service) <gwava_realm> (the realm used to authenticate to the GWVAPI service) <gwava_interface> (the ID of the interface to be used for the scanning service)
Edit the following GroupWise Mobility Service configuration file:
/etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/mobility/connector.xml
Add or replace the following entries:
<gwava_enable>1</gwava_enable> <gwava_url>http://0.0.0.0/GwavaAPI/v1/scanner/</gwava_url> <gwava_user>apigms_scan</gwava_user> <gwava_pass>D13AA10E81</gwava_pass> <gwava_realm>GWAVA Console</gwava_realm> <gwava_interface>19n6uhr.19pmbfu.1ss</gwava_interface>
3. Finally, save the file and restart the GMS service to load the new configuration settings
Now Novell GroupWise Mobility Service can connect to the GWAVA system for scanning.
WARNING! There can only be one instance of each of these settings in the connector.xml file! The connector.xml file can have the order scrambled. If this file has been modified previously with GWAVA information, ensure that only one instance of each of the settings exists.