What is PASOE?
The Progress Application Server (PAS) is the core Web application server, based on Apache Tomcat, that's the foundation for application servers in OpenEdge, and other Progress products. Progress Application Server for OpenEdge (PASOE) is a Progress Application Server that's tailored specifically to support OpenEdge applications, including WebSpeed applications.
Java Requirements
PASOE and Progress uses the same Java which 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. For Linux, these are:
AdoptOpenJDK OpenJDK | Oracle Java SE Development Kit |
jdk-11.0.4+11 (x64) for Linux (Hotspot) | 11.0.4+10 |
PASOE Components
Each environment has at least one PASOE Instance which consists of several components.
PASOE is an Apache Tomcat Web server and servlet container that's customized to provide application server support for OpenEdge applications and to respond to HTTP/HTTPS client requests.
PASOE Components are:
Transports WEB APSV SOAP & REST
PASOE responds directly to HTTP/HTTPS requests because it's an Apache Tomcat Web server with a default ROOT application configured to support APSV (analogous to AIA), REST, and SOAP requests. The Web Transport is part of the OEABL application deployed in the Java Servlet Container of the instance.
Session Manager
The ABL Session Manager in PASOE isn't identical to, but is functionally similar, to the broker in the OpenEdge AppServer. It responds to client requests by communicating with an agent process to assign a session, to make sure that ABL code executes, and to ensure that a response returns to the client. If there are no free sessions in one agent, it launches another agent.
MS Agent
In the OpenEdge AppServer, each agent is an operation system process that handles a single ABL session.
In PASOE, an agent is a single operation system process that can run multiple ABL sessions. It is often referred to as a Multi-session Agent (MSAgent).
*** You configure properties (the number of sessions supported by an agent, the number of agent processes allowed in a server, etc.) in a PASOE instance's /conf/openedge.properties file. It's similar in format to the ubroker.properties file, but it only applies to a single instance. All individual PASOE instances have their own openedge.properties file.
How PASOE and Coins ERP+ handles a request
This section describes how the components of the PASOE Instance interact to respond to a request from a client browser.
The Web server (Apache) receives the request from a Web browser. Each request is in the form of a URL
Apache has symbolic links in the htdocs folder to the Coins ERP+ application for style sheets images etc
Apache uses Coins ERP+ rewrite rules in /etc/httpd/conf.d/coins.conf to adjust style sheets and images as needed
Apache uses a reverse proxy “/etc/httpd/conf.d/<env>.conf” to reroute the requests to the PASOE instance, below is an example of /etc/httpd/conf.d/live.conf
Apache sends the request via a reverse proxy to PASOE via the WEB Transports
Session manager—A process that manages pools of ABL sessions, where each pool runs in the context of a multi-session agent. The session manager coordinates requests from clients and locates ABL sessions to handle each request. The session manager is useful for sizing and configuring an instance.
Multi-session agent—A pool of ABL sessions that executes ABL business logic on behalf of clients.