Licensing Oracle Java – An overview of the risks you should be aware of

Java – you have definitely heard of it and you’re most probably using it every day if you use a computer. Apart from an application, Java is first of all a programming language. There are some mechanisms to help Java to be translated into machine executable code. Java Virtual Machine (JVM), plus some other utilities around it, is doing exactly that. These mechanisms (JVM and others) were implemented by multiple publishers, the initial and most popular coming from Sun Microsystems. Another popular implementation was done by BEA Systems. However, at some point, both companies were acquired by Oracle.

The initial popularity of Java was mostly generated by the open source mindset that Sun had while developing and making their implementation available to the community. This strategy turned out not to be very profitable for Sun and their acquisition by Oracle was just around the corner. After the acquisition, Oracle gradually started to adjust its strategy for licensing Java. Some of these adjustments came as restrictions in licensing the Java SE platform to get a fair compensation for the effort they’re putting into developing these products.

These restrictions are now becoming more visible in the market and more and more end users struggle to assess the impact of these changes. In our daily work we assist organizations in managing their license entitlements and deployment, and we have compiled a list with answers to the most important questions you should ask yourself to make sure you are compliant from a licensing perspective. Read our “Licensing Oracle Java – An overview of the risks you should be aware of” whitepaper and stay ahead of the game.

This article was published on 18-09-2018