Deploying a Remote Integrator

The procedure for deploying a remote agent has not changed significantly since the alpha releases. The process involves several steps:

1. In the Gateway management application, generate a new remote integrator record and associated 'key' file.
2. Provide the key file and password to your client (in a secure two-step manner - provide the file electronically and provide the password by some other means such as phone or SMS).

3. Provide download links to the remote integrator installer and install at the remote site.

   Connexion.Integrator Installer

   The latest Connexion Integrator Installer can be downloaded from here: /wiki/spaces/CON/pages/14057573

4. During installation, provide the 'key' file and password.
5. In the Gateway management application, promote the remote agent to 'authorized'.
6. Deploy channels.

Provision a Remote Integrator

Once the remote integrator installer has run, you should see the state change from 'Awaiting Connection' to 'Awaiting Authorization'.

Click the 'Authorize' button (beside the green shield icon) to enable unrestricted communications to the remote site.

Restrictions & Notes

1. The only queue device supported by the RemoteAgent is the Mongo queue device. Within Connexion, you will need to open the Nuget package manager and install this device. In all channels destined for the remote integrator, you must replace the regular queue device with the Mongo Queue.
2. You must deploy the Mongo queue to the remote agent before deploying any channels. You may do this by clicking the 'Add' button in the bottom right corner of the Device manager area (which itself is the bottom-right rectangle).
3. The branch device is not supported by the remote integrator.
4. Channels cannot be created within the Management application, you must create them in Connexion and then copy/paste or export/import them into the management application.
5. Message transfer is facilitated by the Remote Agent Inbound/Outbound connector devices (under the 'Remote Agent' category in Connexion).

There are two videos from the alpha release which show the general idea behind deploying channels and enabling message flow (please note some of the UIs may be out of date):