Configuration Directory

Mirth® Connect by NextGen Healthcare User Guide

Other Files and Folders

The various files and folders present in the installation directory are used to contain application configuration files and other executables. Other files and folders present in the Installation Directory include the following: cli-lib: Libraries used by the Command Line Interface. These should not be changed. client-lib: Libraries used by the Mirth Connect Administrator. These should not be changed. custom-lib: Custom libraries can be dropped in this folder, to be used by the default library resource. docs: Contains license information for Mirth® Connect and all third-party libraries. Also contains the Javadoc documentation used by User API. extensions: Extension libraries used by the Server, Administrator, and CLI. These should not be changed. logs: This is the default location that server logs will be written into. This can be changed from the log4j2.properties file. manager-lib: Libraries used by the Server Manager. These should not be changed. mccommand(.exe): The entrypoint scrip

Mirth® Connect by NextGen Healthcare User Guide

Application Data Directory

This directory stores configuration files and temporary data created by Mirth® Connect after starting up. Usually the name of this directory is "appdata" and it resides directly inside your installation directory. However the name and location of this directory can be modified from mirth.properties. The main files/folders of note here are as follows: configuration.properties extension.properties keystore.jks server.id temp configuration.properties extension.properties The extension.properties file stores the current state of all installed extensions. Typically you do not need to edit this file, as enabling and disabling of extensions can be done using the Extensions view. keystore.jks server.id temp Parent topic: Installation Directory

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

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-cli-config.properties File

This properties file allows you to launch the Mirth Connect Command Line Interface without having to include any command line arguments like the username / password. The following properties are supported: address: The HTTPS address of the Mirth® Connect server to connect to. user: The username to connect with. password: The password to connect with. version: The version to enforce, to ensure that you do not incorrectly connect to an unexpected server version. Use "0.0.0" to allow all. script: The file to use for non-interactive script mode. Parent topic: Configuration Directory

Mirth® Connect by NextGen Healthcare User Guide

log4j2.properties File

The log4j2.properties file specifies where to write log files to and how verbose the logs should be. This file is used to specify where to write log files to and how verbose the logs should be. It is split up into the following sections: rootLogger = ERROR,stdout,foutThis is the "root" logger property which is used to denote the appenders to include and the root level. The following levels can be set in order from least to most logging: OFF FATAL ERROR WARN INFO DEBUG TRACE ALL # stdout appenderappender.console.type = Consoleappender.console.name = stdoutappender.console.layout.type = PatternLayoutappender.console.layout.pattern = %-5p %d{yyyy-MM-dd HH:mm:ss.SSS} [%t] %c: %m%nThis appender ensures that all logging can redirect to STDOUT, if you are running Mirth Connect from an attached shell. # file appenderdir.logs = logsappender.rolling.type = RollingFileappender.rolling.name = foutappender.rolling.fileName = logs/mirth.logappender.rolling.filePattern = logs/mirth.log.%iappender.rol

Configuration Directory

Recommendations

Other Files and Folders

Application Data Directory

Before You Upgrade

Installation Directory

mirth-cli-config.properties File

log4j2.properties File

Other Files and Folders

Application Data Directory

Before You Upgrade

Installation Directory

mirth-cli-config.properties File

log4j2.properties File