Did this article resolve your question/issue?



How to change the Java version for an OpenEdge installation on Windows

« Go Back


TitleHow to change the Java version for an OpenEdge installation on Windows
URL Name000043873
Article Number000166377
EnvironmentProduct: OpenEdge
Version: 10.x , 11.x, 12.x
OS: All supported platforms
Question/Problem Description
How to change the JDK/JRE version for an OpenEdge installation on Windows.
How to change the Java version for an OpenEdge installation on Windows.
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Note: Please make sure that the new Java version is supported with the specific OpenEdge version. Refer to the Product Availability and Life Cycle Guide for more details:  In OpenEdge Versions 12.1 and later

OpenEdge 12.1 and later are no longer ship with Java, which means you have to install the certified version before running the OpenEdge Install. Post-install, the Java vendor can be changed or Java patch level can be upgraded, as long as you stay within the supported Minor version (JDK 11.0 not 14.0)

Java patches of a certified version of Java will be supported by default. This policy is based on assumption that Java patches do not alter any existing behavior or functionality. Should an issue arise we will provide technical support when customers are using a more-current patch release. With our certification on OpenJDK, this will cover any vendors offering i.e. we will support any OpenJDK version commercially available with the caveat that if there is an issue we need to be able to reproduce it on the version of OpenJDK that we certified on. In general we expect that any new release of OpenJDK is fully tested by the provider.

After you have installed OpenEdge the current configuration needs to be upgraded to reflect the change. The full instructions are provided :
In summary: After stopping the current Fathom and AdminServer, the following need to be updated to the new JDK

1.   The new value of the JAVA_HOME environment variable in <DLC>/properties/
2.   JDKHOME and JREHOME Registry keys need to point to the new JDK :
3.   Developer Studio environments need to open <DLC>/oeide/eclipse.ini  and update the -vm argument
4.    OEM / OEE tailoring needs to be updated.

In OpenEdge Versions 12.0, 11.x, 10.x

Before upgrading the shipped version, please refer to the following Article: To change the Java version for an OpenEdge installation on Windows:

Install the required 32-bit or 64-bit Java as instructed by the vendor.

Method 1: Update the Registry
  1. Stop all OpenEdge processes.
  2. Open the Windows Registry Editor (regedit).
  3. Change the path for the each of the following properties to point to the new JDK:
Note: In the case of a 32-bit OpenEdge installation on a 64-bit Windows the registry key is: 

Method 2: Copy the required java install to the current DLC installed java
  • Make a backup of the current %DLC%\jre and %DLC%\jdk directories and delete their content.
  • Copy the jdk and jre directories from the required Java installation.
  • Paste them to the %DLC% directory overwriting the old ones.
Additional Considerations:

OpenEdge Explorer or OpenEdge Management:
  • %DLC%/properties/ file, change the path for "tools.jar"
  • %DLC%\oeide\eclipse\eclipse.ini, change the value of the -vm argument to the location of the javaw.exe
Last Modified Date12/15/2020 11:18 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.