9.4 Secure Message Gateway (GWAVA 7) Integration

Mobility 18 provides an integration with Secure Message Gateway (GWAVA 7) to secure your device emails. Device emails are scanned and accepted or rejected. If accepted, the message is delivered to GroupWise. If rejected, the sender receives an email explaining that the email was rejected by the Secure Message Gateway scan.

For this integration to work, you must do the following:

  1. An Interface must be created in Secure Message Gateway for Mobility. For information on creating an interface see SMT Interface in the Secure Message Gateway documentation.

  2. Open the following file on the Mobility server:

    /etc/datasync/configengine/engines/default/pipelines/pipeline1/connectors/mobility/connecter.xml
  3. Add the following elements in the <custom> section:

    Element

    Value

    <securegatewayEnable>0</securegatewayEnable>

    A “0” is disabled. A “1” is enabled. Set the value to “1” if you want to use Secure Message Gateway.

    <securegatewayHost>securegatewayhost</securegatewayHost>

    securegatewayHost should be set to the value found in the Secure Message Gateway Admin > Module Management > Interfaces > 3rd Party Application Manager > <Name of Interface created for GMS> > Server Address.

    <securegatewayPort>securegatewayport</securegatewayPort>

    securegatewayPort should be set to 80 if not using SSL and 443 if using SSL.

    <securegatewaySecure>securegatewaysecure</securegatewaySecure>

    A “0” is non-secure or HTTP. A “1” is secure or HTTPS. Set the value to what you are using for Secure Message Gateway.

    <securegatewayAppkey>securegatewayAppkey</securegatewayAppkey>

    securegatewayAppkey should be set to the value found in the Secure Message Gateway Admin > Module Management > Interfaces > 3rd Party Application Manager > <Name of Interface created for GMS> > Application Key.

  4. Restart Mobility.