1. Pacific Application Server for OpenEdge
PUG Challenge 2014
----- Meeting Notes (2/19/14 13:05) -----
David Cleary
Principal Software Engineer
June 9, 2014

2. Disclaimer
This presentation is for informational purposes only. You are cautioned that any information contained in this presentation may change in the course of product development. This presentation may not be interpreted as a commitment on behalf of Progress, and future development and release of this product remains at the sole discretion of Progress.

3. Agenda Introduction to the Pacific Application Server for OpenEdge
Pacific Application Server for OpenEdge Architecture
Performance and Scalability

4. Introduction to PASOE

5. Pacific Application Server Platform
Created from Apache Tomcat distribution
Configured for production by default
Default ROOT application replaced
Tomcat manager web applications not installed
Auto deployment disabled by default
Shutdown port disabled on Unix
JMX not enabled by default
Web crawler filtering enabled
Spring Security Framework included
Realms and roles defined to implement access control
Enhanced command line tool to configure and manage server
Will be default implementation for Rollbase and Corticon

6. Pacific Application Server for OpenEdge (PASOE)
Responds to the need for tighter integration between OpenEdge and web technologies for both cloud and on-premise solutions
Re-architecture and re-implementation of the traditional AppServer stack
Runs in PSC’s unified Pacific Application Server (PAS) platform
Simplifies web based ABL application architectures, deployment, and administration
Optional server-side session context management
Security built-in
Open REST APIs & JMX for remote administration
Two products:
Pacific Application Server for OpenEdge (development)
Pacific Application Server for OpenEdge (production)

7. Some Comparisons of PASOE versus traditional AppServer
Mixed stateless & stateful ABL application models per instance
Integrated [adapter] transports
Single web application:
Less process resource consumption
Single configuration
Two tier network connections
Many ABL sessions per OS process
Limited to one ABL application model per AppServer instance
Independent adapters
Multiple web applications:
More process resource consumption
Multiple configurations
Three tier network connections
One ABL session per OS process

8. Pacific Application Server for OpenEdge Architecture (PASOE)

9. PASOE Architectural Concepts and Terms
PAS is a Java web application server with Progress extensions
Optional web application for remote administration using text, html, or JMX proxy APIs
ABL services for Pacific Application Server (ABLPAS)
An collection of Java web applications and resources installed and into a PAS
Java web applications use multi-session agent OS process (MSAgent)
Optional web application for remote administration using REST APIs
ABLPAS web services can be installed into the PAS of other PSC product installations
PASOE is an OpenEdge installed PAS with a pre-installed ABLPAS services
You design, package, deploy, configure, debug, and control access to your ABL application in the context of a web application running in a web server

10. Out With The Old – In With The New
Compare the number of lines and boxes
OLD
NEW
OpenEdge PASOE installation
web server
PAS
Console admin UI
REST/SOAP services
ABLPAS (adapters)
AIA
WSA
REST
MSAgent (n sessions)
Admin Service
Security risk – run in intranet only
uBroker
Agent
Agent (1 session)
OpenEdge RDBMS
Console admin UI
Note: remote OEM administration is optional
ABL Application
OpenEdge RDBMS

11. PASOE Software Ecosystem
Progress Developer’s Studio
unified Pacific Application Server
Administration Services
Session Management
Security Services
Common Services
Command-line Tools
OEE/OEM Administraion
Admin Service
ABLPAS Services
Rollbase Service
Corticon Service
OpenEdge Manager
ABL Application
REST/Mobile/SOAP services ABL r-code Mobile applications
OpenEdge RDBMS

12. PASOE Web Services JMX Console oemanager.war oeabl.war Common Services
Spring Security
REST API
JMX Console
oeabl.war
Network Transports
Spring Security
Admin
Metrics
Logging
Properties
Common Services
ABL Session Manager
MSAgent (ABL sessions)
MSAgent (ABL sessions)

13. PASOE ABL Application Architecture Models
Client controls ABL session model via traditional AppServer connection type
Stateless session model
Equivalent to traditional AppServer state-free connection type (any session, in any Agent, in any PASOE server, can execute a client’s request)
Client can execute concurrent ABL requests – one per PASOE server connection
Client, User, and ABL application context managed entirely by the ABL business application
Asynchronous [out] requests executed within same running ABL session
Stateful session model
Equivalent to traditional AppServer state-aware connection type
Sticky ABL sessions (each client request routed to same PASOE server, MSAgent, and ABL session)
Client context stored within ABL session between requests ( manually deleted)
Client can execute pipelined ABL requests to single ABL session

14. AppServer Event Procedures
agentStartupProc & agentShutdownProc
Executes when Session Manager starts / stops Agent OS process
sessionStartupProc & sessionShutdownProc
Executes when Agent starts/stops an ABL session
Occurred in traditional AppServer when the single ABL session Agent started/stopped
sessionConnectProc & sessionDisconnectProc
Executes when client starts/stops a session-managed (state-aware) connection
sessionActivateProc & sessionDeactivateProc
Executes when client runs a procedure/class
Occurred in traditional AppServer only for session-free (state-free) connections

15. MS Agent Architecture PASOE Web Services Common Services
Admin
Metrics
Common Services
MSAgent Admin
ABL Admin Session
ABL Session Manager
MSAgent Pool
MSAgent
ABL Session & Thread Manager
Free ABL Session Pool
Free OS thread Pool
ABL Request Manager
Shared Resources
OE DB
Active ABL Session Pool

16. Resource Sharing in Initial Release
Shared
Self-service OpenEdge database connections
Procedure libraries
R-code
Promsg files
OS threads
Not shared
Temp-tables / ProDatasets
Sockets (including SOAP and AppServer connections)
Network OpenEdge database connections
LBI & DBI files
ABL session memory

17. PASOE Instances PASOE relies upon PAS’s instance support
Each instance is an individual run-time server
All instances share common binaries, shell scripts, and libraries
All web applications and services are deployed to an instance
The PASOE installation in DLC is a non-runnable template for creating instances
An instance can be a unit of deployment (with customer’s configuration & applications)
All instance lives outside of the OpenEdge install (such as WRKDIR)
An instance’s lifetime can span multiple OE release installations
An instance can have its own shared [web] application libraries

18. Creating PASOE Instances
DLC/servers/pasoe
PASOE (V1.0.0)
Tomcat lib bin conf logs temp work webapps PAS common/lib extras
PASOE Instance
Tomcat bin conf logs temp work webapps PAS common/lib
Start,stop, etc
Full copy
ROOT
tcman.sh create [ports] [alias-name] <target-directory>

19. CATALINA_HOME (version 1.0)
Instance Topology
Tomcat Cluster
Apache httpd
Inst1
CATALINA_BASE
Inst2
CATALINA_HOME (version 1.0)
Inst3
Inst4

20. PASOE Instance Deployment Options
CATALINA_BASE
.WAR applications
Inst2
Inst-A
Deploy preconfigured instance
.WAR applications
.ZIP deployment archive
CATALINA_HOME (version 1.0)
Inst3
Inst4

21. PASOE Upgrades Using Instances
CATALINA_BASE
Inst2
CATALINA_HOME (version 1.0)
CATALINA_HOME (version 1.1)
Inst3
Inst4

22. Configuration and Log Files
<instance>/conf/appserver.properties # PAS configuration properties
<instance>/conf/openedge.properties # PASOE properties (like PROPATH)
<instance>/logs/<oeabl-app>.<date>.log # PASOE web services log
<instance>/logs/ROOT.agent.log # PASOE MSAgent log
----- Meeting Notes (2/19/14 13:44) -----

23. Application Deployment Options
SOAP service
SOAP service descriptor .wsm generated by Proxygen
Deploy .wsm file via PASOE command line tool deploySOAP
REST service
REST/Mobile service descriptor .paar file exported from PDSOE (same as 11.3)
Deploy .paar file from PASOE command line tool deployREST
ABL r-code / libraries
Same as traditional AppServer ( it’s all about PROPATH )
As a OEABL Java web application (.war)
Create .war file from OEABL service with embedded ABL code and SOAP/REST services
Deploy PASOE instance as a ZIP file with pre-installed OEABL services (manual)
----- Meeting Notes (2/19/14 13:44) -----
Propath in openedge.properties

24. Performance and Scalability

25. ATM Test Simulates ATM Banking Transactions Highly update intensive
Machine Specifications
Redhat Linux Server Bit
8 CPU’s
6 GB Ram
Classic AppServer
1 Agent per Client (75 Clients = 75 Agent Processes)
PASOE
1 Agent Period.

26. ATM Test

27. Early Access Availability in Coming Months
Interested? Contact Rob Straight –