Skip to content

Build With Closed Source Extensions

Chris Turczynskyj edited this page Nov 3, 2021 · 2 revisions

This document will walk you through importing and using a closed source Mirth Connect extension in Eclipse.

Pre-requisites

You have cloned the latest release of Mirth Connect and have it successfully building in Eclipse. For this example we'll be using Mirth Connect 3.11.0. See Clone, Build, and Run from Source.

You have one of the NextGen closed source extensions for Mirth Connect matching the version number of Mirth Connect. For this example we'll be using the FHIR extension for 3.11.0.

Setup

Extract the plugin to Mirth Connect server's build/extensions folder (for example: connect/server/build/extensions/fhir).

Extract Extension

Refresh the Mirth Connect Server project. You should see some additions to the build folder.

Copy Extension Files

Configure the Server Classpath

Add the extension jars and extension libraries to the classpath

Right Click Server > Build Path > Configure Build Path...

Open Build Path

Click the "Libraries" tab.

Libraries Tab

Click the "Add JARs..." button. Select all of the JAR files at the root of the extension and all of the JARs in the extension's lib folder. In this case, the extension should be at Server/build/extensions/fhir.

Add JARs

Set the JAR Loading Order

Order the libraries on the "Order and Export" panel, moving the extension jars above the extension library jars. Sometimes we override functionality in included libraries and if our jars aren't loaded first, it can lead to errors and missing functionality.

Order JARs

You could also edit the Server/.classpath directly.

Edit Classpath

Test the Environment

Start Mirth Connect Server.

Start Mirth Connect Server

Start Mirth Connect Client then create and deploy a FHIR Listener channel.

Create FHIR Listener

The channel should deploy without errors.

Deploy FHIR Listener

Clone this wiki locally