Configuration

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

Configuration Directory

This directory contains the main configuration files Mirth® Connect needs in order to start up correctly. Modifying the configuration requires a restart of Mirth® Connect. The following files are found here: dbdrivers.xml File log4j2.properties File log4j2-cli.properties File mirth.properties File mirth-cli-config.properties File dbdrivers.xml File log4j2.properties File The log4j2.properties file specifies where to write log files to and how verbose the logs should be. log4j2-cli.properties File The log4j2-cli.properties files is the same as the log4j2.properties file, except that it is specific to the Command Line Interface. mirth.properties File 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. mirth-cli-config.properties File Parent topic: Installation Directory

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

Logs

Whenever an issue occurs, it may be helpful to look at the server logs. These are stored in the "logs" folder inside your Installation Directory. The "mirth.log" file is the most recent log. Parent topic: Troubleshooting

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.

Mirth® Connect by NextGen Healthcare User Guide

Manually reset a password in the database

If you forgot or lost your password and cannot login, you can reset the password in the database manually. You will need to use a third-party SQL client, either a command line tool or a graphical client like SQuirreL SQL Client. First locate the ID of the user you want to reset the password for. SELECT * FROM PERSON; The users are in the PERSON table, and the "admin" user usually has an ID of 1: Issue an UPDATE statement to the PERSON_PASSWORD table, using the ID of the user located in the previous steps. Change the question mark in the statement below to the correct ID. UPDATE PERSON_PASSWORD SET PASSWORD = 'YzKZIAnbQ5m+3llggrZvNtf5fg69yX7pAplfYg0Dngn/fESH93OktQ==' WHERE PERSON_ID = ?; The above example uses a salted hash for the password "admin", assuming that the digest algorithm is still set to SHA-256. After issuing the above UPDATE statement, you should be able to login with a password of "admin". After logging in change the password as you see fit. Parent topic: Troubleshooting

Configuration

Recommendations

Before You Upgrade

Configuration Directory

Frequently Asked Questions

Logs

Installation Directory

Manually reset a password in the database

Before You Upgrade

Configuration Directory

Frequently Asked Questions

Logs

Installation Directory

Manually reset a password in the database