Progress Application Server (PAS) for OpenEdge offers the following new features in OpenEdge 12.2:

Create and deploy OpenEdge Application Archive (OEAR) packages

The following new topics were written in support of the OpenEdge Application Archive (OEAR) packaging and deployment structure:

  • OpenEdge Application Archive Structure

    Details about the requirements for the structure of OEAR packages are explained in the OpenEdge Application Archive Structure topic in Manage PAS for OpenEdge.

  • Create an OpenEdge Application Archive using TCMAN export

    The OpenEdge Application Archive (OEAR) is a new application packaging strategy where an ABL application and its components are packaged as a unit of deployment. This packaging simplifies ABL application deployment, and supports ABL application deployment in CI/CD pipelines.

    For more information, see Create an OpenEdge Application Archive using tcman export in Manage PAS for OpenEdge.

  • Create an OpenEdge Application Archive using an Ant Build

    PAS for OpenEdge now includes an OpenEdge Ant Task called ABLApp that allows system administrators or DevOps engineers to automate the creation of OpenEdge Application Archive (OEAR) packages for use in CI/CD pipelines.

    For more information, see Create an OpenEdge Application Archive using an Ant Build and Tailor an ABLApp installation using Ant in Manage PAS for OpenEdge.

  • Deploy an ABL application as an OpenEdge Application Archive

    PAS for OpenEdge has introduced a new application deployment strategy where an ABL application and its components are packaged as an OpenEdge Application Archive (OEAR). This new deployment strategy supports ABL application deployment in CI/CD pipelines.

    For more information, see Deploy an OpenEdge Application Archive using tcman import in Manage PAS for OpenEdge.

Enhanced ABL session management

PAS for OpenEdge enhanced the multi-session agent so that it self-manages ABL sessions. This means that requests no longer fail due to resource unavailability.

For more information, see Enhanced ABL session management in Manage PAS for OpenEdge.

Deploy new web handlers in OpenEdge 12.2

Web handler deployment changed in OpenEdge 12.2. The existing deployment model for web handlers is still supported, but a new web handler model was added that can help mange large numbers of APIs and does not require edits to the openedge.properties file.

Using the new functionality, web handlers are no longer specified in openedge.properties, but through an information file for each web service called either ROOT.handlers or webapp-name.handlers.

For more information, see Deploy web handler services in Manage PAS for OpenEdge.

PAS for OpenEdge new production security model

PAS for OpenEdge added a third security model to the product, which is a subset of the Production security model. The security model is called pas and it is accessed at instance creation by using the -Z pas option. Specifying the pas production security model creates an instance with a WAR file called noaccess.war that is deployed to the ROOT application, instead of oeabl.war. Additionally, instances with this security model have no default ABL application deployed, and therefore does not have a multi-session agent.

For more information, see Security configurations in Manage PAS for OpenEdge.

New HealthScanner views and custom view support for the OpenEdge HealthScanner

The OpenEdge HealthScanner added two new data views that can be accessed with the following URLs on a running PAS for OpenEdge instance with HealthScanner enabled:
  • http://hostname:8899/health?view=config
  • http://hostname:8899/health?view=dataset
These views provide server health information in an ABL dataset-friendly format.

For more information, see Access HealthScanner data topic in Manage PAS for OpenEdge.

Additionally, OpenEdge 12.2 offers the ability for system administrators and DevOps engineers to write their own custom HealthScanner views for monitoring their PAS for OpenEdge instances.

For more information, see Write a custom HealthScanner view in Manage PAS for OpenEdge.

Swagger enabled by default on development instances

In OpenEdge 12.2, the Swagger REST API monitoring and testing tool is enabled by default when OpenEdge Manager is deployed to the instance.

For more information, see Use Swagger UI to explore management REST APIs in Manage PAS for OpenEdge.

PAS for OpenEdge Lite

OpenEdge 12.2 offers a new licensing option for users who want to use PAS for OpenEdge in production.

For more information, see PAS for OpenEdge Lite in Learn About Progress Application Server for OpenEdge.