Oracle® changed the Java license terms with the release of Java 11. From then on, a commercial license is required for its use. How does this change affect the relationship between Java and Mirth Connect? Do we need to make any changes to our integrations?

Understanding the Java 11^® license changes #

We’ve all been installing and using Java for many years, but, with the release of Java 11 in 2018, something has changed that could significantly affect us. Here’s all the information you need to continue using and developing with Java without any issues.

In September 2018, Oracle® released Java 11. This is a major version that will replace Java 8 in many environments as the default version. This new version has two very important features:

• Java 11, as an LTS (Long-Term Support) version like Java 8, marks a trend in Java’s development cycle. With the end of support for Java 8, Java 11 and subsequent LTS releases have become the go-to versions for most production environments. These LTS versions ensure continued support and stability, making them a reliable choice for long-term use.
• It requires a commercial license for its use in production. Oracle has changed the Java license, and this is where doubts begin.

Does this mean I will have to pay to use Java?
Yes and no. Don’t panic, let’s see what we can do.

The flavors of Java JDK #

JDK stands for Java Development Kit and is the key resource for developing using Java and for running Mirth Connect. However there is not a unique version of Java JDK, but several ones, which are explained below.

Oracle JDK #

Oracle JDK is Oracle’s commercial JDK. Until Java 11, Oracle offered its JDK (Java Development Kit) for free. It also offered the possibility of contracting a commercial license for this same JDK.

But this has changed starting from Java 11. We can continue using the Oracle JDK for development and testing, but we cannot use it in production without a commercial license.

OpenJDK to the rescue #

OpenJDK is the open source distribution and can be used without limitations for development, testing, and production. Therefore, if we do not have a commercial license, we will have to use one of the OpenJDK distributions.

There are many distributions of OpenJDK, three of the main ones are:

• OpenJDK HotSpot: Oracle’s own open source distribution.
• OpenJDK OpenJ9: Eclipse’s distribution, designed for reduced memory usage and faster startup.
• Azul Zulu: Azul Systems’ OpenJDK distribution.

On the website Adoptium, we can find Eclipse version. Although there are many other OpenJDK distributions, each with its update model, support, and backed by different organizations. Java Almanac offers a good starting point to look for a distribution.

Mirth Connect, Java, and OpenJDK #

Mirth Connect is developed in Java and therefore needs Java installed to function. Additionally, version 3.7 of Mirth Connect is the first to support Java 11. So, we might wonder what changes Java 11 brings that affect Mirth Connect.

Well, Java 11 brought two important changes, one technological and one legal that we should know well:

• First, Java Web Start (JNLP) is retired: this was the mechanism used to launch the Mirth Connect Administrator. So, from Java 11, this method will no longer be available, and we will have to use the Administrator Launcher (which does not depend on JNLP).
• And second, a commercial license is now required to use Oracle Java in production. Therefore, if we do not have a commercial license, we must use OpenJDK to deploy Mirth Connect.

Fortunately, from Mirth Connect 3.7 both Oracle JDK and OpenJDK are supported, so we can use either without any problem.

Furthermore, OpenJDK and Oracle JDK are functionally identical from Java 11 onwards, so we do not have to worry about compatibility issues.

Additional resources:

• Learn more about Mirth Connect Administrator.
• Download Mirth Connect.
• Learn more about Administrator Launcher.
• Download Administrator Launcher.

How does Java version affect my integrations with Mirth Connect? #

We may find ourselves in different scenarios depending on our starting situation:

System with Mirth Connect 3.7 or later #

Mirth Connect 3.7.0 is the first version to be compatible with Java 11, but it is also compatible with Java 8. So we can take any of these options:

• Continue using Java 8:
  • If we have a commercial license, we can continue using Oracle Java 8 and continue receiving support until March 2030 with extended support.
  • On the other hand, if we do not have a commercial license, Java 8 is outdated and updates are only released for development or personal use. Therefore, it is highly advisable to switch our production systems to OpenJDK or to purchase a commercial license.
• Switch to a newer JDK version or later LTS releases:
  • If we have a commercial license, we can use a newer Oracle JDK LTS version in production with support and updates.
  • Conversely, if we do not have a commercial license, we CANNOT use Oracle JDK in production. Doing so risks receiving a call from Oracle asking for more than explanations. In this case, it’s better to use OpenJDK in one of its versions.

Tip: Go to our downloads page to get the most recent version of Mirth Connect.

Previous Versions of Mirth Connect #

Previous versions of Mirth Connect are completely outdated and have known security risks, please use a recent and secure version of Mirth Connect. In the case that we have a legacy system that cannot be updated, we must take into account that versions prior to 3.7 are not compatible with Java 11, so we will need to use another compatible version, preferably OpenJDK 8.

You can learn more about the compatibility between Mirth Connect and Java versions in our article on Mirth Connect system requirements.

Tip: Avoid future headaches, choosing wisely. How to choose the right Mirth Connect version?

Timeline for Oracle Java versions #

To plan our next migrations, we can find the main milestones in the life of Java 8 and later on the Oracle Java SE Support Roadmap.

Conclusion #

In summary, Oracle’s license change with Java 11 is something to be taken into account, as it can cause us to violate the license unknowingly while using Mirth Connect. Violating the license is serious because it can cause legal problems, which are more difficult to solve than code issues.

However, the solution is simple and involves choosing one of the two available options:

• Contract a commercial license from Oracle.
• Use OpenJDK.

Although, in many cases, the decision does not depend on us but on our clients and employers, we believe it is important to know the reality of the tools we use daily, like Java. Especially if knowing it can prevent problems.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.