How are Control-M products that use Java affected by announcements from Oracle relating to changes in the licensing policy and release cadence of Java software?
Oracle Announcemnts: http://www.oracle.com/technetwork/java/eol-135779.html https://www.java.com/en/download/release_notice.jsp |
Oracle recently announced a major change to their licensing policy and release cadence for Java SE (Standard Edition including both JDK and JRE). Oracle has moved Java SE to a Long-Term-Support (LTS) release and non-LTS release (end of life in 6 months) cadence. The open source distribution (OpenJDK) will move to the non-LTS release schedule with new releases scheduled every 6 months. The LTS releases require a commercial license and will be scheduled every 3 years. Oracle has stated that customers can remain on the non-LTS release publicly available for 6 months, but then must upgrade to the latest release every 6 months as Oracle will no longer provide public updates (including security vulnerability updates) for prior releases. For customers that require more stability and can’t align to a 6-month upgrade cadence, only the commercial option will provide updates to security vulnerabilities for prior versions. Commercial Premier Support will be available for 5 years after an LTS release. Starting from Control-M release 9.0.19.100, Control-M customers will have one of the following options: 1. Use of OpenJDK: - Control-M 9.0.19.100 will be released with OpenJDK. This allows customers' to use Control-M without requiring commercial support from Oracle or Azul.
- Control-M 9.0.18 the customers will be able to point Control-M BMC_JAVA_HOME variable to their version of Open JDK 8
Additional patches are required for EM, Control-M/Server and Control_M/Agent,. Refer to the A-Z list for each of the components for instructions on how to download the patches.
2. Use of a commercial JDK: - BMC will additionally verify major versions of the Oracle and Azul JDKs, and enable the usage of these, for customers that have third party commercial support agreements in place. Please refer to documentation for the use of BMC_JAVA_HOME and procedure for supporting external Java
Control-M for Managed File Transfer now includes OpenJDK starting with release 9.0.19.100 but does not support BMC_JAVA_HOME. 3. Are there liabilities with using Oracle Java SE releases embedded in Control-M under previous licenses, such as the BCL? link from Oracle https://www.oracle.com/java/technologies/javase/jdk-faqs.html You may continue to use releases you have downloaded under the terms of the license under which you downloaded them. Legacy releases are still available in the Java Archives. Note that older versions of the JRE and JDK are provided to help developers debug issues in older systems. They are not updated with the latest security patches and are not recommended for use in production. Oracle strongly recommends that you remain on an up-to-date version of Java with the latest performance, stability and security updates. NOTE: Control-M application plugins that are not bundled into the Control-M Application Pack have a separately planned migration path to OpenJDK, and continue using Oracle JDK 1.8.For more information see 000166732. For more information, please refer to following document: http://documents.bmc.com/supportu/documents/96/27/509627/509627.pdf |