PAS for OpenEdge can be packaged and deployed as a complete, pre-configured instance. The instance can be unpacked in an OS file system and reconfigured for the local OpenEdge installation and for the site's requirements. Briefly stated, the process involves:
1. Creating a PAS for OpenEdge instance that represents the deployment package.
2. Deploying and configuring the OE ABL Web applications that will make up the ABL application.
3. Deploying and configuring any SOAP and/or REST Web services into the OE ABL Web applications.
4. Deploying the ABL application's .p and/or .r files as part of the instance's openedge directory, or an OE ABL Web application's openedge directory.
5. Locating any optional files used by your ABL application in the instance's extras directory.
6. Installing any application tailoring scripts into the instance's bin directory.
Note: On Unix, script files must be set to executable because archive files do not preserve file permissions.
7. Supplying any OS process environment files containing the environment variables needed by your application.
8. Configuring the core PAS server's default features (see TCMAN in the Progress Application Server for OpenEdge: Administration Guide) and properties (see the TCMAN config command).
To do the packaging, use the Java jar utility or the WinZip (or equivalent) utility to create a single archive file that starts with the instance's root (CATALINA_BASE) directory.
Note: 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 OE infrastructure for deployment, updates, and security.
