Connect to Database using SSL/TLS

Mirth® Connect by NextGen Healthcare User Guide

Before You Upgrade

Before upgrading, NextGen Healthcare highly recommends that you backup both your Mirth® Connect Server Configuration and your Mirth® Connect database using the following steps. Note: mirth_home directory. Backup server configuration: Before proceeding, it is important that you backup your existing server configuration. This can be done through the Mirth Connect Administrator (Settings>Server Tab>Server Tasks – Backup Config). The server configuration includes channels, code templates, alerts, and global scripts. User accounts and stored messages will not be backed up. Backup database: If you use the embedded Derby database, create a backup of the "mirth_home/appdata/mirthdb" folder. Note that appdata is the database folder as defined in the "mirth_home/conf/mirth.properties" file. For additional information, see mirth.properties File. If you use an external database (for example, PostgreSQL, MySQL), create a backup of your database using your preferred database administration tool (for

Mirth® Connect by NextGen Healthcare User Guide

Frequently Asked Questions

This section addresses the most common questions users have about Mirth® Connect by NextGen Healthcare. What is Mirth® Connect? Mirth® Connect is a versatile, standards-based healthcare integration engine that speeds bi-directional message routing, filtering, and transformation between disparate health-info systems over various messaging protocols (e.g., HL7, X12, EDI, DICOM, XML). Is Mirth® Connect the same as "Mirth"? Yes. Mirth 1.0 was released in 2006 by WebReach, Inc. Based on the success of the Mirth application, WebReach, Inc. was renamed "Mirth Corporation" in 2009. To avoid confusion between the new company name and its products, the Mirth application was renamed Mirth® Connect. As of early 2016, Mirth Corporation, as a business entity, no longer exists, having been absorbed into the Quality Systems, Inc. family of products in Sept. 2013. QSI has since become NextGen Healthcare, and Mirth® Connect lives on with other former Mirth Corporation products as part of the "Mirth Solu

Mirth® Connect by NextGen Healthcare User Guide

Installation Directory

In general, the principle of least privilege should be followed, and only Administrators should have access to the installation directory that Mirth® Connect is installed into. If installed on a dedicated machine, that machine should only be accessible to said administrators. If installed on a shared machine, it should be done in such a way that the Connect installation directory is only accessible by administrators. Notes on specific folders inside the installation directory: appdata: The Application Data Directory stores configuration and temporary files used by Mirth® Connect during runtime. Take note of: configuration.properties: By default this file is used to store the current state of the Configuration Map. However in mirth properties you can choose to store the configuration map in the database, or you can select a different file location. For example if you have a separate network storage location specifically for secure files, you could choose to store the configuration map f

Mirth® Connect by NextGen Healthcare User Guide

mirth.properties File

This is the main configuration file that tells Mirth® Connect where to store application data, what web server ports to listen on, and which database to connect to. You can also set other security and encryption options. The following properties are supported: Property Default Value Description Directories dir.appdata appdata The location of the Application Data Directory. dir.tempdata ${dir.appdata}/temp The location of the temporary files directory, by default set inside of the Application Data Directory. Ports http.port 8080 The HTTP port to make the web server available from. This is used to access the launch page and download signed client resources from. If this property is omitted or commented out, the web server only starts up on the HTTPS port. https.port 8443 The HTTPS port to make the web server available from. This is used to access the secure opening of a page, web dashboard, and all REST API traffic (which includes the Administrator and CLI) . Password Requirements passwo

Mirth® Connect by NextGen Healthcare User Guide

Changing the Database Type

By default, Mirth® Connect is configured to connect to an embedded Apache Derby database for quick deployment, development, and testing. Warning: When using Mirth® Connect in production environments, we recommend changing the underlying database to one of the supported servers: PostgreSQL 8.3+ MySQL 5.0+ Oracle 10gR2+ SQL Server 2005+ See Also: Connect to Database using SSL/TLS Backup Current Server Configuration Change Database Settings Restart the Mirth Connect Server Restore Server Configuration Parent topic: Getting Started with Mirth Connect

Mirth® Connect by NextGen Healthcare User Guide

Installation Directory

This is the location you installed or extracted Mirth® Connect into. Typically only administrators need to have access to this, and even then usually only once when first setting up. For example this where you can edit initial configuration to change the databaseMirth® Connect points to. Application Data Directory Configuration Directory Other Files and Folders The various files and folders present in the installation directory are used to contain application configuration files and other executables.

Connect to Database using SSL/TLS

Recommendations

Before You Upgrade

Frequently Asked Questions

Installation Directory

mirth.properties File

Changing the Database Type

Installation Directory

Before You Upgrade

Frequently Asked Questions

Installation Directory

mirth.properties File

Changing the Database Type

Installation Directory