Understanding the Mirth^® Connect system requirements is crucial to prevent performance issues and system downtime. Therefore, it’s essential to consider these requirements when selecting the server features where we will deploy our system.

Mirth Connect is a standalone application that only requires a Java Virtual Machine. This article could end here, but it’s not that simple. In addition to Java, we will need to make decisions about other server variables such as the operating system, the RAM, and the processor we will use.

Before reviewing the requirements, let’s identify the components of Mirth Connect to understand their individual needs.

Components of Mirth Connect #

Although we refer to Mirth Connect as a single application, it is actually a system composed of several applications. The two main ones are Mirth Connect Server and Mirth Connect Administrator. We must know the system requirements for both applications and how to use them to avoid leaving the server without enough RAM or disk space.

First, Mirth Connect Administrator is the tool used to create, configure, deploy, and monitor the channels of our integrations. We must be careful when using it, as improper use can exhaust the server’s RAM. Later on, we’ll see what to do to avoid this problem.

Secondly, Mirth Connect Server is the application that will receive, process, and send information according to the channels we have created with the Administrator. It runs on the server, and it is the one for which we really have to consider the minimum requirements.

To meet the requirements of Mirth Connect Server, we need to consider several aspects:

• The operating system of our server.
• The database that will be used.
• And choosing a compatible Java version.

Mirth Connect Operating System requirements #

Mirth Connect is compatible with the main operating systems, whether it’s Windows, Linux, or even Mac OS. Therefore, our server won’t have special requirements in this regard. The most common practice is to use a Windows or Linux server. (Does anyone really use Mac OS to deploy Mirth in production?).

Our preferred option is to use a Linux server based on Debian or Ubuntu, but it is also common to deploy Mirth Connect on Windows Server. Either of the two options should work well.

You can find all versions for Windows and Linux (and Mac OS) on our Mirth Connect download page.

In summary, the operating system requirements for Mirth Connect are not very demanding since it really depends more on the version of Java we install on the system.

Java version requirements for Mirth Connect #

This is the key component of the minimum requirements for Mirth Connect, as it determines whether or not we can install it on our server.

The version of Java we can use depends on the version of Mirth Connect we plan to install. The following table shows the compatibility between the versions:

Therefore, we must choose versions of Java and Mirth Connect that are compatible with each other.

It is very important to note that, starting with Java 11, Oracle introduces a change in its license, and its version cannot be used in production without a commercial license. In our article about Java 11 and Mirth Connect, we explain how to act in each situation to avoid problems.

Tip: check out our article about what you should know about Java JDK license and Mirth Connect.

Additional configuration for Java 9 or greater #

Mirth Connect version 3.7 and later supports a minimum of Java 8. However, to use Java 9 or greater, an additional manual step is advisable. Note that this step is already included in Mirth Connect 4.4, so it is only necessary when using Java 9+ with Mirth Connect versions 3.7 to 4.3.

• Locate the docs folder in the Mirth Connect installation directory.
• Inside this folder, you will find a file named mcservice-java9+.vmoptions. This file contains the JVM options required to run Mirth Connect with Java 9 or higher without encountering errors or warnings.
• Copy the contents of this file into either the mcserver.vmoptions or mcservice.vmoptions file, depending on whether your deployment uses mcserver or mcservice.
• Restart Mirth Connect to apply changes.

Configuring the Reserved Memory for Mirth Connect #

The default amount of memory reserved for Mirth Connect is usually set too low. To configure this value, we must modify a configuration file located in the root directory of the installation. The file to be modified is:

• mcservice.vmoptions, if installed as a service. This is the default option if we have a single instance of Mirth Connect.
• mcserver.vmoptions, if installed as a server.

The default content of this file is:

-server
-Xmx256m
-Djava.awt.headless=true
-Dapple.awt.UIElement=true

To reserve more memory for Mirth, we’ll need to edit the second line and change the value. For example:

• -Xmx256m: 256 MB.
• -Xmx512m: 512 MB.
• -Xmx1024m: 1 GB.

After editing it, we must restart the Mirth Connect service for the change in the reserved memory amount to take effect.

Database requirements for Mirth Connect #

Mirth Connect utilizes a database to store its configuration settings and messages. While an Apache Derby database is included by default, it is not recommended for production use. Instead, installing another compatible database that Mirth Connect supports is necessary for production environments.

Mirth Connect is highly flexible with its database compatibility, supporting most mainstream databases.

The minimum compatible versions for each databases are:

• PostgreSQL: 8.3 or higher.
• MySQL:
  • Version 5.6 from Mirth Connect 3.8.x.
  • Version 5.0 to 5.7 for Mirth Connect up to 3.7.x.
• Oracle: 10g Release 2 ot higher.
• SQL Server: 2005 or higher.

Subsequently, later versions of these databases should be suitable for a Mirth Connect deployment. It is always advised to use the most recent stable version of a database to ensure the best performance and security.

Minimum server requirements for Mirth Connect #

When setting up a Mirth Connect server, often a virtual machine, it is best to start with the right setup to ensure everything runs smoothly from the beginning, even though you can adjust resources later as needed.

Server requirements essentially refer to three components:

• Processor (CPU)
• Memory (RAM)
• Disk space

Each of these variables depends on different factors that we will need to consider when establishing the minimum configuration of our server. Therefore, the ideal configuration depends on the characteristics of the integration itself.

In addition, we should consider whether the workload will be constant or if there will be specific peaks of activity that the server will need to absorb and for which it will require more resources.

Disk space requirements #

Disk space requirements depend on:

• Database Storage: Keeping the database on the same server as Mirth Connect can prevent connectivity issues and simplify configuration but will require additional disk space. An external database reduces the need for local disk space but adds the complexity of managing network connections and potential connectivity issues.
• Logging: Log files can accumulate and take up substantial space. It’s essential to configure logging properly to prevent server crashes due to disk space exhaustion.

RAM requirements #

The amount of RAM our server will need is heavily influenced by the number of channels. Starting from a baseline amount, RAM should be scaled in proportion to the number of channels configured within Mirth Connect.

CPU requirements #

The CPU demand is more about the volume of messages processed than the number of channels. High message throughput requires stronger CPU capabilities.

Consideration for messaging spikes is crucial, as they can temporarily require increased processing power to handle the load efficiently.

Server configuration examples for Mirth Connect #

It is impossible to define one-size-fits-all minimum requirements for server configurations due to the variability of integrations. However, for resource-rich environments where the integration plays a critical role, the following setup could be considered standard:

• RAM: 8 GB total, with 3 GB allocated to Mirth Connect. For systems with fewer channels, 4 GB of RAM with 1 GB allocated to Mirth Connect may suffice.
• Storage: 50 to 100 GB of expandable hard drive space for the operating system, Mirth Connect, and the database. Solid-state drives (SSDs) are highly recommended for better performance.
• CPU: Either a single CPU at 2.4 to 3 GHz or dual CPUs at 2.1 GHz each.

These recommendations should be tailored to the specific needs of each integration project. Additionally, there are several techniques that can be employed to optimize resource usage.

Below is a table that provides four examples of server configurations, intended to serve as a reference point.

Caution regarding the Administrator and server memory #

The Administrator, Mirth Connect’s graphical management interface, can be quite demanding on RAM. To prevent potential memory shortages, it is advisable not to run it on the same server as the Mirth Connect Server.

Although launching the Administrator on servers with a graphical interface may seem convenient, it poses significant risks. The server could run out of memory, particularly if multiple users access the Administrator concurrently and inadvertently leave it open after their sessions. This can cause the server to retain memory unnecessarily, degrading performance.

This situation isn’t a direct system requirement of Mirth Connect, but neglecting it can undermine the careful planning of your server resources.

Recommendation: Always operate the Administrator from a machine separate from the server to eliminate the risk of depleting the server’s working RAM.

Learn more about Mirth Connect Administrator.

Conclusions #

Mirth Connect’s system demands are mostly tied to the use of compatible Java and database versions. Disk space and memory needs are contingent on system load and the specific setup of your integration channels.

Designing an efficient server setup and preventing resource shortages rely heavily on experience. Without substantial expertise, consulting with a specialist is prudent, especially when dealing with production environments. Caution is key in such critical systems to avoid service disruption.