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.
Recommendations
Explore
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
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
Change Database Settings
Using the Mirth Connect Server Manager (Windows / Linux): Double-clicking the Mirth icon in your system tray to open the Mirth® Connect Server Manager. Select the Database tab. In the Type field, select the database server you want to connect to from the pull-down menu. The JDBC URL field will be auto-populated with a sample URL. In the URL field, change the IP, port, and database name as needed. Enter the Username and Password, if needed. Select Apply. Select OK to exit the Server Manager. Note: If using sqlserver, the SQL Server/Sybase (jTDS) driver is used by default. If you prefer to use the Microsoft SQL Server driver, you must edit the properties file directly (see Editing the Properties File Directly for Windows, Linux, and Mac). Editing the Properties File Directly for Windows, Linux, and Mac Parent topic: Changing the Database Type
Mirth® Connect by NextGen Healthcare User Guide
Restore Server Configuration
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 Type
Mirth® Connect by NextGen Healthcare User Guide
Backup Current Server Configuration
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 topi
Mirth® Connect by NextGen Healthcare User Guide
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 Parent topic: Getting Started with Mirth Connect
