The Connexion Gateway ("Gateway") is the service which enables the end-to-end communications between remote sites and the data-center. It should be the first component installed in an Integrator deployment (although existing Connexion instances can be connected to the Gateway).
There are two pre-requisites for the Gateway:
- A SQL Server instance to host the 'AdvancedServices' database. If you are deploying the Gateway within the DMZ, you will need to configure your network to allow communications between the internal SQL instance and the Gateway.
- An SSL certificate from a trusted authority installed on the Gateway host OS. If you are deploying a test environment which will have no PHI, you may skip this step (the Gateway deploys a self-signed certificate as part of the installation). Your certificate should point to the endpoint/domain name you intent to expose to remote integrators.
Once you have an available SQL instance as well a SSL certificate installed, install the Gateway (see the downloads section). Once the files have been deployed, the Gateway configuration wizard will be launched. This application guides you through the required configuration steps. The first step is to obtain a license. You will need to provide your Hardware ID and Licensee information in order to receive a license key.
The next step is to enter the location and credentials for your SQL instance which will host the AdvancedServices database. This can be the same instance used to host Connexion. Please note that the credentials you enter must have SysAdmin privileges in order to create the database. This account is used only for installation - a separate account is used by the Gateway to read/write.
The next screen lets you specify the account used to run the Gateway service as well as what SQL credentials it will use to connect to the AdvancedServices database. The service and SQL credentials should be restricted accounts (reader/writer for SQL).
Now you must specify the certificate, domain, and port information. The certificate name is typically the domain you specified when you entered your certificate request to the 3rd party certificate provider. This same value is typically used as the 'External FQDN' which is the endpoint remote clients will be connecting to (in the screen capture below there is an extra www. due to an obscure certificate bug). The internal port is the port which Connexion will connect to (ie, exposed from your DMZ to your internal network). The external port is used by Remote Integrators to connect via the internet.
You're all set to start the configuration process:
If all goes as expected, your configuration is complete and you can move on to installing/upgrading Connexion.
