A major change to how Java is licensed and supported will start on January 31, according to Oracle. In considering these changes, Esri has decided to replace Oracle’s Java Runtime Environment (JRE) with the AdoptOpenJDK JRE, which is identical in functionality to Oracle’s JRE.
This blog outlines how ArcGIS will be affected by the changes in Java licensing and what steps need to be taken. No customers will be responsible for any additional licensing to Oracle for Java components in any current or future Esri products.
The upcoming ArcGIS 10.7 release will include the AdoptOpenJDK JRE in ArcGIS Desktop (ArcMap), ArcGIS Engine, and ArcGIS Enterprise.
For versions prior to 10.7, there is no direct impact to the functionality of software. However, customers may have questions and need recommendations on how to plan for this change particularly if they are using Java add-ins or other Java-based extensions and applications. Customers who are not using Java-based add-ins with ArcGIS products are not affected unless they have organizational policies that control the versions of Java installed by applications like ArcGIS Desktop.
What Esri software is affected by the change from Oracle’s JRE to the AdoptOpenJDK JRE?
This change affects the following software:
- ArcGIS Desktop (ArcMap) 10.6.1 and prior
- ArcGIS Engine 10.6.1 and prior
- ArcGIS Enterprise 10.6.1 and prior or ArcGIS 10.4.x for Server
Is there an impact to customers using any of the software affected?
ArcGIS Desktop (ArcMap) 10.6.1 and prior
No functional impact, which means that no existing Java add-ins will stop working on these releases of ArcGIS Desktop. After January 31, 2019, the Java runtime environment that is part of ArcGIS Desktop 10.6.1 and earlier will no longer receive updates. This is not a change as Esri has not updated Java in released versions of ArcGIS Desktop already in production in the field. We have always updated Java in our next release.
ArcGIS Engine 10.6.1 and prior
No functional impact, which means that no existing ArcGIS Engine applications will stop working on these releases of ArcGIS Engine. After January 31, 2019, all existing ArcGIS Engine applications deployed using ArcObjects SDK for Java with ArcGIS Engine 10.6.1 and earlier will no longer receive updates. This is not a change as Esri has not updated Java in released versions of ArcGIS Engine already in production in the field. We have always updated Java in our next release.
ArcGIS Enterprise 10.6.1 and prior or ArcGIS 10.4.x for Server
No impact.
What does Esri recommend that customers do?
ArcGIS Desktop (ArcMap) 10.6.1 and prior
- Upgrade to version 10.7 when available (late Q1 2019)
- Immediately begin exploring the following options:
-
- Migrate applications and add-ins to version 10.7
- Begin migrating ArcMap add-in workflows to ArcGIS Pro and customize with the ArcGIS Pro SDK
- Begin migrating existing ArcMap add-ins to .NET
ArcGIS Engine 10.6.1 and prior
- Upgrade to version 10.7 when available (late Q1 2019)
- Immediately begin exploring the following options:
-
- Migrate ArcGIS Engine Java applications to use the ArcGIS Runtime SDK for Java 100.4
- Migrate ArcGIS Engine Java applications to ArcGIS Engine 10.7 to continue Esri support
- Rewrite ArcGIS Engine Java applications to use ArcObjects SDK for .NET
ArcGIS Enterprise 10.6.1 and prior or ArcGIS 10.4.x for Server
- No need to make any changes.
If your organization has a policy that requires the use of the latest version of Java at all times, you will not be able to manually update files installed by ArcGIS Enterprise. If a security vulnerability is identified in a supported version of ArcGIS Enterprise — whether or not it is related to Java — Esri will issue the appropriate security update that includes updating the embedded version of Java if required. Customers with security concerns are encouraged to contact Esri’s Product Security Incident Response Team (PSIRT) via https://trust.arcgis.com/en/security-concern/
For more information, please read the Year-End 2018 Deprecated Features document.
Commenting is not enabled for this article.