Is it expected behavior that the "manager.war" file is not expanded, while all other web apps (.war) files are expanded when the 'pasman deploy' command is run?

Jul 14, 2021
Knowledge

Title

URL Name

Is-it-expected-behavior-that-the-manager-war-file-is-not-expanded-while-all-other-web-apps-war-files-are-expanded-when-the-pasman-deploy-command-is-run

Article Number

000204034

Environment

Product: OpenEdge Version: 11.7.x, 12.x OS: All Supported Operating Systems Other: N/A

Question/Problem Description

Is it expected behavior that the "manager.war" file is not expanded, while all other web apps (.war) files are expanded when the 'pasman deploy' command is run?

Steps to Reproduce

1) Create a PASOE instance either via the command line or OpenEdge management console and do not start it. 2) Deploy the "manager.war" file with the command "PASMAN DEPLOY -I <PASOE_instance_name> <OE_install_directory>\servers\pasoe\extras\manager.war" or through the OpenEdge management console, and you will see that it doesn't get deployed and also not expands in the PASOE instance "webapps" folder. NOTE: If the same is done with "oemanager.war" file or other applications they are deployed successfully even when the PASOE instance is not started.

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

This is expected behavior.

The reason being: there are two primary Java web application deployment processes:
a) A pure Java web application that can run on any Tomcat server.
b) An OpenEdge Java web application made to run only within a PASOE server (Tomcat + the OpenEdge application product).

The Tomcat "manager.war" is an example of a pure Java web application and does not get expanded by Tomcat until the server is started, or an online (-l option) deployment to a running Tomcat web server. Standard Tomcat behavior.

The "oemanager.war", or any customer ABL web app derived from the "oeabl.war" applications, are examples of OpenEdge Java web applications. The OpenEdge Java web applications are deployed differently so that built-in auto-tailoring of the Java web application is executed at deployment time. When deploying those types of .war packages the administration utility tcman looks for, and finds, a WEB-INF/tlr directory with an xxx_tlr file - that triggers TCMAN to do the OpenEdge deployment process. The resulting OpenEdge deployment process will manually expand the .war file into the webapps directory, then execute the built-in tailoring that configures it for use in an ABL application. After the tailoring step, the web application is not running according to the Tomcat deployment model but will be fully expanded and tailored.

Resolution

Workaround

Notes

Progress Article(s):

000195065, How to deploy and where to deploy the manager.war webapp
000156219, PASOE: Manual deployment of OE Manager not functioning
000176012, What's the PASOE oeabl.war file?

Keyword Phrase

Last Modified Date

7/14/2021 9:55 AM

Is it expected behavior that the "manager.war" file is not expanded, while all other web apps (.war) files are expanded when the 'pasman deploy' command is run?

Files(0)

Was this article helpful?

Was this article helpful?

Is it expected behavior that the "manager.war" file is not expanded, while all other web apps (.war) files are expanded when the 'pasman deploy' command is run?

Information

Related Articles