- Java Licensing: Oracle’s first ‘not free for production use’ patchset.
- Oracle Java Datasheet
- Java теперь платная? Развенчиваем слухи (или нет?)
- Что произошло
- Что-а-а?
- Зачем они это сделали?
- Что насчет Java 8, 9, 10, 11.
- Это касается JRE?
- Это мне надо теперь все снести на продакшене.
- А что теперь делать?
- А от OpenJDK ничего не сломается?
- Oracle Java License Change: Everything You Need to Know
- How Much Does Java Cost?
- How did Java Licensing Change?
- Which Java Versions Don’t Require Licensing Fees?
- Oracle Java License Change: Commercial vs Personal Use
- What Are Deployment Rule Sets?
- How Can Deployment Rule Sets Save Money on Java Licensing?
- Using PolicyPak to Simplify Deployment Rule Sets
Java Licensing: Oracle’s first ‘not free for production use’ patchset.
Update January 2023 – As of 24 January 2023, Oracle changed the way that it charges customers for using Oracle Java SE: they no longer sell it in the Processor and Named User Plus metrics. Instead, it is ONLY available under the Oracle Java SE Universal Subscription on the basis of Employees – i.e. all your employees plus those of your outsourcers providing support to your business. For more information, please review this page.
Java underpins a wide variety of enterprise software, particularly on the server side, and has historically been considered ‘free’ by businesses.
Recent changes to the way Oracle Java is licensed and supported will affect any organisation that currently relies on an up-to-date Oracle Java Virtual Machine in any production capacity. This, in turn, will affect how organisations choose to architect and deploy technologies based on the Java language, both packaged and bespoke solutions.
The 16th of April means the release of Oracle Java 8 update 211 / 212 – also known as Oracle’s first ‘not free for production use’ patchset.
The important thing to note is that this update will be released under the new Oracle Technology Network License Agreement for Oracle Java SE and so you must read it very carefully and understand the terms before you download or use it. It is not as simple as saying you only need a license in production (and be careful with the definition of production); nor is it a case of ‘you now need a license’ (which we have seen people saying – remember, Java has always needed a license, just not always a paid-for license!). You may want to restrict access to Oracle’s download site if you are not sure who may download updates.
Equip yourself with the necessary knowledge and business strategies to navigate Oracle Java Licensing in 2019 through our series of insights:
If you are unsure as to what the 2019 change means, how it applies to your estate or whether you need to pay for a subscription, contact our expert team for a licensing consultation.
About Version 1
Version 1 has many years of specialist expertise and experience managing Java license installations for our customers. As an independent advisor, we recommend that all organisations using Java should carry out an urgent survey of their Java usage, cataloguing the version number in use, its purpose, and the infrastructure upon which it runs.
Oracle Java Datasheet
In our latest Java Datasheet, we discuss a range of topics including how to manage your Oracle Java SE Subscriptions and our Oracle Java Discovery Approach, which lays out the high-level steps for your approach to assessing Oracle Java requirements.
Java теперь платная? Развенчиваем слухи (или нет?)
Уже 2 дня как вступили в силу изменения лицензионной политики Oracle на распространение сборок Java SE. В среде разработчиков-слоупоков (я тоже в их числе) начали носиться кошмарные слухи.
Что произошло
В середине 2018 года Oracle объявил, что собирается изменить лицензионную политику. 16 апреля 2019 года изменение вступило в силу. Теперь все опубликованные после этой даты сборки Java SE можно использовать бесплатно только для личных нужд и с целью разработки. Для использования в коммерческих целях (в том числе для продакшена) надо оформить платную подписку у Oracle.
Что-а-а?
Oracle выстрелил себе в ногу и убивает Java? Нет, не убивает. Нет, не выстрелил. Но проблем халявщикамвсем нам подкинул. Давайте быстро разберемся, что это означает в практическом плане, без этих ваших GPL, BCL, WTF…
Зачем они это сделали?
Как известно, Oracle на самом деле собирает и публикует две версии JDK: Oracle JDK (aka Java SE, расположена на java.com) и Open JDK (расположена на openjdk.java.net).
Чтобы понять смысл всей затеи достаточно взглянуть на этот слайд из их презентации:
Для коммерческой сборки поддержка длительная. Для бесплатной – короткая. Т.е. чтобы накатить патчи на бесплатную OpenJDK через полгода надо будет проапгрейдить версию. Oracle JDK будет выпускать патчи еще 5 лет после выпуска. Поэтому она платная.
Что насчет Java 8, 9, 10, 11.
Это касается JRE?
Нигде отдельно не указывается лицензия на JRE. Считается, что раз JRE является подмножеством JDK, то и лицензионные ограничения такие же. Т.е. — да, это касается JRE.
Это мне надо теперь все снести на продакшене.
Нет. Изменения касаются только новых выпусков (после 16 апреля). Для Java 8 SE первым выпуском с ограничениями стала Update 211. Все что было выпущено ранее, можно использовать дальше без ограничений.
А что теперь делать?
Ставить OpenJDK. Но сам OpenJDK от Oracle не имеет официального виндового установщика (и автоматического апдейта), надо его распаковывать руками.
Если вам важен именно установщик, остается только пользоваться ранними релизами от Oracle (Update 202). А апдейты все равно придется отключить.
UPD: В комментариях подсказали, что существуют бесплатные бинарники с установщиком AdoptOpenJDK, поддерживаемые comunity.
Еще можно обратить внимание на Liberica JDK, которая поддерживается JetBrains.
А от OpenJDK ничего не сломается?
Не должно (с). Отличия в функциональности минимальны и очень мало кого затрагивают. При этом Oracle планомерно уменьшает эти различия, вливая их в OpenJDK или удаляя совсем.
Oracle Java License Change: Everything You Need to Know
The Oracle Java license change has become a hot topic amongst information technology professionals. As of January 2019, administrators who install Java 8 U 202 and later are only able to get security updates when they purchase support for each desktop. Furthermore, Java 11 and above is only available from Oracle under a commercial support agreement. The Java Oracle license change has raised concerns because support costs are expected to rise. Fortunately, you can avoid costs associated with Java licensing changes.
In this blog, we’ll explain the Oracle Java license change and demonstrate how Java Deployment Rule Sets (DRS) can help you bypass unnecessary costs.
How Much Does Java Cost?
The current cost of an Oracle Java license is $30 per seat up to 1,000 named user plus seats per year. The price decreases as the number of seats increase, with the lowest cost per Java license at $15.00. The prices include bug fixes and security updates for the specific versions of Java that you might need on your endpoints. At any rate, builds of the latest version are available from Oracle for free under an open source license. For greater volumes of commercial licenses, you should speak with a salesperson.
How did Java Licensing Change?
Oracle is no longer providing free public updates to Java 8. Older, minor releases of Java are still available at no cost for Java 8, Java 7, and Java 6. Oracle previously released these older versions as free public updates. The Oracle Java license change kicks in for Java 11 and later. With these releases, Oracle now requires a commercial subscription for the use of the Oracle Java Runtime Environment.
Which Java Versions Don’t Require Licensing Fees?
You can avoid Java licensing fees by using Java 8 U 202 and earlier. However, when Java 8 U 202 expires, your users are presented with the pesky pop-up shown in Figure 1. Furthermore, you must accept that Oracle will no longer provide updates or patches.
Figure 1: Oracle Java pop-up
Oracle Java License Change: Commercial vs Personal Use
Commercial enterprises that use Java 8 will not be able to obtain free updates. However, updates are available for personal use through the end of 2020. Although Java is available for download on Java.com, organizations that use those builds for commercial gain violate the license terms.
What Are Deployment Rule Sets?
A Deployment Rule Set (DRS) is a mechanism that administrators use to control the execution of applets and Web Start applications. A DRS acts like a version “map” between applets and Java Runtime Environments (JRE). DRS mappings enable users to have a mix of older Java 6, 7, 8, and 9 applications on the same machine without any virtualization beyond the Java Virtual Machine.
How Can Deployment Rule Sets Save Money on Java Licensing?
Some websites require a specific version of Java to function. By using a DRS, you can ensure that only free versions of Java are being used in your environment.
Using PolicyPak to Simplify Deployment Rule Sets
PolicyPak Java Rules Manager creates a secure connection between specific websites and their compatible versions of Java. First, PolicyPak allows you to download and utilize whatever older JREs are needed (as free versions). Second, PolicyPak enables you to download, install, and utilize the final public release of Java 8 (Java 8 U 202) alongside older versions of Java. Finally, PolicyPak simplifies the creation and execution of Deployment Rule Sets and forces applets to run specific versions of Java (or the latest in the family).
Jeremy Moskowitz is a recognized expert in the computer and network security industry. Co-founder and CTO of PolicyPak Software (now part of Netwrix), he is also a 17-time Microsoft MVP in Group Policy, Enterprise Mobility and MDM. Jeremy has authored several best-selling books, including “Group Policy: Fundamentals, Security, and the Managed Desktop” and “MDM: Fundamentals, Security, and the Modern Desktop.” In addition, he is a sought-after speaker on topics such as desktop settings management, and founder of MDMandGPanswers.com.