As a system administrator of a classic AppServer application, it’s time for you to move those applications to a production staging instance of the PAS for OpenEdge for testing. This Quick Start tutorial gets your applications running and connects your clients to the new server. After completing the steps in this tutorial, review the Next steps with PAS for OpenEdge topic, where you will find additional links for modernizing, securing, and tuning your new server for production.

PAS for OpenEdge is a unified web server that does not require special adapters. All client types send requests to your ABL server code using one of four transports:

The Session Manager distributes those client requests to an underlying Multi-Session Agent which ensures efficient use of your server resources. Built on Apache Tomcat web server technology, and enhanced by OpenEdge development to manage the specific needs of your OpenEdge clients, you get the best of both worlds. Progress development applies Apache Tomcat updates that ensure compliance with industry standards, like Spring security, while supporting all client types in a single server with no additional products, using easy to configure properties files.

A PAS for OpenEdge instance is created with a predeployed ROOT ABL web application (located in the instance-name/webapps directory) and an ABL application with the same name as the instance in the instance-name/ablapps directory. In this tutorial, you will deploy code into the ROOT ABL web application.