Java Did What? Understanding How 2019 Java Licensing Changes Impact You
If you have Java in your environment you may have already heard that in 2018, Oracle announced deep Java licensing changes to Java Standard Edition (SE) that took effect in January 2019. These changes have left the community with many unanswered questions about licensing and about their environments, not in the least of which is, “What should our Java licensing look like?” Similarly, those who have already made their decision on Java licensing are also left wondering, “Have I under or over provisioned licensing and what’s the impact if I’m not compliant?”
If you’ve been wondering the answer to either one of these questions, this blog post might be for you. But first, let’s review, what were Oracle’s Java licensing changes?
Clearing up the confusion: what are the Java licensing changes?
In short, since January 2019, Oracle no longer issues public updates for commercial users of Java SE 8 which means free updates for commercial use are no more. Oracle has officially moved Java SE to a subscription-based model. Whether an organization has previously purchased a perpetual license of SE or uses OpenJDK, these licensing changes will likely impact any organization looking to keep up with support. Read more about Oracle’s support roadmap for Java SE here.
|Java Platform Products|
|Named User Plus||Software Update License & Support||Processor License||Software Update License & Support|
|Java SE Advanced Desktop||40||8.80||–||–|
|Java SE Advanced||100||22.00||5,000||1,100.00|
|Java SE Suite||300||66.00||15,000||3,300.00|
Prices in US (Dollar)
Source: As dictated in Oracle’s Global Price List last updated June 19, 2018.
Perhaps the easiest way to make sense of the changes is to think of Red Hat’s open source model. Red Hat offers its software for free, but enterprise customers are sold support services and premium subscriptions. In much the same way, the changes Oracle announced mid 2018 are moving Java in that same direction. Oracle will continue to offer its OpenJDK for free, but they will start charging for enterprise support.
So, is Java still free? It depends…
Do I need to start paying for Java licenses?
If any of the following statements apply to you, you will likely require an Oracle license:
– I use commercial features of Java SE
– I use Oracle Java SE v11 +
– I need support from Oracle
– I use Java SE versions for longer than 6 months
– I am running unsupported Java SE in my environment
If you want to use Java for free for commercial use, one way of doing it is to use an Oracle JDK, Oracle’s OpenJDK builds and OpenJDK from other providers. This, of course, does not include support from Oracle, however.
What should my Java licensing and spend look like?
In order to answer this question, you need to have the right data on your environment and determine:
– Where Java is being used and where it has been installed
– Which versions of Java exist in your environment
– What are the applications calling Java
– How many users are there by application
Read this brief on how you can answer these questions
To help answer these questions, we have built a dashboard within SysTrack that pulls exactly this kind of data. For those unfamiliar with SysTrack, it is a solution that monitors any and everything that may be impacting end-user experience which turns out to be tens of thousands of different indicators. SysTrack gathers data on performance and usage of IT products and services and analyzes them directly from each endpoint in the environment. In the context of Java licensing changes, SysTrack data proves to be helpful because not only does it pull the Java versions in the environment and specifically which apps and users are calling it, but SysTrack also gathers and analyzes data on how virtually every IT resource and service is performing and being used, beyond Java. It can report on Office 365 licensing usage so that you can potentially scale back on E5’s just as it can determine critical compute resource usage in virtual environment, like CPU and RAM. Below you will see a screenshot of the type of data SysTrack can report to help make your decision on Java licensing and spend. Request a demo today if interested!
Alternatively, it’s important to point out Oracle has built a license tool that requires its own subscription.
What happens if I don’t purchase the subscription?
It seems the verdict is still out on how Oracle will be auditing for Java licensing and what it will mean should an organization not be compliant. However, should an organization not purchase the subscription, aside from risking non-compliance, at the very least they will be missing out on:
- early access to bug fixes
- licensing and support for cloud, server and desktop deployments
- some performance, stability, and security updates
- around the clock support
- and more (source)
Additionally, when it comes to renewal time, if an organization does not renew the subscription, they lose the rights to any commercial software downloaded during the subscription.
Digital experience monitoring software like SysTrack can help bring visibility into these critical aspects of Java licensing but also into the usage and performance of end-user technology, whether hardware or software. If you’d like to see SysTrack in action, watch this demo!
About Lakeside Software and SysTrack
Lakeside Software is a leader in digital experience monitoring. For 20 years, we have been developing software that helps IT teams have clear visibility into their environments in order to design and support productive digital workplaces. Our customers use Lakeside Software technology to perform workplace analytics, IT asset optimization, and AIOps.
SysTrack is our flagship solution. The digital experience monitoring software gathers and analyzes data on everything that may impact end-user experience and business productivity. Directly from the workspace, SysTrack captures data such as CPU, RAM, memory, and other 10,000+ data points. These are then analyzed by SysTrack and used by IT in countless ways that lower costs and optimize operations including: lowering the amount of help desk tickets, identifying over and under-provisioning, reducing time to resolution, tracking SLA performance, measuring the performance of rollouts, and so much more.