PAS for OpenEdge is not an AppServer. Its architecture is different, its core server subsystems are different, and its execution of the ABL language sessions is different. Therefore, all of the classic AppServer's administration and monitoring support is inappropriate and is not compatible with PAS for OpenEdge. As a result, any third party automation tools written to monitor a classic AppServer will no longer be useful, and must be rewritten.
PAS for OpenEdge supports a vastly expanded set of metric data collection that provides a broad picture of server and application health. PAS for OpenEdge supports a number of administrative state queries and operations targeted at discovering what is happening at that moment, with the option to correct certain conditions (hangs, runaways, etc.) without having to restart the entire server.
PAS for OpenEdge provides three administrative ports:
1. JMX — The Java standard JMX support for PAS for OpenEdge supplements that of the PAS (Apache Tomcat) JMX administration. JXM gives the administrator full PAS for OpenEdge administration support without exposing the server to dangerous remote administration through Web applications.
2. REST — PAS for OpenEdge provides an optional REST management API through a Web application for OpenEdge Management/OpenEdge Explorer and third party administration tools. This Web application can be secured, but it is not a standard part of the PAS for OpenEdge production server product.
3. Manager — PAS for OpenEdge provides an optional Apache Tomcat Manager Web application for remote administration of the core PAS server. See the Apache Tomcat's Manager documentation for detailed information. The TCMAN utility provides full text client access to PAS information. This Web application can be secured, but it is not a standard part of the PAS for OpenEdge production server product.
