Mysttic Connect
Mysttic Connect
An integration engine for HL7, X12, DICOM, XML and JSON, FHIR over HTTP included. It is built from the Mirth Connect 4.5.2 code the way the official release was built: the engine is the same, the name and the start scripts are its own.
Copy your Mirth Connect 4.5.2 configuration over, start it, and your channels run as they did before.
Three parts, each with its own version number: the server, the Administrator Launcher and the Server Manager. From 1.2.0 the Administrator Launcher and the Server Manager check for new versions themselves, and this can be turned off.
Latest release: checking…
Like the Mirth Connect setup: the server with its own Java 17, the “Mysttic Connect Service”, the Server Manager, the CLI and the Administrator Launcher, Start Menu shortcuts. Upgrades in place and keeps your configuration and data.
Download the installer
A .tar.gz with the Mysttic Connect folder:
mcserver to run the server, mcservice to run it
as a service, mccommand and mcmanager.
A .zip with the same folder for an installation by hand:
mcserver.bat to run the server, install-service.bat
to register the “Mysttic Connect Service”.
SHA-256 of the server files, to check a copy that reached a server through several hands.
Download checksumsLatest release: checking…
Downloads the Administrator from a Mysttic Connect server and starts it, with its own Java and JavaFX. Install it on every computer that runs the Administrator; it also opens the file of the Web Dashboard’s “Launch Mysttic Connect Administrator” button. Any version of it works with any Mysttic Connect server; the copy installed with the server is updated with the server.
A .tar.gz for 64-bit Linux; install-desktop-entry.sh
adds it to the application menu.
Checksums of the launcher files
Latest release: checking…
The Server Manager is installed with the server, by the installer and from both packages above. These files only update the Server Manager of an existing installation of Mysttic Connect 1.2.0 or later; they install no server and leave the server as it is.
For a server installed with the Windows installer: replaces the Server Manager and starts it again. It needs administrator rights and changes nothing if the server is older than this Server Manager needs.
Download the update
A .tar.gz to unpack over the installation folder, for a server
installed from one of the packages;
the steps are below.
Checksums of the Server Manager files
The installer and the launcher bring their own Java 17. The .tar.gz
and .zip packages carry none: install a 64-bit Java 8 or newer
first. Nothing here is signed with a code-signing certificate yet: Windows may
show a SmartScreen warning (More info, then Run anyway), and macOS opens the
launcher only after “Open Anyway” in System Settings, Privacy &
Security. The launcher checks the Administrator’s files against the
SHA-256 list of the server, not their signatures, which are made with a public
build key. The interface is in English.
An engine for your Mirth Connect 4.5.2 channels, built from the same code and compared with the official release file by file, with every difference explained.
The Mirth Connect 4.5.2 code, changed only where it shows the product name and where it finds its two configuration files (new names, the old ones still work). The engine version stays 4.5.2, so extensions made for 4.5.2 load as they are, and the database schema is the one Mirth Connect uses.
The same Java 8 compiler and Ant version as the official 4.5.2 build. Every file of the Linux and macOS package is compared with the official 4.5.2 release, and every difference is accounted for: the name, the signatures, the build timestamps and the start scripts, which are our own in place of the install4j launchers.
99 integration cases run on the official Mirth 4.5.2 and on Mysttic Connect side by side: the same ACKs, responses, files, database rows and e-mails. The only differences are the product name in texts, the default User-Agent and the default alert subject.
Same channels, code templates, configuration map, users, REST API,
X-Mirth-* headers and JavaScript API. Nothing to export or
import: the installation takes over Mirth's files and database.
A conf/mirth.properties copied from Mirth Connect is used
in place of the default conf/mysttic.properties, and the
log says so. Rename it when it suits you.
Four steps on the server Mirth runs on. Keep the old folder until the new installation has run for a while.
On Windows stop the “Mirth Connect Service” and set it to start manually: both services use the same ports, and after a reboot both would start.
On Windows run the installer into a new folder (the default
C:\Program Files\Mysttic Connect) with the ports Mirth used,
then stop the “Mysttic Connect Service” it started. Elsewhere,
or by hand, unpack the package next to the old installation: it creates the
Mysttic Connect folder.
conf/mirth.properties, the whole appdata folder
without temp (it holds the keystore, the server id, the
configuration map and, with Derby, the database), custom-lib,
your own extensions, and whatever you changed among the
.vmoptions, conf/dbdrivers.xml,
conf/log4j2.properties and
conf/mirth-cli-config.properties.
Installed with the installer: start the “Mysttic Connect
Service” again (Server Manager or services.msc). From the
package: run mcserver, or as a service on Windows
install-service.bat /start as Administrator, on Linux and macOS
the service you had pointed at the mcservice script. Remove the
old service once the new one runs.
The engine behaves exactly like Mirth Connect 4.5.2, its bugs and the known vulnerabilities of its libraries included. Run it inside your network, not on the internet.
Instead of the install4j .exe launchers there are
mcserver.bat, mccommand.bat and
mcmanager.bat, and the service is Apache Commons Daemon
(mcservice.exe). The installers and the package have been
tested under Wine, not yet on Windows itself.
The image that replaces the official Mirth Connect one is not public. The packages above are the way to install from this page.
The Administrator, Server Manager, CLI and web pages; the files
conf/mysttic.properties and logs/mysttic.log;
the Windows service; the default User-Agent of the HTTP
Sender and the default subject of alert e-mails.
Everything channels, data and partners depend on: the
com.mirth classes, the JavaScript API, MIRTH
in automatic ACKs, the REST paths, the mirthdb database and
the mirth-*.jar file names.
For a server installed from the Linux and macOS package or the Windows
.zip, version 1.2.0 or later. Check the download against its line
in the Server Manager checksums first, with sha256sum (on macOS
shasum -a 256).
Choose Close Manager in its tray menu. The server and its service keep running: the update replaces only the Server Manager.
With the command below, into the folder holding mcserver, for
example /opt/Mysttic Connect; only the Server Manager’s
files change. On a Windows .zip installation run it without
sudo, in a Command Prompt opened as Administrator.
Start the Server Manager with mcmanager (on Windows
mcmanager.exe).
sudo tar -xzf mysttic-connect-manager-<version>-unix.tar.gz -C "<install folder>"