4.6.0 Upgrade Notes
This topic coveres the improvements and the new features included in Mirth® Connect version 4.6.0.
Change in Licensing Model
With the release of 4.6, Mirth® Connect has transitioned from a dual license model (open-source and commercial) to a single Enterprise license model that is closed-source and proprietary. This change is designed to enhance the quality and reliability of our product, ensuring that you receive the best possible experience.
Upgrading to Mirth® Connect 4.6 is similar to previous releases. However, if you are using an open-source version, you need to contact our sales team at mirthconnectsales@nextgen.com to obtain a license, this allows you to download the software. For current clients, you can download the software from the Success Community and proceed with the upgrade as usual.
For more details about this change please refer to our FAQs.
Updating Custom Extensions
To update the custom extensions, refer to the topic 4.6.0 Updating Custom Extensions.
New Docker Image Distribution of Mirth® Connect
Updating Minimum Supported MySQL Server Version in Mirth® Connect 4.6.0
The minimum MySQL Server requirements have been updated. Mirth® Connect now supports MySQL 8.0+ instead of 5.7+.
Updating Minimum Supported Java Version in Mirth Connect 4.7.0
Beginning with Mirth® Connect version 4.7.0, the minimum supported Java version will be updated from Java 8 to Java 17.
Removed Libraries
We have removed and replaced the following libraries from all Mirth® Connect Components:
javax.annotation-api-1.3.2.jar -> jakarta.annotations-api-1.3.5.jar
javax.inject-2.4.0-b31.jar -> jakarta.inject-2.6.1.jar
javax.ws.rs-api-2.0.1.jar -> jakarta.ws.rs-api-2.1.6.jar
validation-api-1.1.0.Final.jar -> jakarta.validation-api-2.0.2.jar
If you are referencing these libraries in your code, please refer to the upgraded libraries instead.
We have removed the following libraries from all Mirth® Connect Components:
jersey-guava-2.22.1
If you are referencing any of these libraries in your code, please include them in your custom libraries instead.