This type of installation extends an existing PAS for OpenEdge instance. While deployment of general Web applications can be performed online or offline, the implementation of the OE ABL Web applications indicates that the installation is best performed offline.
To install a prepackaged OE ABL Web application:
1. Load the .war file containing the prepackaged OE ABL Web application.
2. Run the instance's tcman.{sh|bat}deploy command to load the Web application into the instance's Web application directory.
3. Run the oeprop utility to configure the Web application in the ABL application's openedge.properties file.
4. Run the oeprop utility to configure the Web application's APSV, SOAP, and REST transports according to site requirements.
5. Use a text editor and configure the OE ABL Web application's security according to the site requirements. (See the sections on security in the Progress Application Server for OpenEdge: Administration Guide.)
6. Deploy any .p or .r code required to support the new OE ABL Web application.
a. If the ABL .p or .r code is packaged inside the OE ABL Web application, use the oeprop utility to add its path to the ABL application's PROPATH.
b. If the ABL .p or .r code is packaged inside the OE ABL Web application but needs to be moved elsewhere, move it and update the ABL application's PROPATH with its new location.
c. If the ABL .p or .r code is packaged externally, expand that distribution to its new location and update the ABL application's OE ABL Web.
If you absolutely must, you can deploy the ABL application's .p and/or .r files anywhere on the OS's file system, just like in a classic AppServer. However, you loose most, if not all, of the benefits of the PAS for OpenEdge infrastructure for deployment, updates, and security.
