1. Care and Feeding of the Pacific Application Server for OpenEdge in Production
David Cleary
Principal Software Engineer
Progress Software

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 any commitment on behalf of Progress, and future development, timing and release of any products, features or functionality described in this presentation remains at the sole discretion of Progress.
D I S C L A I M E R

3. What We Will Be Talking About
Architecture
Configuration
Administration
Migration
Demo
Early Software Access Program
Architecture: Quick overview of architecture, for more detailed information please refer to Dave Cleary’s talk ***need name of talk***
Configuration: Different
Migration: Differences running an application from Classic to PAS for OE
Administration: How to administer, monitor and manage
DEMO: I love live demos!
ESAP: This is great! How do I get the new PAS for OE?

4. PAS for OpenEdge Architecture

5. Not just the architecture, but how you have to think about an AppServer application. Not just the components, but how they interact and change management and administration.

6. It is not a repackaged AppServer
Architecture: Basics
It is a web server:
Tomcat
It is not a repackaged AppServer
We migrated the functionality – not the implementation
Its designed for the Cloud
Scales
New monitoring and administration tools

7. Architecture: Components
Classic AppServer Components
PAS for OpenEdge Components
Client
AIA WSA
REST/Mobile
Client
AdminServer
PAS for OpenEdge
NameServer
APSV (AIA) SOAP (WSA) REST/Mobile
Session Manager
AppServer
CLASSIC
Must have an AdminServer
- AdminServer starts NameServer and AppServer
- then the AdminServer is just used to monitor and manage
Client connects to NameServer (optional) and is then redirected to the AppServer
If the Client needs to connect through the internet (HTTP/HTTPS)
- you must install and configure separate and distinct adapters AIA/WSA/REST/Mobile
PAS for OE
Start the PAS for OE instance
Client connects using HTTP/HTTPS always
+ AdminServer is not necessary (except for running OEMgmt on the same machine or publishing)
+ There is NO NameServer (load balancing and fault tolerance are handled another way)
Agent (1 ABL Session)
MSAgent
1 ABL Session
1 ABL Session
ABL Sessions

8. Architecture: Session Models
Classic AppServer Instance
PAS for OpenEdge Instance
Session states are controlled and set at the AppServer
State-aware
State-reset
Stateless
State-free
Client controls ABL session model via the CONNECT –sessionModel option
Stateful session model
-sessionModel Session-Managed
Statefree session model
-sessionModel Session-Free

9. Architecture: Multi-Session Agent
Multiple client requests at the same time
Supports both Session-Managed and Session-Free request simultaneously
Manages database shared memory connections
Uses much less system resources
Is as much as 7 times faster than the single session AppServer agents

10. Classic AppServer Components
Architecture: Sample
Classic AppServer Components
PAS for OpenEdge Components
Client
AIA WSA
REST/Mobile
Client
AdminServer
NameServer
PAS for OpenEdge
State-Free
Rest/Mobile
APSV (AIA) SOAP (WSA) REST/Mobile
State-Aware
Stateless
Session Manager
AppServer
Agent (1 ABL Session)
50 Agents
AppServer
Agent (1 ABL Session)
50 Agents
AppServer
Agent (1 ABL Session)
50 Agents
CLASSIC
Must have an AdminServer
- AdminServer starts NameServer and AppServer
- then the AdminServer is just used to monitor and manage
Client connects to NameServer (optional) and is then redirected to the AppServer
If the Client needs to connect through the internet (HTTP/HTTPS)
- you must install and configure separate and distinct adapters AIA/WSA/REST/Mobile
PAS for OE
Start the PAS for OE instance
Client connects using HTTP/HTTPS always
+ AdminServer is not necessary (except for running OEMgmt on the same machine or publishing)
+ There is NO NameServer (load balancing and fault tolerance are handled another way)
MSAgent
1 ABL Session
150 ABL Sessions

11. Architecture: Products
PAS for OpenEdge Development
Debug and management tools installed
We create a sample instance at install time (OEPAS1)
Limited concurrent connections
Ability to compile code
Installed automatically with Progress Developer Studio
PAS for OpenEdge Production
Designed for high security
Unable to compile code
Debug and management tools _NOT_ installed by default
Unlimited concurrent connections

12. Architecture: NameServer and AdminServer
There is _NO_ NameServer with PAS for OpenEdge
Load balancing will be handled _before_ the PAS for OpenEdge instance
Any HTTP/HTTPS load balancing product should work
The AdminServer is not required to manage PAS for OE unless:
you want to PUBLISH
you want to manage PAS for OpenEdge using OpenEdge Explorer
you want to monitor PAS for OpenEdge using OpenEdge Management

13. PAS for OpenEdge Configuration

14. Create a new PAS for OpenEdge instance
Configuration
Create a new PAS for OpenEdge instance
In the Classic AppServer you created a new AppServer by adding a definition in the ubroker.properties file
With PAS for OpenEdge you create an working instance of the “read-only” instance in $DLC/servers/pasoe in a new location
$DLC/servers/pasoe/bin/tcman.sh create –p 8080 –P 8443 –s /psc/115/wrk/oepas1
Start the new PAS for OpenEdge instance
/psc/115/wrk/oepas1/bin/tcman.sh start

15. Configuration: PAS for OpenEdge at Instance Create and Run-time
PAS for OE Instance
*.sh conf logs temp work webapps openedge
/psc/115/wrk/oepas1
create
( CATALINA_BASE )
$DLC/servers/pasoe
PAS for OE Process
lib bin *.sh conf logs temp work webapps common/lib openedge
run
OS Process
PAS for OE (template)
lib bin *.sh conf webapps common/lib openedge extras
( ROOT [ *.war ] )
Full copy
Copy & tailor
( CATALINA_HOME )

16. Configuration: Files
openedge.properties
In <pas_instance>/conf directory
Use oeprop.sh/bat to make changes
appserver.properties
Use tcman.sh features to modify values in this file
Log files
In <pas_instance>/logs directory
OpenEdge and Tomcat files

17. PAS for OpenEdge Administration

18. Administration: tcman.sh/.bat
Server actions
create
start
clean
feature
env
Manager actions
deploy
enable
delete
stop
clean -A
ON or OFF
shows env and running status
undeploy web apps
disable web apps
TCMAN is your all-in-one administration tool
tcman extends all Tomcat administration and enables PAS for OE administration
For help with TCMAN: tcman.sh/.bat help
tcman.sh/.bat help action

19. Administration: More Command Line Tools…
deployREST.sh/.bat
undeployREST.sh/.bat
deploySOAP.sh/.bat
undeploySOAP.sh/.bat
oeprop.sh/.bat
oeprop.sh/.bat testinst.ROOT.SOAP.wsaUrl=
oeprop.sh/.bat +AppServer.Agent.oepas1.PROPATH=.,${WRKDIR}
oeprop.sh/.bat ~ AppServer.SessMgr.agentStartupParam="-db sports"

20. Administration: OpenEdge Explorer and Management
For full management AdminServer must be local
OpenEdge Management
Can monitor and alert
But trending is not available yet

21. Administration: Log Files
Log files are located in the <pas_instance>/logs directory
Problems with the web server:
catalina.out – log for tomcat instance startup and shutdown
catalina.<date>.log – same as catalina.out and standard error
Problems with an application
localhost.<date>.log – application logging
localhost_access_log.<date>.txt – HTTP response messages (200,401,404)
Problems with the PAS for OpenEdge instance
<application_name>.<date>.log – session manager messages and errors
<application_name>.agent.log – multi-session agent messages and errors

22. Administration: New Monitoring Access!
Classic AppServer tools
asbman –query
OpenEdge Explorer or Management
PAS for OpenEdge
Management REST API
The “oemanager” application must be installed for access to the REST API
JMX Remote access
Using Jconsole
Locally by PID
Remotely running “tcman.sh/.bat feature JMXLifecycle=on”
Nagios
3rd party tool recommended by Tomcat for monitoring
Uses the tools above to monitor, alert and graph

23. Migration - PASOE Upgrades
Inst1
CATALINA_BASE
Inst2
PASOE (version 11.5)
PAS OE (version 11.6)
Inst3
Inst4

24. PAS for OpenEdge Migration

25. Migration: Connect Method
REST/Mobile clients: No differences in URL ../rest/.. to ../rest/..
SOAP clients: ../soap/.. instead of ../wsa/.. in URL
OpenEdge clients
URL connection format only
-URL http[s]://host[:port]/[oeabl-path]/apsv
Default URL
-URL
Reference: Connecting to AppServers Using a URL

26. Migration: Configuring AppServer Event Procedures
Changes to openedge.properties
New agent Startup and Shutdown values
srvr values have been renamed to session
Some ABL code may need changes
CONNECT – as in previous slide
sessionStartupProc & sessionShutdownProc
Binding a session
QUIT to clean up (mimic State-Reset)

27. PAS for OpenEdge Demo

28. Not Quite Live Demo
Need extra power point slides showing demo in case of problems and when the slides are posted online.
Show HTTP connect
Show REST API call
Show Nagios with data

29. We have several ways you can get metrics data with the new PAS for OE
In development mode you can hit the and you will see a landing page with Adapter Status. (This is an older screen shot, this will look different in 11.5 shipment, but the same data is represented.
Here you can see the SessionID and the Session Type. Notice both Session-Managed and Session-Free can be run on any Session.

30. We also give you an OpenEdge Manager Application (oemanager
We also give you an OpenEdge Manager Application (oemanager.war) automatically installed in Developer product. You have to install in Production product if you wish.
This is a REST API application. This browser shows the data for a “sessions” call.
You can run this from CURL or use the “jget” script in the $DLC/servers/pasoe/bin directory (a JAVA HTTP Curl-like command-line utility).
You can get metrics, requests, agents and you can also run some management API’s, like terminating a session.

31. This is the OpenEdge Explorer or Management tool.
It gives you all the tools to manage the Session, Requests, Connections and Agents.
Here you can see the data about sessions and can terminate sessions.

32. This is the JAVA Jconsole. It comes with JDK 1. 6 or higher
This is the JAVA Jconsole. It comes with JDK 1.6 or higher. So you will find it in your 11.5 install under $DLC/jdk/bin/jconsole.
You may connect using the PID of the Jconsole is running on the same machine as the PAS for OE instance.
Or you can setup remote administration using tcman.sh feature and turning on the JMXLifecycle.
This will allow you to look for idle sessions, long running sessions (maybe you want to terminate long running sessions? You decide what long running means)
You can do everything in the JMX console, same as REST API’s, but you don’t have to open ports if running on the same machine.

33. Now we can use the new metrics tools to plug into a 3rd party tool like Nagios.
Nagios has a pay for Enterprise version, but it also has a free edition where you do all the configuration yourself.
Nagios is the recommended tool to monitor Tomcat from Apache.
Here we see the Nagios dash board.
If you see the little graph icons, these are graphs you can quickly review.
You can also set up Nagios to alert you if conditions aren’t OK, like if a service shows as WARNING or CRITICAL like in this picture.

34. Here we selected the graph for the JMX memory of the tomcat instance.
This uses the JMX connection to gather this information, like Jconsole would, but in script form.

35. Here we selected “Concurrent Connections” these are snap shots of how many connections there are.
This uses the REST API way of gathering metric information.
We hope that all of the metric data we are now supplying will allow everyone to get the information they need to manage their Application in the new PAS for OE.

36. Some Tomcat References
Connecting Tomcat to the World
Apache Tomcat and SSL
Monitoring Apache Tomcat
20with%20JMX.pdf

37. PAS for OpenEdge Early Software Access Program

38. Early Software Access Program
Want to try it before (almost) anyone else?
Sign up for the ESAP program (started September 30, 2014)
Download a cdimage
Please log any issues in the ESAP forum

39. Q&A

40. Visit the Resource Portal
Get session details & presentation downloads
Complete a survey
Access the latest Progress product literature