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
Recommendations
Explore
Mirth® Connect by NextGen Healthcare User Guide
Editing the Properties File Directly for Windows, Linux, and Mac
Navigate to the directory where you installed Mirth® Connect. Open the mirth.properties file inside the conf folder. Edit the following properties as needed: database: The type of database server to connect to (derby, mysql, postgres, oracle, sqlserver) database.url: The JDBC URL connection string If you need to connect using SSL/TLS, typically this is where you would add additional options to the URL. See Connect to Database using SSL/TLS for additional information. database.driver: If you need to use a custom JDBC Driver class, enter that fully-qualified class name here. database.username: Username for the database connection. database.password: Password for the database connection. Save the file. Parent topic: Change Database Settings
Mirth® Connect by NextGen Healthcare User Guide
Connect to Database using SSL/TLS
By default, Mirth® Connect is configured to connect to an embedded Apache Derby database for quick deployment, development, and testing. When using Mirth® Connect in production environments, we recommend changing the underlying database to one of the supported servers: PostgreSQL 8.3+ MySQL 5.6+ Oracle 10gR2+ SQL Server 2005+ There is more information on changing the database type here: Changing the Database Type And more information about configurable options in mirth.properties here: mirth.properties File Typically these database connections are not encrypted by default. The instructions to enable SSL/TLS traffic for database connections differ depending on the database and JDBC driver you are using. Here are some instructions for each of the supported backend databases. For more information, consult the manuals for the specific database and JDBC driver you are using. Importing the Database Server Certificate PostgreSQL MySQL Oracle SQL Server Parent topic: Secure Installation and De
Mirth® Connect by NextGen Healthcare User Guide
The Mirth® Connect Server Manager
The Mirth® Connect Server Manager enables you to configure and access your Mirth® Connect Server. For Windows and Mac OS X version installations, the Mirth® Connect Server Manager application resides in the system tray (Windows) or in the Applications > Mirth Connect folder (Mac). Service Tab The Service tab provides an easy way to start, restart, stop, and refresh the service, rather than using the task scheduler or command line. Server Tab The Server tab enables you to enter details about your ports, server memory, log levels, and view log files. Database Tab The Database tab is where you can to manage Mirth® Connect's internal database. Info Tab The Info tab shows the Mirth® Connect server and Java versions as well as the server ID and a link to the NextGen Healthcare website. Parent topic: Getting Started with Mirth Connect
Mirth® Connect by NextGen Healthcare User Guide
Mirth® Connect System Requirements
The Mirth® Connect server is a fully standalone application that does not require an application server. You do not need to install a container service like Tomcat, Glassfish, etc. The following requirements apply to any computer running the Mirth® Connect server, Command Line Interface, or Administrator. Operating System Requirements Windows XP or later macOS (OS X) 10.7 Lion or later Linux Processor (CPU) Requirements 32-bit or 64-bit x86 processor Note: Apple M1 and M2 processors are currently not fully supported. Java Requirements Mirth® Connect is written in Java and runs on any system capable of running a Java virtual machine. Database Requirements The Mirth® Connect Server requires a database for configuration and message storage. Parent topic: Getting Started with Mirth Connect
Mirth® Connect by NextGen Healthcare User Guide
Database Requirements
The Mirth® Connect Server requires a database for configuration and message storage. For quick deployment, development, and testing, Mirth® Connect already includes an embedded database (Apache Derby™). For production, the latest version of Mirth® Connect supports the following databases: PostgreSQL® 8.3+ MySQL 5.6+ Oracle® 12c+ SQL Server® 2005+ Note: The above database requirements apply only to what is used for the configuration and message storage for the Mirth® Connect server and have no impact on which databases Mirth® Connect can interface with. Parent topic: Mirth Connect System Requirements
Mirth® Connect by NextGen Healthcare User Guide
Restart the Mirth® Connect Server
If you are using a Windows or Linux operating system and you have Mirth® Connect installed as a service/daemon, open the Server Manager. Select Restart and verify the server has started up successfully. Parent topic: Changing the Database Type
