36 days until Oracle starts charging for Java, are you prepared?

Oracle Java Compliance Risk Analysis

In January 2019, all organizations should expect cost increases from the use of Java as Oracle has elected to begin charging for any type of Java updates in a commercial, production or business situation.

Whilst license cost increases are inevitable, Oracle will take any failure to purchase a license very seriously. Incompliance with the Oracle’s license terms could result in significant financial implications, as well as troublesome engagement with Oracle’s audit team.

The updates in question include product enhancements, critical patches, bug fixes etc.

It is therefore essential for any organization running Java to analyze the implications of the changes and understand the liability in its environment.

The ensuing table provides an understanding of the current Java release roadmap:

VersionJava 8Java 9 – Non LTSJava 10 – Non LTS
Release DateMarch 2014September 2017March 2018
End of Free Updates: CommercialJanuary 2019March 2018September 2018
End of Free Updates: PersonalDecember 2020March 2018September 2018

 

Subsequent to the release of Java SE 8, Oracle has positioned releases as Long-Term Support (LTS) editions every three years. Non-LTS releases are thought as an aggregate set of product enhancements of the most recent LTS release.

In effect, Java SE9 (Non-LTS) release is succeeded by Java SE 10 (Non-LTS) release and then by Java SE 11 (LTS) release. Java SE 11 is a Long-Term Support release and as such, Oracle customers will receive Premier Support and interval releases even after the release of Java 12 (Non-LTS).

 

Xensam’s Oracle Java Compliance Risk Report

Xensam has dynamic software recognition that is supported by Machine Learning. Even before January 2019 the Xensam’s Oracle Java Compliance Risk Report analysis will identify which versions of Java are deployed in your environment and the potential liability in January 2019. Xensam’s Active Usage will also show whether any of these deployments are ineffectively deployed and therefore, can be removed to save the need for a license.

 

Xensam Oracle Java Risk Report

Xensam’s Oracle Java Risk Report

 

When Java deployments do require a license purchase, Xensam’s powerful Xource database will immediately show its compliance position, as well as unprecedented usage metrics that will enable advanced license and cost optimization.

Please contact your local representative or email info@xensam.com to learn more about Xensam’s Java capabilities or to arrange a product demo.