Change Database Settings
- Select the Database tab.
- Enter the Username and Password, if needed.
Recommendations
Mirth® Connect by NextGen Healthcare User Guide
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 SettingsEditing the Properties File Directly for Windows, Linux, and Mac
Mirth® Connect by NextGen Healthcare User Guide
Launch the Mirth Connect Administrator (see Mirth Connect Administrator Overview) . In the Mirth Connect pane, select Settings. Select the Server tab if not already selected. In the Server Tasks pane, select Restore Config. Select the server configuration XML file you exported earlier, then select Open. You will be prompted to confirm your action. You can also choose whether or not you want channels to automatically be deployed after the restore finishes. Select Yes to begin the restore process. Once the restore process is complete, a dialog appears indicating whether the restore was successfully performed. Select OK to close the information message. Parent topic: Changing the Database TypeRestore Server Configuration
Mirth® Connect by NextGen Healthcare User Guide
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 TypeRestart the Mirth® Connect Server
Mirth® Connect by NextGen Healthcare User Guide
Before you begin A Server Configuration file is a snapshot of your current server settings, including all channels, alerts, scripts, and other properties. This configuration may be backed up from one Mirth® Connect server and restored into a different server. Note: If you have just installed Mirth® Connect and you do not yet have any channels or other configurations, you can skip this section. Use the following steps to backup your server configuration Log into the Mirth Connect Administrator (see Mirth Connect Administrator Overview) . In the Mirth Connect pane, select Settings. Select the Server tab. In the Server Tasks pane, select Backup Config. Enter a location to save the server configuration XML file, then select Save. Review the Information message, then select OK. Warning: The Server Configuration file does not include Users, Events, or Message / Attachment data. To export events, see Searching Events. To export message / attachment data, see Message Browser Tasks. Parent topiBackup Current Server Configuration
Mirth® Connect by NextGen Healthcare User Guide
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 ConnectChanging the Database Type
Mirth® Connect by NextGen Healthcare User Guide
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