To Edit the mcserver.vmoptions file
Access the folder in which
Mirth® Connect
is installed.
Note:
The mcserver.vmoptions file can typically be found in the following location:
Windows
: C:\Program Files\
Mirth® Connect
\mcserver.vmoptions
MacOS
: /Applications/
Mirth® Connect
/mcserver.vmoptions
Open the
mcserver.vmoptions
file.
Set
-Djava.awt.headless=false
.
Save the updated file.
Recommendations
Explore
Mirth® Connect by NextGen Healthcare User Guide
Use the Debugger
Note: mcservice.exe is currently not supported for Debug mode. Debug mode is not recommended for Clustering environment (Basic or Advanced Clustering). Within Mirth® Connect, select Channels. In the Channels list, select the channel you would like to debug. Note: You can currently only debug one channel at a time. In Channel Tasks, select Debug Channel. On the Debug Channel window, select the channel script(s) you would like to use to debug the selected channel. Select OK. A separate debugger window opens for each selected script, and for each destination connector. Process the selected channel (For Example: send a message). The Debugger window(s) will pop-up based on the options you selected. To exit the debug mode, close the debugger window(s) or undeploy the channel. Note: The channel will not stop or undeploy properly if the debugger is waiting for user operation, such as selecting “Go”. Parent topic: Mirth Connect Debugger
Mirth® Connect by NextGen Healthcare User Guide
Mirth® Connect Debugger
The Mirth Connect Debugger tool allows you to troubleshoot JavaScript errors throughout the Mirth® Connect application. The Debugger can be used for the following scripts and connectors: Deploy, Undeploy, Preprocessor, and Post Processor scripts Attachment/Batch scripts Source Connectors: Filters/Transformers Database Reader and JavaScript Reader types Destination Connectors: Filters/Transformers. Database Writer and JavaScript Writer types Response transformers Before You Begin If your Java application does not interact directly with a user, use the following steps to change the Headless mode to false. Setting this mode to false means that your Java application: Displays windows or dialog boxes. Accepts keyboard or mouse input. Uses any heavyweight AWT (Abstract Windowing Toolkit) components. To Edit the mcserver.vmoptions file Use the Debugger Debugger Window Debugger Menus Parent topic: Mirth Connect and JavaScript
Mirth® Connect by NextGen Healthcare User Guide
After the Upgrade
Java JVM parameters: Restore the changes in your backed up "*.vmoptions" files to the corresponding *.vmoptions files in "mirth_home". CLI configuration: Restore the changes in your backed up "mirth_home/conf/mirth-cli-config.properties" file. Start/Restart the server. Custom extensions: Install new versions of any custom extensions. Parent topic: Upgrade Guide
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
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
License Manager User Guide
Connect Through a Proxy Server
If you are unable to allow outbound internet access for the machine that Mirth® Connect by NextGen Healthcare is running on, another option is using an HTTP web proxy or firewall that supports HTTP CONNECT proxy requests. To do this, edit either the mcserver.vmoptions or mcservice.vmoptions file, depending on whether you're running mcserver directly, or using the service/daemon to run mcservice. Add the following options: -Dconnect.license.proxy.host=thehost-Dconnect.license.proxy.port=theport Replace "thehost" and "theport" with the actual hostname/IP and port of your HTTP proxy server. If your proxy server requires Basic Authentication, you can specify those credentials with these options: -Dconnect.license.proxy.username=theusername-Dconnect.license.proxy.password=thepassword Parent topic: Online Validation
