PAS for OpenEdge is not the classic AppServer. Its architecture is different, its Tomcat server subsystems are different, and its execution of the ABL sessions is different. Therefore, all of the classic AppServer's administration and monitoring support 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 several administrative and monitoring features:

  • 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. PAS for OpenEdge supports the following JMX tools:
    • JConsole, a GUI tool to explore and manage Java beans, can be accessed on the same machine using the process ID (PID) or by opening ports for remote access. However, opening remote ports can be considered a security risk and is only advised for development. For more information, see Run JConsole remotely and JConsole and JMX.
    • The PAS for OpenEdge OEJMX scripts gives the administrator full PAS for OpenEdge administration and monitoring support without exposing the server to dangerous remote administration through web applications. For more information, see Use OEJMX to manage and monitor an instance.
  • OEMANAGER—A command-line utility that allows you to obtain metrics about your Progress Application Server (PAS) instance in one call. The output is an easy-to-read textual representation of the metrics initiated from an OS command line. This concept is most similar to the ASBMAN and WTBMAN utilities previously available within the Classic AppServer product. In addition, the utility can be used to manage runtime behavior. For more information, see OEMANAGER utility in Manage Progress Application Server (PAS) for OpenEdge.
  • 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. For more information, see Use Swagger UI to explore management APIs.
  • Manager — PAS for OpenEdge provides an optional Apache Tomcat Manager Web application for remote administration of the Tomcat server and PAS for OpenEdge applications. See the Apache Tomcat Manager documentation for detailed information. The TCMAN utility provides full text client access to server information. This web application can be secured, but it is not a standard part of the PAS for OpenEdge production server product.
  • HealthScanner — PAS for OpenEdge provides an optional OpenEdge HealthScanner web application that monitors your environment. Enabling data collection for the OpenEdge HealthScanner allows PAS for OpenEdge to collect system data in order to calculate a health score. HealthScanner allows the health of your server to be verified by HTTP request. Additionally, separate HTTP requests can gather summary and detailed information about the data collected. The OEHealth script can be used to gather the summary and detailed information without having to enable the web application which can be considered a security risk. For more information, see Use the OpenEdge HealthScanner.
  • Shutdown port — A shutdown port is an unused port number used for the shutdown of Tomcat. If you are creating a PAS for OpenEdge instance on a Windows machine, then this is a mandatory field. UNIX platforms may disable a shutdown port and use signals to halt a running server. Windows platforms, which lack an effective signaling mechanism, require a valid port number.