Production instances — run OIE in production without running the infrastructure

Production instances are part of Managed OIE: production-ready Open Integration Engine, provisioned in the NovaMap cloud and configured for high load and the data you actually handle in production.

Open Integration Engine is the drop-in open source successor to Mirth Connect™.

Running Open Integration Engine has always meant owning the whole stack: the server, the engine, the patching, the monitoring. NovaMap operates the engine itself and the infrastructure beneath it: elastic, resilient compute and storage, secure communications, the operating system, and the JVM. You sign in and start building channels.

What a production instance is

A production-ready OIE instance that runs in production without you running the infrastructure.

Functionally, it behaves the same as the free dev instance anyone can provision from the portal. The difference is how each is provisioned and operated. A production instance is sized for real load and configured for resilience and data security, so your integrations keep running.

Every production instance includes:

• Production-grade NovaMap Cloud hosting
• Configurable VM sizing
• Optional high availability
• Optional dedicated static IP
• Latest stable OIE version
• Priority support

How high availability works

High availability is optional, and it's worth understanding before you decide.

Our HA configuration uses active/active compute units and DB, spread across availability zones. Updates are applied in a staggered manner to ensure no downtime during updates. Managed backups and a defined recovery process mean a single fault doesn't become an outage.

The staggered-update detail matters more than it sounds. Patching an integration engine has traditionally meant a maintenance window, a downstream comms exercise, and someone staying late. Active/active across zones means the update rolls through while the engine keeps taking messages.

Provisioning

Three steps:

1. Create a NovaMap account.
2. Go to Instances in the portal.
3. Request a production instance.

Running the administrator

This works as it does with Mirth Connect™. The OIE administrator is a Java application, downloaded from OIE each time, running on your own machine. To run it you'll need a launcher, and either of these works:

• Ballista, by Kiran Ayyagari
• Mirth Connect™ Administrator Launcher, by NextGen

Once the launcher is installed, configure it with the JNLP URL we send you by email. It's also in the details section of your production instance in the portal.

What you're actually running

OIE is a maintained fork of the last open source version of Mirth Connect™, version 4.5.2, so you'll notice very little difference. Its API is compatible with Mirth Connect™ 4.5.2. There have been a number of changes under the hood, either to improve functionality and performance or to address identified vulnerabilities. The full list is in the release notes on GitHub.

That compatibility is the point. Your channels, your templates, your team's skills: they carry across.

Pricing

Pricing is based on the server size you choose, billed annually. Every production instance is fully managed, so the operating system, JVM, and OIE itself are all included, within NovaMap's monitoring & management platform.

A dedicated static IP, for allow-listing on partner and HSCN connections, is +£300/yr. Custom sizing covers specific requirements such as a site-to-site VPN into your network.

Built to NHS standards

NovaMap is ISO 27001:2022 certified. 25+ NHS Trusts and healthcare system vendors send 1.5M+ messages a day through our products. Security is built in, including support for mTLS and certificate management via the OIE TLS plugin.

Managed OIE gives you the confidence of enterprise support and the freedom of open source.