Gateway & RA Introduction

Gateway & RA Introduction

Although the Connexion integration engine can be installed on-premise as well as in cloud environments, it can be overkill in certain scenarios. One such scenario is when a healthcare software/services vendor requires an integration technology to be deployed along side their software product (within the customer environment). An enterprise integration engine (like Connexion) is usually too expensive to package with other software offerings - especially when dealing with hundreds or thousands of deployments. There can be other complicating factors, such as the requirement for remote access (for management), encrypted networking tunnels, and sometimes deploying company-owned hardware to customer sites.

The Gateway platform was designed to solve this scenario. It has the following attributes:

  • Runs on customer hardware / VMs.

  • Once installed, fully remotely managed.

  • Secure tunnel between the customer site and vendor, with near real-time transport of messages.

  • Transparent to customer firewalls

  • Inexpensive - usually between $200 and $300 (USD) per customer site, per year.

  • Fully-featured UI designed for managing thousands of deployments.

  • Fully-featured high-performance integration engine.

  • Uses the same channels and devices as Connexion

  • Enterprise features for events, alerts, monitoring, metrics, etc.

Gateway_map_regular-20250902-032525.png

The Gateway platform is comprised of two main components:

  • Remote Integrator: The integration software which runs at the customer site. This is comprised of three services: One which hosts channels and devices (“Remote Agent”), and two which are used for monitoring and management (“Updaters”). These services all create secured network tunnels to the Gateway.

  • Gateway: A service which runs at the vendor site and coordinates traffic and management of each Remote Integrator. The gateway also optionally connects with one or more instances of Connexion, and can broker data between the vendor site and Remote Integrators (in both directions, in near real-time).

Brokering data between the vendor site and customer site is easily configured, with tools for monitoring status and state, tracing messages through each platform, and much more.

Laptop_Gateway_3big-20250902-034425.png
Easily connect remote and cloud sites using intuitive drop-downs or drag and drop.

The Gateway platform requires publicly accessible endpoints with valid certificates. Typically, there is one endpoint per Gateway (gw1.mycompany.com, gw2.mycompany.com, etc.) with a wildcard certificate used for all endpoints.

The configuration for the gateway and all remote integrators is stored in the gateway database (Sql Server or Postgres). This means it is very easy to re-create a remote integrator installation if a customer site experiences a failure.

Video: Installing the Gateway

GatewayInstall.mp4

Video: Your First Remote Agent

FirstRA.mp4