The
Tomcat Java Servlet has a strict requirement that a ROOT webapp must exist in order for Tomcat\PASOE to work.
- In PASOE the ROOT webapp is replaced by (our) oeabl.war webapp, which is the default OpenEdge ABL Web application that implements OpenEdge adapters.
- The oeabl.war a type of Java Web application that is pre-configured, with security and Java Servlet interfaces that translate HTTP client requests into ABL requests which schedules their execution using the ABL Session Manager.
- This means that the ROOT webapp required by a Tomcat JSE in a PASOE instance is in reality, simply the oeabl.war deployed with the name ROOT and not the original Tomcat ROOT.war which can also be found under {CATALINA_HOME}/extras.
- The oeabl.war can also be deployed and renamed to create OEABL WebApps. The name of all oeabl.war web applications deployed are updated in the {CATALINA_BASE}\conf\openedge.properties configuration file to know which webapps to manage. OEE/OEM uses this file to manage PAS instances when the oemanager.war is deployed.
Further information is provided by way of example in Article: Must oeabl.war be deployed multiple times when multiple ABL applications run in a single PASOE instance
The
{DLC}\servers\pasoe\extras folder contains additional WAR files that support OpenEdge features exposed as WebApps. These instance management application .war files can optionally be deployed to an instance to support OpenEdge applications and management.
Specific to the
oeabl.war context:
- noaccess.war - To assure when the ROOT webapp exists but is not used, will secure the ROOT webapp in production environments. The server will not expose a JSESSIONID for the ROOT application which is otherwise the oeabl.war. Importantly since OpenEdge 12.2, the PAS for OpenEdge production security model uses noaccess.war deployed to the ROOT application, instead of oeabl.war
The PAS instance will not become a PASOE server until an oeabl.war based webapp is deployed. For further information refer to Article: How to deploy the default secured ROOT webapp for PASOE?
Specific to the
oemanager.war context entirely different to oeabl.war:
- oemanager.war - PASOE Java Web application, required to support OEE/OEM management and monitoring of PASOE ABL applications. It provides a REST API for administration of the OpenEdge Web applications and ABL language engines. It uses the same administration API supported by Tomcat's JMX interface, providing a REST API for remote administration of the OpenEdge Web applications and ABL language engines. It duplicates the same administration API supported by Tomcat's JMX interface, using JSON input/output payloads instead.
Tomcat Web applications provide remote online administration access:
- manager.war - Tomcat Manager Web application, to manage web applications, including deployment and stopping and starting web applications. The manager.war is not the same as oemanger.war. This manager.war is the Tomcat manager, while oemanager.war is an PASOE REST API for managing the instance.
- host-manager.war - Tomcat Host Manager Web application, to manage virtual hosts. In PAS for OpenEdge, a Java Web application, OpenEdge Manager (oemanager.war), is deployed instead of the Tomcat Host Manager (host-manager.war).
