To support and enable the use of emerging technologies, the following changes were made to the OpenEdge stack:

  • Java Development Kit (JDK)/Java Runtime Environment (JRE)—In keeping with recent changes to Oracle’s licensing of Java, the Java Development Kit (JDK) and Java Runtime Environment (JRE) are no longer included with the OpenEdge installer and are now considered prerequisites for installation. You can:
    • Continue to use the Oracle JDK and JRE
    • Use an open-source JDK and JRE (AdoptOpenJDK is certified)
    • Easily upgrade your version of the JDK and JRE for security upgrades or bug fixes
    • Easily change your path to the JDK and JRE if required

    Depending on the option that you choose to install, you may be prompted to provide the location of your own local copy of the JDK and JRE. If you do not already have the JDK installed, you need to complete this installation before you can complete the installation of this OpenEdge release.

    New to 12.1 is the $DLC/properties/java.properties file where the JAVA_HOME environment variable is set. Any changes made to this file for the JDK and JRE go into effect the next time the Docker image is started.

    For information on JDK and JRE support requirements, see OpenEdge 12 Platform Compatibility Guide.

  • Run PAS for OpenEdge in a Docker container—The recommended approach for providing a JDK to a PAS for OpenEdge Docker container is the Docker sidecar design pattern. The JDK is deployed in a separate (sidecar) Docker container. The JDK container is made available to the PAS for OpenEdge container via a volume share.

    The JDK image in the Docker container must be a version supported by PAS for OpenEdge. The image can be from Docker hub or a custom image provided by you. How you attach the sidecar container to the PAS for OpenEdge container depends on how you created the container (Docker run, Docker Compose, or Minikube). A sample script for each approach is bundled in this release. These scripts can be modified per your needs.

    For more information, see Learn About PAS for OpenEdge in a Docker Container.

  • Unified logging for PAS for OpenEdge Containers—Extending its commitment to cloud computing and scalability, OpenEdge now supports using Fluent Bit with PAS for OpenEdge.

    This release provides:

    • An improved process for customizing the configuration of Fluent Bit
    • The default output of Fluent Bit is to the standard output (which is the best practice for docker containers)

    For more information, see Learn About Unified Logging.

  • File holding the schema will be searched in PROPATH—To improve the usability and efficiency of the Developer Studio, the schema file for Business Entities is now defined in PROPATH.

    The advantages of adding the schema file to PROPATH are:

    • PROPATH maintains the list of all the paths required for a project. If a schema file is defined in any of the paths, Developer Studio automatically searches the path and associates the schema file with the project thus eliminating the need to copy the file to the workspace and specify its relative or absolute path.
    • During catalog generation, the relative path specified in the Business Entity is resolved against PROPATH entries.
    • The same Business Entity can be used across development environments by modifying the PROPATH entries to include the relative path of the entity.
    • If you select a schema file from a directory in your PROPATH, the relative path to the directory is displayed in the Schema File field.
    To make the Progress Developer Studio for OpenEdge easier to use and faster to develop with, Schema File for defined Business Entities are added to the PROPATH.

    For more information, see Select a schema file page.