In PAS for OpenEdge, the OpenEdge Manager application, oemanager.war, is deployed to each instance in order to manage it. OpenEdge Manager is a Java web application that provides a REST API for remote administration of the OpenEdge web applications and multi-session agents. It duplicates the administration API supported by the JMX interface from Tomcat, but it uses JSON input/output payloads instead. The oemanager.war file is required to use REST APIs to manage and monitor the ABL applications and PAS for OpenEdge instances.

Tomcat Manager, which uses JMX, is deployed to a PAS for OpenEdge instance using manager.war.

Both manager.war and oemanager.war can be deployed from the $CATALINA_HOME/extras directory to an instance.

Note: Although they may not be deployed in PAS for OpenEdge, standard Tomcat configuration files and applications (like host-manager.war) are preserved in $CATALINA_HOME/extras.

Be aware that for security reasons OpenEdge Manager should not be deployed on a PAS for OpenEdge instance if, for example, you do not want remote administration enabled on a production server instance. Tomcat Manager and OpenEdge Manager are deployed on a development instance by default, and are required for integration with development tools. Some OpenEdge TCMAN commands, such as tcman.sh info, require Tomcat Manager to be loaded and running to work.