After you have installed OpenEdge, you might want to:

  • Upgrade the JDK to a different distribution
  • Change the location of the JDK on your computer

After upgrading or installing a new JDK, you must upgrade your OpenEdge configuration by completing the following steps:

  1. Launch Proenv utility with administrator privileges:
    • On Windows, select Start > Programs (or All Programs) > Progress > OpenEdge > Proenv.
    • On Linux, run the proenv.sh script located in the $DLC/bin folder
  2. Stop all running OpenEdge components, including any PAS for OpenEdge instances.
    • If you use the OpenEdge database, run the following command to stop it:

      $DLC/bin/dbman -all -stop
    • If you use the AdminServer, stop it. For details, see Stop the AdminServer.

    • If you use OpenEdge Management, perform the appropriate action based on how it is configured on your system:
      • As a process: Stop OpenEdge Management.
      • As a service: Stop OpenEdge Management and unregister it.
        1. Stop OpenEdge Management.
        2. Unregister OpenEdge Management:
          fathom -unregister

        For details on stopping OpenEdge Management, see Stop OpenEdge Management.

  3. Change the value of the JAVA_HOME environment variable in the OpenEdge_installation_dir/properties/java.properties file to your new JDK path.
    Note: Do not include the bin folder in the path.
    • On Windows, specify the JDK path using short file name (8.3) notation and forward slashes (/). For example:
      JAVA_HOME=C:/PROGRA~1/ECLIPS~1/JDK-17~1
      
      
      Note: To retrieve the short file name (8.3) for the JDK directory, perform the following steps:
      1. Open the command prompt.
      2. Run the following command, replacing the path with your JDK installation directory path. For example:
        for %A in ("C:\Program Files\Eclipse Adoptium\jdk-17.0.11-hotspot") do @echo %~sA
        
        
        
      3. Copy the path returned in the output.
      4. In the java.properties file, set JAVA_HOME to the copied path.
    • On Linux, specify the full path to the JDK installation. For example:
      JAVA_HOME=/usr/lib/jvm/jdk-17.0.11
  4. Change the value of the JavaHome property in the openEdge_installation_dir/installd.ini file.
    Note: Do not include the bin folder in the path.
    • On Windows, specify the JDK path using short file name (8.3) notation and forward slashes (/). For example:
      javaHome=C:/PROGRA~1/ECLIPS~1/JDK-17~1
      
      
      Note: To retrieve the short file name (8.3) for the JDK directory, perform the following steps:
      1. Open the command prompt.
      2. Run the following command, replacing the path with your JDK installation directory path. For example:
        for %A in ("C:\Program Files\Eclipse Adoptium\jdk-17.0.11-hotspot") do @echo %~sA
        
        
        
      3. Copy the path returned in the output.
      4. In the installd.ini file, set javaHome to the copied path.
    • On Linux, specify the full path to the JDK installation. For example:
      • javaHome=/usr/lib/jvm/jdk-17.0.11
        
        
  5. If you launch Developer Studio from the shortcut menu, the configuration you applied in the above step is sufficient. However, if you launch Developer Studio by running the eclipse.exe file directly, you must update the JDK path in the -vm argument within the eclipse.ini file located at C:\Progress\OpenEdge\oeide\eclipse\.
    -vm
    <Path_to_JDK>/bin/javaw.exe

    This change lets you automatically open .p, .w, or .cls files in Developer Studio by simply double-clicking them on your computer.

  6. Restart all OpenEdge components that you use. For example:
    • Launch Developer Studio.
    • Start a PAS for OpenEdge instance.
    • Start the generic JMS adapter using the oemessaging script.
    • If you use OpenEdge database instances, then run the following command to start it:
      $DLC/bin/dbman -start
    • If you use AdminServer, start it. For details, see Start the AdminServer.
    • If you use OpenEdge Management, perform the appropriate action based on how it is configured on your system:
      • As a process: Start OpenEdge Management.
      • As a service: Reregister and start OpenEdge Management.
        1. Reregister OpenEdge Management:
          fathom -register
        2. Start OpenEdge Management.

        For details on starting OpenEdge Management, see Start OpenEdge Management.

    If your PAS for OpenEdge instance runs as a Windows service, reregister the service to apply the new JDK path. For details, see Update PASOE Windows service after JDK upgrade.