Content Comparison

...

Provision Connexion

Provisioning of the Integrator network requires the following steps:

1. Download Connexion (Developer Build) in the datacenter environment.
2. Run the installer, but do not yet run through the configuration wizard. The installer will deploy the files to the Program Files (x86)\ConnexionV14 folder.
3. Copy the Hub database script files into the Program Files (x86)\ConnexionV14\Connexion.AdvancedServices folder. If this folder does not exist, create it.
4. Open the connexion.exe.config file in the Program Files (x86)\ConnexionV14 directory and set the Hub to enabled.
   
   

5. If your database server for Connexion is not local, it is probably the case that your CXN_AdvancedServices database is also not local. If so, you will need to edit the connexion.exe.config file and update the database connection string for the CXN_AdvancedServices database.
    
   The portion of the string that needs to change is
   
   If you are using Sql Server authentication, and connecting to a machine named "dbserver1", with user "sa", and password "mypassword", the connection string would look like this:
    
   If you are using LocalDB, set the above connection string to:
   
   

   Code Block
   language css
   <add name="AdvancedServiceContext" connectionString="metadata=res://Connexion.Integrator.Hub/Model.csdl|res://*/Model.ssdl|res://Connexion.Integrator.Hub/Model.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=(localdb)\.\ConnexionV14;initial catalog=CXN_AdvancedServices;integrated security=True;MultipleActiveResultSets=True;App=EntityFramework&quot;" providerName="System.Data.EntityClient" />

   
   NOTE: If you are unfamiliar with database connection strings, please seek help from your IT staff. 
    

6. Continue the configuration process by stepping through the configuration wizard.
7. Add a link to the Integrator Management UI by right clicking on the Program Files (x86)\ConnexionV14\Connexion.Integrator.Management.Ui.exe and choosing Send To > Desktop.
   
   

Anchor
ExternalEndpoint ExternalEndpoint

External Endpoint

When testing on the same network, you can ignore this step.

...

Open the Management UI and click the edit hubs button. Update the host and port, and click save.

Provision a Remote Agent

You now have all of the data center components installed and are ready to start provisioning remote customers. There is a well-defined workflow for provisioning a remote agent:

1. Create a registration file unique for the customer we're going to provision. You will be prompted to save a registration file as well as provide a password.
2. Securely send that registration file and the Remote Agent Installer to the client, and have them place both files into a new folder on their PC.
3. Have the client run the installer, using the password you specified in step 1.
4. Authorize the newly established connection from within the Remote Agent Management UI.

...

We now have a row in our pending table. Notice the 'Status' shows 'Awaiting Connection'. The hub is now waiting for a remote agent with a specific signature to connect. The signature is contained within the registration file we just created. Let's install the Remote Agent software and connect to the hub.

Installing the Remote Agent

You must provide 3 things to the customer:

1. Remote Agent Installer
2. Registration File
3. Password

...

The remote agent (customer site) has now been successfully installed.

Authorizing a Remote Agent

...

 Do not use the regular queue device for Integrator channels - use the 'Mongo Queue Device'.

Managing Remote Agent Channels

The Management UI does not let you create or edit channels. Channels must be created in the main Connexion UI and exported to a channel file. Since it is a cumbersome process to be switching into the Connexion UI to perform any channel edits, be as thorough as possible when initially creating the channel.

...

Unofficially, you can edit this configuration and then use the 'ctrl + s' keystroke or the save button on the channel to commit your changes. This functionality is currently being evaluated.
 

Creating Routes

In order to transfer data to/from the Remote Agent, we have created two new devices:

...

Notice the route box now appears at the beginning of the channel, and instead of specifying which channel you are sending to (in Connexion), you specify which channel you are receiving from (in Connexion).