®

OpenEdge 12 Platform & Product Availability Guide

Current version: May 03, 2023

Previous version: March 14, 2023

The OpenEdge® Platform & Product Availability 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, please refer
to the Availability and Compatibility information posted on Progress Information Hub at
https://docs.progress.com/category/openedge

Update Summary:

• Updated the list of supported Operating System.

o Removed certified sub-versions for Microsoft Windows Operating Systems as they
are not relevant for our support for the major version.
o Listed the Operating Systems in a consistent order, i.e., from the latest to the oldest
release.
• Updated the note on the recommendation on using Microsoft Internet Explorer.

© 2023 Progress Software Corporation. All Rights Reserved. Page 1

Contents
1 OpenEdge Supported Platforms ............................................................................................... 4
1.1 Operating Systems .............................................................................................................. 4
1.1.1 Supporting Microsoft Windows Client Operating Systems (Effective June 2019) ...... 5
1.1.2 Supporting 32-bit Microsoft Windows Client Applications ......................................... 6
1.1.3 Supporting Linux ........................................................................................................... 6
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 Progress Application Server (PAS) for OpenEdge ........................................................ 12
2.1.1 Tomcat Update Policy ................................................................................................. 12
2.2 Progress Developer Studio (PDS) for OpenEdge ........................................................... 13
2.2.1 Eclipse Update Policy.................................................................................................. 13
2.3 Progress OpenEdge Adapters .......................................................................................... 13
2.3.1 Progress OpenEdge JMS Adapter ............................................................................... 13
2.3.2 OpenEdge Adapter for Sonic ESB .............................................................................. 13
2.4 Progress OpenEdge Docker Container Images .............................................................. 14
2.5 Progress OpenEdge on AWS ........................................................................................... 14
2.6 Progress OpenEdge DevOps Framework ....................................................................... 14
2.6.1 Gradle .......................................................................................................................... 14
2.7 Progress OpenEdge Pro2.................................................................................................. 14
2.7.1 Supported Operating System ....................................................................................... 15
2.7.2 Compatibility with OpenEdge Release ....................................................................... 15
2.8 Progress OpenEdge Command Center ........................................................................... 15
2.9 Apache Kakfa with Progress OpenEdge ......................................................................... 15
2.10 Progress OpenEdge WebClient .................................................................................. 16
2.11 Apache Ant ................................................................................................................... 16
2.12 Perl ................................................................................................................................ 16
3 Feature / Functionality Obsolescence ..................................................................................... 17
3.1 De-supported Features and Functionality ...................................................................... 17

© 2023 Progress Software Corporation. All Rights Reserved. Page 2

 3.2 Deprecated Features and Functionality .......................................................................... 17
4 Platforms and Product Notes .................................................................................................. 21

© 2023 Progress Software Corporation. All Rights Reserved. Page 3

1 OpenEdge Supported Platforms

1.1 Operating Systems

Table 1. Supported Operating Systems
Supported Processor
Certified Operating Systems OpenEdge Version
Architecture
Microsoft Windows Server 2022 12.2.7+ x86-64
Microsoft Windows Server 2019 12.0+ x86-64
Microsoft Windows Server 2016 12.0+ x86-64
Microsoft Windows 11 12.2.10+ x86-64
Microsoft Windows 10 12.0+ x86-64
Microsoft Windows 8.1 12.0 x86-64
Ubuntu 20.04 LTS 12.2+ x86-64
Ubuntu 18.04 LTS 12.0+ x86-64
Oracle Linux 8.2 12.2+ x86-64
Oracle Linux 8.1 12.2+ x86-64
Oracle Linux 7.9 12.2+ x86-64
Oracle Linux 7.6 12.0+ x86-64
Red Hat Enterprise Linux 9 12.2.10+ x86-64
Red Hat Enterprise Linux 8.6 12.2.10+ x86-64
Red Hat Enterprise Linux 8.4 12.2+ x86-64
Red Hat Enterprise Linux 8.2 12.2+ x86-64
Red Hat Enterprise Linux 8 12.0+ x86-64
Red Hat Enterprise Linux 7.9 12.2+ x86-64
Red Hat Enterprise Linux 7.6 12.0+ x86-64
CentOS 8.1 12.2+ x86-64
CentOS 7.6 12.0+ x86-64
CentOS 7 (2009) 12.2+ x86-64
SUSE Enterprise Server 15 SP2 12.2+ x86-64
SUSE Enterprise Server 15 12.0+ x86-64
SUSE Enterprise Server 12 SP5 12.0+ x86-64
SUSE Enterprise Server 12 12.2+ x86-64
Oracle Solaris 11.4 (SPARC) 12.2.x SPARC
Oracle Solaris 10 (SPARC) 12.1 SPARC
IBM AIX 7.2 TL5 12.2.x, 12.5 POWER
IBM AIX 7.2 TL3 12.0-12.2.x, 12.5 POWER
Amazon Linux 2 12.2.x x86-64
All supported Operating Systems are 64-bit. For information on supporting 32-bit Windows client
application refer to section 1.1.2.
The “x86-64” architecture is also known as x64 or x86_64 and includes both AMD64 and Intel64.
Many Operating Systems have various offerings for a particular release optimized for different
operating environments; for example, Microsoft Windows Server has Standard, Datacenter, and

© 2023 Progress Software Corporation. All Rights Reserved. Page 4

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 to guarantee binary
compatibility between their patches and kernel versions and therefore does not explicitly certify
these patches.

1.1.1 Supporting Microsoft Windows Client Operating Systems (Effective June 2019)

Microsoft offers two flavors of its Windows Operating System (OS):

a) Client OS (e.g., Windows 10) designed to run on personal computers, and
b) Server OS (e.g., Windows Server 2019) optimized to handle mission-critical, heavy
computing loads on production-grade servers.
This section describes how Progress supports OpenEdge-based applications deployed on Windows
Client Operating Systems on different support cycles.
For its Client OS products, Microsoft offers a choice of lifecycle support options:

A. Windows Client OS Semi-Annual Channel (SAC)

The Semi-Annual Channel (SAC), introduced with Windows 10, targets users who wish to stay
current on the latest features. In SAC, the cumulative updates are pushed out (often
automatically) twice per year. For example, Windows 10 1903 release was made available on
May 21, 2019.
What this means to you:
• Progress will not explicitly certify OpenEdge on new Windows Client OS SAC updates.
• Should you encounter a problem using OpenEdge after the latest Microsoft Windows
SAC update is applied, 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, including, if necessary, working with Microsoft. In case a solution or
a workaround is identified, we will share it proactively with our customers.
• If your deployment is mission-critical, to minimize the risk of incompatibility between
the latest OS updates and your OpenEdge version, you should consider using Windows
LTSC instead of SAC.

B. Windows Client OS Long Term Servicing Channel (LTSC)

The Enterprise Long Term Servicing Channel (LTSC) edition is more stable of the two and is
appropriate for mission-critical use, with releases made available approximately once every
three years.
What this means to you:

© 2023 Progress Software Corporation. All Rights Reserved. Page 5

 • Progress will make every effort to certify all then active and mature OpenEdge releases
within 60 days of Microsoft making Windows LTSC updates publicly available. Upon
completing this certification, Progress will update this document (OpenEdge PAG).
• When you open a support case with our Technical Support, you may have to reproduce
the reported issue on the certified Windows Client OS LTSC update. In some cases,
updating to the latest certified LTSC version may be the only remedy available to you.

1.1.2 Supporting 32-bit Microsoft Windows Client Applications

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 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.

1.1.3 Supporting Linux

• OpenEdge is supported on the Linux Operating System for the following processor
architectures:
o Intel x86
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

© 2023 Progress Software Corporation. All Rights Reserved. Page 6

 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 is also applicable for the Linux distributions based on SUSE Enterprise Linux.

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.

1.3 Microsoft .NET

OpenEdge 12.2 and later releases are certified to work with Microsoft .NET v4.8.
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

AdoptOpenJDK Oracle Java SE IBM SDK, Java

OS Platform
OpenJDK (Hotspot) Development Kit Technology Edition
Microsoft Windows jdk1.8u222-b10 1.8.0_221-b11 -
Linux jdk1.8u222-b10 1.8.0_221-b11 -
Oracle Solaris jdk1.8u222-b10 1.8.0_221-b11 -
IBM AIX - - 8.0.5.20

© 2023 Progress Software Corporation. All Rights Reserved. Page 7

Table 3. JDK versions certified for OpenEdge 12.2, 12.3, 12.4 and 12.5

Oracle Java SE IBM SDK, Java

OS Platform AdoptOpenJDK OpenJDK
Development Kit Technology Edition
Microsoft -
jdk-11.0.4+11 (x64) (Hotspot) 11.0.4+10
Windows
jdk-11.0.4+11 (x64) for Linux -
Linux 11.0.4+10
(Hotspot)
Oracle Solaris - 11.0.4+10 -
jdk-11.0.6+10_openj9-0.18.1 11.0.12.0 (OpenJ9)
IBM AIX -
(OpenJ9)

Table 4. JDK versions certified for OpenEdge 12.6 and later

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.

© 2023 Progress Software Corporation. All Rights Reserved. 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 on 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.

© 2023 Progress Software Corporation. All Rights Reserved. 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

Linux x64 Intel

Windows Intel

Oracle Solaris
Microsoft

IBM AIX
SPARC

Notes
Category
Product

Certification and key

Product Name
functionality details
32 64 64 64 64
Bit Bit Bit Bit Bit
4GL Development System ✓ ✓ ✓ ✓ ✓
Development

✓
OpenEdge

OpenEdge Studio
Progress Developer Studio for
✓
OpenEdge
OpenEdge Ultra Controls for
✓
.NET
WebClient™ ✓ ✓
Client Networking ✓ ✓ ✓ ✓ ✓
Query/Results ✓ ✓ ✓ ✓ ✓
OpenEdge RDBMS 4GL & SQL
OpenEdge Personal RDBMS RDBMS support
✓ ✓ ✓ ✓
OpenEdge Workgroup RDBMS Support for SQL Stored Procedures ✓ ✓ ✓ ✓
OpenEdge Enterprise RDBMS Native JDBC Drivers (embedded)
Type-4 v4.0 and Type-5 v5.1
✓ ✓ ✓ ✓
OpenEdge Advanced Enterprise
Edition RDBMS Native ODBC Drivers (embedded)
v5.3 and v7.1
✓ ✓ ✓ ✓
Deployment
OpenEdge

Transparent Data Encryption Support for Hardware Security Module ✓ ✓ ✓ ✓

Multi-tenant Tables ✓ ✓ ✓ ✓ B
Table Partitioning ✓ ✓ ✓ ✓ B
OpenEdge 12.2 and higher – Oracle
19c (19.3.0.0)
✓ ✓ ✓ ✓ ✓ C
OpenEdge DataServer for OpenEdge 12.1 and higher - Oracle
18c (18.3.0.0) ✓ ✓ ✓ ✓ ✓ C
Oracle
Oracle 12c R2 (12.2.0.1) ✓ ✓ ✓ ✓ ✓ C
Oracle 12c R1 (12.1.0.2) ✓ ✓ ✓ ✓ ✓ C
OpenEdge 12.2 and higher - Azure
SQL Database (ODBC18 driver (for
OpenEdge DataServer for OpenEdge 12.2.11+), ODBC17 driver ✓ ✓ D
Microsoft SQL Server for SQL Server, SQL Native Client 11,
Data Direct ODBC driver)

© 2023 Progress Software Corporation. All Rights Reserved. Page 10

 Linux x64 Intel
Windows Intel

Oracle Solaris
Microsoft

IBM AIX
SPARC

Notes
Category
Product

Certification and key

Product Name
functionality details
32 64 64 64 64
Bit Bit Bit Bit Bit
OpenEdge 12.1 and higher - MS SQL
Server 2019
(ODBC18 driver (for OpenEdge
12.2.11+), ODBC17 driver for SQL
server, ✓ ✓
SQL Native Client 11,
Data Direct ODBC driver,
SQL server)
MS SQL Server 2017
(ODBC18 driver (for OpenEdge
12.2.11+), ODBC17 driver for SQL
server, ✓ ✓
SQL Native Client 11,
Data Direct ODBC driver,
SQL server)
MS SQL Server 2016
(ODBC18 driver (for OpenEdge
12.2.11+), ODBC17 driver for SQL
server, ✓ ✓
SQL Native Client 11,
Data Direct ODBC driver,
SQL server)
MS SQL Server 2014
(ODBC18 driver (for OpenEdge
12.2.11+), ODBC17 driver for SQL
server, ✓ ✓
SQL Native Client 11,
Data Direct ODBC driver,
SQL server)
MS SQL Server 2012
(SQL Native Client 11,
Data Direct ODBC driver,
✓ ✓
SQL server)
Progress Application Production and Development ✓ ✓ ✓ ✓
Server for OpenEdge
OpenEdge Explorer ✓ ✓ ✓ ✓
Standard Edition
Console & Trending Database
✓ ✓ ✓ ✓
OpenEdge Management Remote OpenEdge and operating
system monitoring
✓ ✓ ✓ ✓
SNMP Adapter ✓ ✓ ✓ ✓
OpenEdge Replication ✓ ✓ ✓ ✓
OpenEdge Replication
OpenEdge Replication Plus ✓ ✓ ✓ ✓

© 2023 Progress Software Corporation. All Rights Reserved. Page 11

2.1 Progress Application Server (PAS) for OpenEdge
The table below lists the Apache Tomcat versions supplied with PAS for OpenEdge.
Table 6. Apache Tomcat versions
OpenEdge Release Tomcat Version
12.0 , 12.1 9.0
12.2.0 - 12.2.5 9.0.30
12.2.6 – 12.2.7 9.0.45
12.2.8-12.2.10 9.0.59
12.2.11+ 9.0.64
12.3 9.0.37
12.4 9.0.45
12.5 9.0.55
12.6 9.0.64
12.7 9.0.73

2.1.1 Tomcat Update Policy

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}
$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.

© 2023 Progress Software Corporation. All Rights Reserved. Page 12

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.

2.2 Progress Developer Studio (PDS) for OpenEdge

The table below summarizes component versions within PDS for OpenEdge.
Table 7. Eclipse IDE Versions

OpenEdge Release Eclipse Version

12.0 and 12.1 4.9
12.2 - 12.5 4.13
12.6 - 12.7 4.23

2.2.1 Eclipse Update Policy

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 difficult
troubleshoot 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.

2.3 Progress OpenEdge Adapters

Starting with OpenEdge release 12.2, both JMS Adapter and Sonic ESB Adapter have separate
installers.
Unlike other OpenEdge products that require JDK 11 or JDK17, these adapters require JDK 8 as a
pre-requisite. Table 2. JDK versions certified for OpenEdge 12.1 lists the certified versions for
JDK 8.

2.3.1 Progress OpenEdge JMS Adapter

Progress OpenEdge JMS Adapter supports any JMS1.1 or higher compliant vendor
implementation. Progress validated this with Aurea Messenger MQ (formerly known as Aurea
SonicMQ), ArtemisMQ, and WebsphereMQ.

2.3.2 OpenEdge Adapter for Sonic ESB

Table 8. Compatibility between OpenEdge Adapter for Sonic ESB and Aurea Messenger ESB (formerly known as Aurea Sonic
ESB). Other vendors are not supported.

OpenEdge Adapter for Sonic ESB Aurea Messenger ESB

12.1 and higher 2018 R2 and higher

© 2023 Progress Software Corporation. All Rights Reserved. Page 13

2.4 Progress OpenEdge Docker Container Images
Progress offers Progress Application Server for OpenEdge and Progress OpenEdge RDBMS as
container images available at Docker hub.
Table 9. OpenEdge Docker Container Images

OpenEdge Container Image OpenEdge Releases

12.0.0, 12.1.0, 12.2, 12.3, 12.4,
Progress Application Server for OpenEdge
12.5, 12.6, 12.7
Progress OpenEdge RDBMS Enterprise/Advanced 12.1.0, 12.2, 12.3, 12.4, 12.5,
Enterprise 12.6, 12.7
Note: The container images are available at the Progress OpenEdge ESD for all supported releases.

2.5 Progress OpenEdge on AWS

For OpenEdge customers looking to deploy their on-premises applications on a highly available
three-tier Progress OpenEdge stack on the AWS Cloud, Progress partnered with Amazon Web
Services to develop AWS Quick Starts. To learn more, visit Progress OpenEdge on AWS.
AWS Quick Starts uses the Progress Application Server for OpenEdge and Progress OpenEdge
RDBMS Amazon Machine Images (AMIs) to support OpenEdge applications’ deployments on
AWS Cloud. The images are available in the AWS marketplace.

2.6 Progress OpenEdge DevOps Framework

To facilitate the continuous integration for OpenEdge applications, the OpenEdge DevOps
Framework offers the following Gradle plugins,
• progress.openedge.abl
• 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.x is certified and supported on Gradle 7.3.3.
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.

2.7 Progress OpenEdge Pro2

Progress OpenEdge Pro2 is released independently of the OpenEdge Platform release, and its
lifecycle is covered separately under Progress OpenEdge Pro2 Life Cycle Policy Guide.

© 2023 Progress Software Corporation. All Rights Reserved. Page 14

2.7.1 Supported Operating System

Progress OpenEdge Pro2 is supported on all the Operating Systems mentioned in Table 1.
Supported Operating Systems.

2.7.2 Compatibility with OpenEdge Release

The compatibility matrix between the active Pro2 release and OpenEdge releases is available at
OpenEdge Life Cycle.

2.8 Progress OpenEdge Command Center

Progress OpenEdge Command Center (OECC) is a cloud-ready OpenEdge management console
for managing multiple Progress AppServer for OpenEdge (PASOE) instances.
The table below list the compatibility of OECC with OpenEdge releases,
Table 10. OpenEdge Command Center Releases
OpenEdge Command Center
OpenEdge Releases
Release
12.2.7 and higher, 12.5, 12.6,
1.2
12.7
To learn more about OECC, visit Learn about OpenEdge Command Center

2.9 Apache Kakfa with Progress OpenEdge

Apache Kafka is a fast, highly scalable, and fault-tolerant distributed data store that centralizes
communication between producers and consumers of streaming data in real-time.
Starting with OpenEdge 12.5, Progress OpenEdge provides an API for using Apache Kafka. The
Apache Kafa support is only available on the 64-bit Linux and Windows Operating Systems (all
supported versions).
The Apache Kafka C/C++ library, librdkafka is a prerequisite for Apache Kafka that must be
separately downloaded and installed. The installation steps for Windows and Linux are listed
at Install the Apache Kafka C/C++ library on Windows and Install the Apache Kafka C/C++ library
on Linux, respectively.
To learn more, visit Use Apache Kafka with Progress OpenEdge.

© 2023 Progress Software Corporation. All Rights Reserved. Page 15

2.10 Progress OpenEdge WebClient
The OpenEdge WebClient enables you to build and distribute updates for web-based OpenEdge
applications. It requires the following 32-bit and 64-bit Visual C++ redistributable packages to be
installed for the 32-bit and 64-bit OpenEdge WebClient installations, respectively.
Table 11. Required VC++ redistributable packages

OpenEdge Release VC++ Redistributable Packages

12.2.x Visual Studio 2015, 2017, 2019, and 2022
12.7 Visual Studio 2015, 2017, 2019, and 2022
Note: Before installing the WebClient with a non-admin user, the above listed packages should be
installed in the system. To know more, visit Requirements for using WebClient

2.11 Apache Ant

The Apache Ant build tool is used by Progress OpenEdge, by the installer for tailoring, by PDS
for OpenEdge, and is required with PCT.
OpenEdge 12.2 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 Perl
programming language.
OpenEdge 12.2 ships with Perl version 5.26.1 compiled by Progress directly from the source code.
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.

© 2023 Progress Software Corporation. All Rights Reserved. Page 16

3 Feature / Functionality Obsolescence
Progress OpenEdge Life Cycle Policy Guide defines the terms for De-Support and Deprecation.

3.1 De-supported Features and Functionality

The following table contains the current list of de-supported features and operating systems for
OpenEdge 12. Timeframe details are published to help partners and customers with their planning.
We recommend substituting obsolete functionality with appropriate equivalents as indicated in the
following table.
Table 12. De-supported Features and Functionality
De-Support Information
De-Supported
Replacement De-Support
Feature or
Feature Scheduled Notes
Functionality
For
Microsoft Windows Server 2012 R2 reached its
mainstream end of life in September 2018 and is
Windows Server not supported for OpenEdge 12.0 and later.
None OpenEdge 12.0
2012 R2 An earlier version of the Product Availability
Guide published on May 19, 2020, incorrectly
listed Windows Server 2012 R2 as supported.
Microsoft Windows 8.1 reached its mainstream end
Windows 8.1 None OpenEdge 12.1 of life in January 2018 and is not supported for
OpenEdge 12.1 and later.
In addition to English, OpenEdge supports 13
Supplemental languages out of the box. OpenEdge also provides
None
PROMSGS 21 downloadable supplemental languages that will
not be maintained.
Red Hat has discontinued CentOS and has
OpenEdge 12.5 announced an early end of life for CentOS 8 by
CentOS 8.x N/A
December 31, 2021.
CentOS 7.x reaches its end of life in June 2024.

OpenEdge is not supported on Oracle Solaris for

Oracle Solaris 11 None OpenEdge 12.5
OpenEdge 12.5 and later releases

OpenEdge is not supported on IBM AIX for

IBM AIX None OpenEdge 12.6
OpenEdge 12.6 and later releases

3.2 Deprecated Features and Functionality

The following table contains the current deprecated features and operating systems for OpenEdge
12.0. Timeframe details are published to help partners and customers with their planning. We
recommend substituting obsolete functionality with appropriate equivalents, as indicated in the
following table.

© 2023 Progress Software Corporation. All Rights Reserved. Page 17

Table 13. Deprecated Features and Functionality
Deprecation Information
Deprecated
Replacement Announced
Feature or
Feature OpenEdge Notes
Functionality
Version
• Since OpenEdge 12.2 requires Java 11, and
Aurea Messenger still requires Java 8, the latest
Aurea Messenger MQ client jar is no longer
distributed by Progress.
Aurea Messenger
• Progress OpenEdge JMS Adapter now supports
(Sonic) MQ client jar is Generic JMS
OpenEdge 12.2 multiple JMS 1.1 implementations, not just
included with OpenEdge Adapter
from Aurea. If required, Aurea Messenger MQ
distribution
client jars are available directly from Aurea.
• The 'Generic JMS Adapter' is a separately
downloadable component available on ESD,
post OpenEdge installation.
Enhanced support for
Aurea Messenger MQ OEM/OEE will continue supporting Aurea
by Progress OpenEdge Messenger MQ Adapter configuration, management,
None OpenEdge 12.2
Management (OEM) and and monitoring for OpenEdge releases before 12.2.
Progress OpenEdge
Explorer (OEE)
• Microsoft Windows Server 2016 Failover
Failover Cluster
None OpenEdge 12.2 Clusters (64-bit OpenEdge only)
Managers
• PowerHA 7.1 (HACMP 7.1) with AIX 7.1
Progress OpenEdge
Progress Trade-in Value is available for OpenEdge
Application Server
Application Application Server licenses under a current
(Basic and Enterprise), OpenEdge 12.0
Server (PAS) for Maintenance contract towards the purchase of PAS
including Progress
OpenEdge for OpenEdge.
WebSpeed
Progress
Developer Studio WebSpeed Workshop was part of Progress
WebSpeed Workshop OpenEdge 12.0
(PDS) for WebSpeed, which is already deprecated.
OpenEdge
V9 Debugger V12 Debugger OpenEdge 12.0

Embedded SQL-89/C None OpenEdge 12.0

Translation Manager None OpenEdge 12.0

Progress Dynamics source code can be used and
Progress Dynamics None OpenEdge 12.0
maintained by users in OpenEdge 12.
OpenEdge Replication
None OpenEdge 12.0 Not a performant solution
Synchronous Commit

© 2023 Progress Software Corporation. All Rights Reserved. Page 18

 Deprecation Information
Deprecated
Replacement Announced
Feature or
Feature OpenEdge Notes
Functionality
Version
Both ciphers have documented vulnerabilities.
While these ciphers are removed from internal use
Assorted current by OpenEdge, they continue to be available for ABL
MD5 & RC4 ciphers OpenEdge 12.0 application use. ABL application developers are
ciphers
encouraged to update their products and replace
these algorithms because OpenEdge may drop their
support in a future release.

Ability to directly link C Host Language

Progress supported this in Classic AppServer,
code to the AVM Call (HLC)
OpenEdge 12.0 which is not part of release 12.x. PAS for
running on the feature in
OpenEdge has never supported this.
application server OpenEdge 12.2

New Relic will no longer support or maintain its

plugins after June 16, 2021
https://discuss.newrelic.com/t/new-relic-plugin-eol-
New Relic Plugins for wednesday-june-16th-2021/127267
All OpenEdge
PAS for OpenEdge and OECC 1.2 Agents
Releases
OpenEdge Database The OpenEdge Command Center 1.2 agents are
capable of collecting performance metrics from
PASOE and Database. For more information, refer
to the documentation

Shared AVM feature in

Shared AVM allowed sharing an instance of AVM
Progress Developer None OpenEdge 12.5
across multiple projects in PDSOE.
Studio for OpenEdge

To know about Tools for Business Logic visit

Tools for Business Logic
https://docs.progress.com/bundle/openedge-
in Progress Developer None OpenEdge 12.6
developer-studio-help/page/Learn-About-Business-
Studio for OpenEdge
Logic-Tools_2.html

Support for the smaller database block sizes, 1024

and 2048 kilobytes, will be removed in OpenEdge
12.7.

Sizes 4096 and 8192 were introduced in Progress

V8.2 (1997). The defaults were changed early in
Database block sizes Database block
OpenEdge 12.7 OpenEdge 10.x (4096 for windows and linux, 8192
1024 and 2048 size 4096 or 8192
for unix).

To identify your database block size, use:

proutil describe
and locate the Block Size in the output.

© 2023 Progress Software Corporation. All Rights Reserved. Page 19

 Deprecation Information
Deprecated
Replacement Announced
Feature or
Feature OpenEdge Notes
Functionality
Version
To change the database block size, you must
perform a dump and load of the data into a database
with a new structure. You are able to do this using
your current version.

© 2023 Progress Software Corporation. All Rights Reserved. Page 20

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 configuring 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.

© 2023 Progress Software Corporation. All Rights Reserved. Page 21

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 Linux x86 Oracle Solaris
Database Certified IBM AIX
on Intel (SPARC)
Version Version 32-bit 64-bit
19C 19.3.0.0 12.2 12.2 12.2 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.
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.

© 2023 Progress Software Corporation. All Rights Reserved. Page 22