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.

• 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 example pgAdmin, MySQL Administrator).

Changes to some custom configuration files may need to be manually copied over after the upgrade. If you have made changes to any of the following files, copy them to a location outside of your existing mirth_home directory before running the new Mirth Connect installer. After Mirth® Connect is upgraded, update the newly installed files with your custom changes.

• Custom database drivers: If you have added custom database drivers they will be preserved in custom-lib during the upgrade. However, you will need to back up your additions to "mirth_home/conf/dbdrivers.xml".
• Java JVM parameters: If you have added any Java JVM parameters or changed any of the default heap size settings, create a backup of any "mirth_home/*.vmoptions" files
• CLI configuration: If you have made any changes to the CLI configuration file, create a backup of "mirth_home/conf/mirth-cli-config.properties".: