What Java version does Mirth Connect require?

Mirth Connect 4.x requires Java JDK 11 or 17 (LTS). Java 8 is no longer supported in recent versions. We recommend Java 17 LTS for new installations as it provides the best long-term support.

Which database should I use with Mirth Connect?

PostgreSQL is the most commonly recommended database for Mirth Connect in production due to its performance, reliability, and open-source licensing. MySQL is also widely used. For high-volume environments processing 10,000+ messages per day, PostgreSQL with proper tuning is the preferred choice.

Mirth Connect Setup Guide

Mirth Connect
Installation Guide

Q: Can Mirth Connect run on Linux?

Yes. Mirth Connect runs on any modern Linux distribution including Ubuntu 20.04+, CentOS/RHEL 8+, and Debian. Linux is the preferred deployment platform for production Mirth Connect environments due to its stability and performance characteristics.

A complete, step-by-step guide to installing and configuring Mirth Connect — covering system requirements, Java setup, database configuration, service startup, and production hardening for healthcare IT teams.

Mirth Connect 4.xJava 11 & 17Linux & WindowsProduction-Ready

Get Installation Support

Our Mirth Connect engineers can handle the installation for you — contact us for professional setup services.

Prerequisites

System Requirements

Ensure your server meets these requirements before beginning the Mirth Connect installation.

Operating SystemWindows Server 2016/2019/2022, RHEL 7/8/9, Ubuntu 18.04+, CentOS 7/8

Java VersionOpenJDK 11 or OpenJDK 17 (LTS recommended)

Minimum RAM4 GB (8–16 GB recommended for production)

Disk Space10 GB minimum; additional for message storage

DatabaseEmbedded Derby (dev only), PostgreSQL 12+, MySQL 8+, or SQL Server 2017+

Network Ports8080 (HTTP), 8443 (HTTPS), 6661 (MLLP default), configurable

Step-by-Step

Mirth Connect Installation Steps

Follow these steps in order to install and configure Mirth Connect for development or production use.

Install Java Runtime

Mirth Connect requires Java 11 or Java 17. Download and install OpenJDK from the official distribution for your OS. Set JAVA_HOME environment variable and verify with 'java -version'.

# Linux (RHEL/CentOS)
sudo yum install java-17-openjdk-devel
export JAVA_HOME=/usr/lib/jvm/java-17-openjdk

# Ubuntu/Debian
sudo apt-get install openjdk-17-jdk
export JAVA_HOME=/usr/lib/jvm/java-17-openjdk-amd64

Download Mirth Connect Installer

Download the latest Mirth Connect installer from the NextGen Healthcare GitHub releases page. Choose the installer appropriate for your operating system (Windows .exe, Linux .sh, or platform-independent .zip).

# Download via wget (Linux)
wget https://github.com/nextgenhealthcare/connect/releases/download/4.5.0/mirthconnect-4.5.0.b325-unix.sh
chmod +x mirthconnect-4.5.0.b325-unix.sh

Run the Installer

Execute the installer with administrative privileges. The GUI installer will guide you through selecting the installation directory, port configuration, and initial service settings. For Linux headless servers, use the console mode installer.

# Linux console mode installation
sudo ./mirthconnect-4.5.0.b325-unix.sh -c

# Windows (Run as Administrator)
mirthconnect-4.5.0.b325-windows.exe

Configure External Database (Recommended)

For production deployments, replace the embedded Derby database with PostgreSQL or MySQL. Edit the mirth.properties file in the Mirth Connect installation directory to configure the external database connection.

# Edit mirth.properties
database = postgres
database.url = jdbc:postgresql://localhost:5432/mirthdb
database.username = mirth
database.password = your_secure_password
database.max-connections = 20

Start the Mirth Connect Service

Start the Mirth Connect server service. On Windows, use the Services panel or the Mirth Connect Service Manager. On Linux, use systemctl or the mcservice script included in the installation directory.

# Linux (systemd)
sudo systemctl start mcservice
sudo systemctl enable mcservice
sudo systemctl status mcservice

# Using mcservice script
sudo /opt/mirthconnect/mcservice start

Connect via Administrator Client

Launch the Mirth Connect Administrator desktop client (Java Web Start or standalone) and connect to your server at https://[server-ip]:8443. Default credentials are admin/admin — change these immediately after first login.

# Default connection settings
Server: https://your-server-ip:8443
Username: admin
Password: admin

# Change password immediately after login!
# Administrator > Settings > User > Change Password

Harden for Production

Before going live, apply production hardening: change default credentials, configure SSL certificates, enable audit logging, restrict administrative access by IP, and configure automatic backups of your Mirth configuration.

# Key production hardening steps:
# 1. Change admin password and create role-based users
# 2. Import valid SSL certificate (not self-signed)
# 3. Configure backup schedule in Settings > Server
# 4. Enable message pruning to manage disk usage
# 5. Configure SMTP for alert notifications

FAQ

Installation FAQs

What version of Java does Mirth Connect require?

Mirth Connect 4.x requires Java 11 or Java 17. We recommend OpenJDK 17 LTS for production deployments as it offers long-term security updates. Older versions of Mirth Connect (3.x) may work with Java 8, but upgrading to the latest version with Java 17 is strongly recommended.

Can Mirth Connect run on Linux?

Yes. Mirth Connect runs on Linux, Windows, and macOS. For production deployments, RHEL, CentOS, or Ubuntu Server (Linux) is recommended for better performance, stability, and system management using systemctl.

Should I use the embedded Derby database or an external database?

The embedded Derby database is only suitable for development and testing. For any production environment, use PostgreSQL, MySQL, or SQL Server. External databases provide better performance, reliability, backup options, and support for high-availability clustering.

What ports does Mirth Connect use by default?

Mirth Connect uses port 8080 for HTTP and 8443 for HTTPS (Administrator access). The default MLLP listener port is 6661. Each channel you create can be configured to listen on additional ports. Ensure your firewall allows traffic on any ports your channels need.

How do I upgrade from an older version of Mirth Connect?

Before upgrading, back up your Mirth Connect configuration (channels, code templates, server settings) and your database. Run the new installer, pointing it to the same installation directory. Mirth will automatically migrate your existing configuration to the new version. Always test upgrades in a non-production environment first.

Can Taction Software help with Mirth Connect installation?

Yes. We provide professional installation services for Mirth Connect, including system sizing, database configuration, SSL setup, production hardening, and initial channel deployment. We also provide post-installation support and managed services.

Need Help Installing Mirth Connect?

Skip the complexity — let our Mirth Connect engineers handle the installation, configuration, and production hardening for you. We'll have your environment ready faster and configured correctly from the start.

Professional installation on your infrastructure
Database setup and migration
SSL configuration and security hardening
Initial channel deployment and testing

Get Professional Installation Help

Tell us about your server environment and our engineers will get your Mirth Connect running right.

Mirth ConnectInstallation Guide