OpenEdge 12 Platform Compatibility Guide
OpenEdge 12 Platform Compatibility Guide
The OpenEdge® Platform Compatibility Guide reflects the current commercial releases for
Progress Software’s OpenEdge 12 products. This document does NOT address unannounced future
product release plans. The information contained in this document is updated regularly and is
subject to change without notice.
A platform is a collective term referring to a computing environment explicitly validated by
Progress to deploy and use a given OpenEdge release. For this document, a platform includes
operating systems, Java, Microsoft .NET, and, where relevant, other third-party products such as
Apache Tomcat server and Perl. Expect some of these products to be supplied and maintained by
OpenEdge customers, while Progress ships others with OpenEdge. In each case, this guide clarifies
the expectations on the minimum supported versions and recommended patching/upgrade practices
to ensure our ability to help you.
For platform and product information related to earlier Progress OpenEdge releases or to archived
versions of this document, please refer to the Compatibility and Availability information posted on
the Progress Content Portal.
Update Summary:
• Added OpenEdge 12.2.18 and 12.8.9 releases to all Releases and Updates in Section 2.1.
• Updated the version of Perl supplied in OpenEdge 12.2.18 to 5.40.2
• Updated the list of supported Operating Systems:
o RHEL 9.6 (OpenEdge 12.2)
• Added OpenEdge Command Center 2.0 supported OS platforms in Section 2.8
Page 1
Contents
1 OpenEdge Supported Platforms ............................................................................................... 4
1.1 Operating Systems .............................................................................................................. 4
1.1.1 Supporting Microsoft Windows .................................................................................... 5
1.1.2 Supporting 32-bit Microsoft Windows Client Applications ......................................... 5
1.1.3 Supporting Linux ........................................................................................................... 5
1.2 Web Browsers ...................................................................................................................... 7
1.3 Microsoft .NET .................................................................................................................... 7
1.4 Java....................................................................................................................................... 7
1.5 Cloud and Virtualization Support Policy ......................................................................... 9
2 OpenEdge Product Availability by Platform ......................................................................... 10
2.1 OpenEdge Updates, Progress Application Server (PAS) for OpenEdge ..................... 12
2.1.1 Tomcat Update Policy ................................................................................................. 13
2.2 Progress Developer Studio (PDS) for OpenEdge ........................................................... 14
2.2.1 Eclipse Update Policy.................................................................................................. 14
2.3 Progress OpenEdge Adapters .......................................................................................... 14
2.3.1 Progress OpenEdge JMS Adapter ............................................................................... 15
2.3.2 OpenEdge Adapter for Sonic ESB .............................................................................. 15
2.4 Progress OpenEdge Docker Container Images .............................................................. 15
2.5 Progress OpenEdge on AWS ........................................................................................... 15
2.6 Progress OpenEdge DevOps Framework ....................................................................... 15
2.6.1 Gradle .......................................................................................................................... 16
2.7 Progress OpenEdge Pro2 ................................................................................................. 16
2.7.1 Supported Operating System ....................................................................................... 16
2.7.2 Compatibility with OpenEdge Release ....................................................................... 16
2.7.3 Supported Target Databases ........................................................................................ 16
2.8 Progress OpenEdge Command Center ........................................................................... 16
2.9 Apache Kafka with Progress OpenEdge......................................................................... 17
2.10 Progress OpenEdge WebClient .................................................................................. 17
2.11 Apache Ant ................................................................................................................... 17
Page 2
2.12 Perl ................................................................................................................................ 18
3 Feature / Functionality Obsolescence ..................................................................................... 19
3.1 Retired Features and Functionality ................................................................................ 19
3.2 Removed Features and Functionality ............................................................................. 20
4 Platforms and Product Notes .................................................................................................. 23
Page 3
1 OpenEdge Supported Platforms
Page 4
Many Operating Systems have various offerings for a particular release optimized for different
operating environments; for example, Microsoft Windows Server has Standard, Datacenter, and
Essentials editions. Progress generally only certifies the OS vendor’s standard variation and trusts
the OS vendor to guarantee binary compatibility with other editions.
Note: Operating Systems vendors regularly issue critical and security patches and updates
(“Patches”) for their releases. Progress relies on the Operating System vendors guaranteeing
binary compatibility between their patches and kernel versions and therefore does not explicitly
certify these patches.
Legacy OpenEdge client applications compiled to run on 32-bit Windows often depend on 32-bit
ActiveX (or OCX) controls not supported on modern 64-bit Windows. To help our customers
maintain these 32-bit applications,
1. OpenEdge’s latest development tools generate platform-independent output to use on both
64-bit and 32-bit Windows.
2. The development tool supports 32-bit client-side AVM to validate the changes made by
running updated or modified applications on their native 32-bit platform.
For additional information, please refer to the Knowledge Base Article “HOW TO COMPILE
AND RUN AN OPENEDGE APPLICATION WITH 32-BIT OCX USING OPENEDGE 12?”
Note: If your application uses the 32-bit OpenEdge ODBC driver, you should compile the
corresponding SQL application in 32-bit mode.
• OpenEdge is supported on the Linux Operating System for the following processor
architectures:
o Intel x86
Page 5
o AMD64
o Intel EM64T
• Support of the Network File System protocol version 3 (NFSv3) under the Linux Intel x86
platform for Progress OpenEdge products, mainly, the support of RDBMS files (physical and
recovery) on an NFS partition, requires updates and features found within the 2.4.21 Linux
Kernel and OpenEdge Updates (Service Packs in the past). Network File System (NFS)
protocol versions NFSv2 and NFSv4 under Linux have not been certified and are therefore
unsupported.
• There are many enterprise-grade Linux distributions based on Red Hat Enterprise Linux that
are not listed as supported Operating Systems in this document. With CentOS 8.x reaching end-
of-life (December 2021), our customers are exploring Linux options for deploying and
operating OpenEdge, including Operating Systems not explicitly listed in this document.
While Progress cannot test and validate all available Operating Systems, we understand our
customers' preference for various, often no-cost, offerings based on Red Hat Enterprise Linux.
Therefore, customers may choose to operate OpenEdge on a Linux Operating System not listed
in this document based on a supported version of the Red Hat Enterprise Linux, at their
discretion. However, in case of any issue, the same should be reproducible on the
corresponding Red Hat Enterprise Linux version to get support in line with the customer's
Progress support agreement to ensure that the changes/customization of the Operating System
vendor isn't causing the issue.
Note: (1) Read more on OpenEdge support on CentOS at,
https://knowledgebase.progress.com/articles/Knowledge/P114682
(2) This policy also applies to Linux distributions based on SUSE Enterprise Linux.
• Red Hat Enterprise Linux offers minor releases for each major (8, 9, …) release. From a Red
Hat support perspective:
o The odd-numbered minor releases, e.g., 9.1, 9.3, …, are supported by Red Hat until
the next minor release is published.
o The even-numbered minor releases, e.g., 9.0, 9.2, 9.4…, are supported by Red Hat for
a period typically between 6-12 months after the subsequent odd-numbered minor
release is published. In addition, the even-numbered minor releases are typically
designated as Extended Update Support (EUS), which provides 2 or more years of
support for a fee.
Progress formally certifies OpenEdge with the even-numbered releases and does not
explicitly certify the odd-numbered releases given their short life cycle. Should you choose
to use OpenEdge with an odd-numbered release and encounter an issue, you may open a
support case with our Technical Support. Progress will make a reasonable effort to
investigate the issue and help find a solution or a workaround. In case a solution or a
workaround is identified, we will share it proactively with our customers.
Page 6
1.2 Web Browsers
OpenEdge does not certify any specific web browser with any OpenEdge product release. Except
as noted below, if a problem arises using a particular web browser, please contact Progress Support
for assistance.
Note: As of June 15, 2022, Microsoft Internet Explorer is retired, and therefore we don’t
recommend using it.
.NET 8 has been certified for use with OpenEdge 12.8, starting with OpenEdge 12.8.4, on
Microsoft Windows.
Progress recommends you monitor Microsoft’s critical updates for your supported version of
Microsoft Windows and apply them as needed to stay current. As always, before updating your
production environment, validate that the change will not cause issues.
Note: Starting with OpenEdge 12.3, .NET Framework is not distributed with OpenEdge.
1.4 Java
Starting with OpenEdge release 12.1, Java Development Kit (JDK) is no longer included with
the product. Instead, the supported JDK version must be available as a pre-requisite to the
installation of OpenEdge.
Table 2. JDK versions certified for OpenEdge 12.1
Page 7
Table 3. JDK versions certified for OpenEdge 12.2, 12.3, 12.4 and 12.5
Oracle Java SE
OS Platform Eclipse Temurin (Adoptium) OpenJDK
Development Kit
Microsoft
jdk-17.0.3+7 (x64) (Hotspot) 17.0.4
Windows
Linux jdk-17.0.3+7 (x64) for Linux (Hotspot) 17.0.4
The certified Java versions receive regular security patches from their vendors. Progress
recommends customers to,
a. Monitor Java vendor’s updates for the latest security patches.
b. If you decide to apply the latest security patches, test in a non-production critical
environment first.
Note: OpenEdge is supported only on the major JDK version specified in this section. For example,
OpenEdge 12.2 is supported on JDK 11.0.x, where x can be 4 (i.e., 11.0.4) or later.
For your convenience, we list the sources where you can find security fixes and updates for the
below recommended Java distributions,
• AdoptOpenJDK OpenJDK - https://adoptopenjdk.net/index.html
Note: AdoptOpenJDK OpenJDK is rebranded to Adoptium OpenJDK with the new releases
available at https://adoptium.net/releases.html
• Oracle JDK - https://www.oracle.com/java/technologies/javase-downloads.html
• IBM SDK, Java Technology Edition - https://www.ibm.com/support/pages/java-sdk-
downloads-version-110
If you are using OpenEdge on Docker containers, refer to the relevant supplied documentation for
recommended JDK.
Page 8
1.5 Cloud and Virtualization Support Policy
Modern computing infrastructure technology continues to evolve towards virtualization and cloud
to support growing scalability and performance demands. As a result, our customers are facing
new choices and considerations when it comes to deployment and operating OpenEdge, including:
• Server Virtualization including capabilities like VMware® VMotion™
• Virtual Desktop Infrastructures (VDI), for example, from Citrix
• Containerization, for instance, from Docker
• Cloud Computing, including AWS, Azure, and others
Unless explicitly stated, Progress supports OpenEdge on Operating Systems listed in this
document, irrespective of any given cloud or virtualization technology. In case of any issue, the
same problem should be reproducible with a standard OS installation to get support in line with
the customer’s support agreement, i.e., you must ensure that changes/customization of the cloud
virtualization platform isn’t causing the issue.
Page 9
2 OpenEdge Product Availability by Platform
Note, this also covers File Systems. Refer to Note A in Platforms and Product Notes.
Table 5. OpenEdge Product Availability by Platform
Oracle Solaris
Microsoft
IBM AIX
AMD64
SPARC
Notes
Category
Product
OpenEdge Studio ✓
OpenEdge
Page 10
Linux x64 Intel/
Windows Intel
Oracle Solaris
Microsoft
IBM AIX
AMD64
SPARC
Notes
Category
Product
Page 11
Linux x64 Intel/
Windows Intel
Oracle Solaris
Microsoft
IBM AIX
AMD64
SPARC
Notes
Category
Product
Page 12
OpenEdge Version Release Date (GA) Tomcat Version
12.3.0 Oct 22, 2020 9.0.37
12.4.0 July 28, 2021 9.0.45
12.4.1 Oct 30, 2021 9.0.45
12.5.0 Feb 22, 2022 9.0.55
12.5.1 May 24, 2022 9.0.55
12.5.2 July 29, 2022 9.0.55
12.6.0 Sep 29, 2022 9.0.64
12.7.0 May 2, 2023 9.0.73
12.8.0 Jan 16, 2024 10.1.15
12.8.1 Feb 22, 2024 10.1.15
12.8.2 Apr 22, 2024 10.1.19
12.8.3 Jun 12, 2024 10.1.19
12.8.4 Sep 4, 2024 10.1.19
12.8.5 Jan 27, 2025 10.1.19
12.8.6 Feb 10, 2025 10.1.19
12.8.7 May 9, 2025 10.1.39
12.8.8 Jun 23, 2025 10.1.41
12.8.9 Aug 15, 2025 10.1.41
Progress OpenEdge embeds a version of the Apache Tomcat Web server in the Progress
Application Server (PAS) for OpenEdge product and recognizes customer requirements to keep up
to date with Apache Tomcat security patches. The best way to get the latest security fixes for
Tomcat is to upgrade to the newest version of PAS for OpenEdge.
Suppose you cannot upgrade to the latest version. In that case, you can try to replace the core
Apache Tomcat server libraries that you may update from an official Apache Tomcat distribution
(e.g., http://tomcat.apache.org/migration.html) of the same release version. The patch is applied
must be a higher version. The core Tomcat server libraries contain most of the security patches.
Note: An Apache Tomcat distribution also contains configurable text files that cannot be updated
without invalidating the PAS for OpenEdge security configuration, ABL language support, and its
integration with the overall OpenEdge product set. Please review the “Tomcat configuration file
differences” section in the correct version of the link above. Please consult with Progress Technical
Support before altering these text files.
The possible list of files that may be safe to update from an official Apache Tomcat distribution
includes:
$DLC/servers/pasoe/bin/bootstrap.jar
$DLC/servers/pasoe/lib/*.jar
$DLC/servers/pasoe/bin/catalina.{sh|bat}
Page 13
$DLC/servers/pasoe/bin/daemon.{sh|bat}
$DLC/servers/pasoe/bin/setclasspath.{sh|bat}
Patching the PAS for OpenEdge SSL/TLS capability may require updating the JDK version. Please
refer to the Java section for information on updating JDK versions.
Please note that Progress cannot formally certify each security patch released by Apache. You can
report the issues that arise from installing these patches to Progress Technical Support for further
assistance, so long as they are part of the same major Tomcat release version. But realize Progress
may not resolve the issue without requiring you to upgrade to the latest version of OpenEdge.
Progress ensures the version of Eclipse shipped with OpenEdge is fully supported. We advise you
against changing the Eclipse version as it may render the product inoperable and/or lead to
difficulty troubleshooting issues. If, despite this advice, you change the Eclipse version and then
contact Progress Technical Support with problems caused by this change, we may ask you to
reproduce the reported issue with the supported Eclipse version.
Page 14
2.3.1 Progress OpenEdge JMS Adapter
Progress OpenEdge JMS Adapter supports any JMS1.1 compliant vendor implementation.
Progress validated this with Aurea Messenger MQ (formerly known as Aurea SonicMQ),
ActiveMQ Artemis, and WebSphere MQ.
Table 8. Compatibility between OpenEdge Adapter for Sonic ESB and Aurea Messenger ESB (formerly known as Aurea Sonic
ESB). Other vendors are not supported.
Page 15
• progress.openedge.abl-base
The OpenEdge DevOps Framework Gradle plugins are released independent of the OpenEdge
platform release.
To learn more about these plugins, refer to Learn About the OpenEdge DevOps Framework
2.6.1 Gradle
The latest OpenEdge DevOps Framework version 2.3.0 is certified and supported on Gradle 8.
Note: Progress OpenEdge 12.2 and later comes with a shell script ‘progradle’ that downloads and
installs the compatible Gradle version when executed for the first time and sets up the JDK required
by Gradle.
Progress OpenEdge Pro2 is supported on all the Operating Systems mentioned in Table 1.
Supported Operating Systems.
The compatibility matrix between the active Pro2 release and OpenEdge releases is available at
OpenEdge Life Cycle.
Progress OpenEdge Pro2 supports replication of an OpenEdge database to Microsoft SQL, Oracle,
and other OpenEdge Databases.
Page 16
OECC Server supports Microsoft Windows Server and Linux. OECC Agent must be deployed on
the same operating systems as OpenEdge versions 12.8 and 12.2. For full OS compatibility details,
refer to Table 1 in the document. Please note, Solaris platform is not supported for OECC Agent
deployment.
OECC 2.0 Server requires MongoDB version 7.0.20 or later patch for it’s configuration
management. Refer to the documentation for detailed steps before installing the OECC Server.
To learn more about OECC, visit Learn about OpenEdge Command Center
Page 17
OpenEdge 12.2 and later releases ships with and is certified to work with Apache Ant 1.10.6.
Progress does not recommend replacing the shipped version of Ant with another version.
2.12 Perl
Some of the Progress OpenEdge tools (e.g., PAS for OpenEdge Migration Wizard) use the Perl
programming language.
Perl is compiled directly from source code by Progress:
Progress does not recommend replacing the shipped version of Perl with another version.
Note: Except for Linux and AIX-based distributions, a 32-bit version of Perl is shipped with
OpenEdge 64-bit Product. Before using Perl (or utilities using Perl), install all dependent libraries
(32-bit) of Perl as specified in the corresponding documentation.
Page 18
3 Feature / Functionality Obsolescence
Progress OpenEdge Life Cycle Policy Guide defines the terms for De-Support and Deprecation.
Page 19
OpenEdge is not supported on IBM AIX for
IBM AIX None OpenEdge 12.6
OpenEdge 12.6 and later releases
Page 20
Deprecation Information
Removed Feature Replacement Announced
or Functionality Feature OpenEdge Notes
Version
V9 Debugger V12 Debugger OpenEdge 12.0
Page 21
Deprecation Information
Removed Feature Replacement Announced
or Functionality Feature OpenEdge Notes
Version
Support for the smaller database block sizes, 1024
and 2048 kilobytes, will be removed in OpenEdge
12.7.
Page 22
4 Platforms and Product Notes
A. File System Support (NFS, iSCSI, CIFS, ZFS, and Encrypted file systems): No matter which
operating system you prefer, there are numerous choices for file systems available, each with
different performance characteristics and limitations.
In general, Progress Software does not support or certify specific file systems for use as
OpenEdge RDBMS storage. File systems are part of an operating system, just as device drivers
are, and are supported by their respective operating system suppliers. If there are bugs or
defects, Progress cannot correct them - the operating system supplier is responsible for that.
Furthermore, certification testing of any operating system using any file system is done from
correct functionality and does not consider performance metrics. Different file systems may
have performance-related side effects that are a by-product of how the file system operates.
Progress advises users to carry out extensive acceptance testing and seek vendor guidance if
performance issues arise. Progress Software cannot help customers configure any file system
to manage performance or other characteristics.
The OpenEdge RDBMS works well with most file systems. As long as the operating system’s
file access API implementation is correct, the file system’s options configuration is proper, and
the supplier’s patches are up to date. Only rare instances have Progress Software certified file
systems or other storage products as OpenEdge RDBMS storage. These were done on an
exception basis, usually in cooperation with the respective vendors, and include Network File
System (NFS), which is supported starting with NFS Version 3; NetApp Filers; EMC SRDF;
and iSCSI, which is supported beginning with the OpenEdge 10.1A release.
For leveraging UNIX/Linux/Windows Encrypted File Systems, OpenEdge products have no
restrictions provided the encryption technology is truly transparent to the Operating System.
There are no plans to certify Encrypted File System Technology formally. The EFS technology
transparently allows files to be stored encrypted on NTFS file systems.
XFS is the default file system for RHEL 8.0 64-bit/CentOS 8.0 64-bit, and OpenEdge
certifications have been carried out using XFS.
B. Report Builder Engine is not supported with tables with Table Partitioning, or Multi-Tenancy
enabled against them. Also:
• The Report Builder Engine will only work with tables in a partitioned database that is not
partitioned. The Report Builder Engine will return an error if the report in question attempts to
access a table in a partitioned database that has been partitioned.
• The Report Builder Engine will only work with tables in a multi-tenant database that is shared
tables. The Report Builder Engine will return an error if the report in question attempts to
access a table in a database that has been defined as multi-tenant.
Page 23
C. Oracle RDBMS Support: Indicates platforms where the Oracle RDBMS product may not be
commercially available, but the OpenEdge DataServer can be installed to provide client/server
access to remote Oracle RDBMS instances. For operating systems that support 32-bit and 64-
bit applications, Oracle 12 and later are only available as 64-bit products. The 32-bit based
OpenEdge DataServer for Oracle can access a 64-bit Oracle Database instance via 32-bit
Oracle Client software.
The table below provides information on the OpenEdge certification of Oracle for the
OpenEdge DataServer for Oracle. The Oracle client version given in the table was used for
certification testing. However, other client versions of the same Oracle release are also
supported. The same version (listed in the “Oracle Certified Version” column) of Oracle Server
and OCI Client Libraries were used for certification.
Table 14. OpenEdge certification of Oracle for the OpenEdge DataServer for Oracle
Oracle Oracle Microsoft Windows Oracle
Linux x86
Database Certified Solaris** IBM AIX
on Intel
Version Version 32-bit 64-bit (SPARC)
19C 19.3.0.0 12.2 12.2, 12.8 12.2, 12.8 12.2 12.2
18C 18.3.0.0 12.1 12.1 12.1 12.1 12.1
12c R2* 12.2.0.1 12.0 12.0 12.0 12.0 12.0
12c R1* 12.1.0.1 12.0 12.0 12.0 12.0 12.0
* In addition to the current support for Oracle 19c, the OpenEdge DataServer for Oracle is
certified for Oracle18c with multi-tenant enabled databases.
** Oracle Solaris was discontinued starting with OpenEdge 12.5.
D. While migrating OpenEdge sequences to Microsoft Azure SQL Database, the native sequences
should be used instead of the revised sequences. The revised sequences do not work with
Microsoft Azure SQL Database.
Page 24