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, you do the following:

  1. Create a PAS for OpenEdge instance that represents the deployment package.
  2. Deploy and configure the OpenEdge ABL web applications that will make up the ABL application.
  3. Deploy and configure any SOAP and REST web services into the OpenEdge ABL web applications.
  4. Deploy the ABL application's .p and/or .r files as part of the instance-name/openedge directory, or an OpenEdge ABL web application's openedge directory (for example, instance-name/webapps/ROOT/WEB-INF/openedge) .
  5. Install any application tailoring scripts into the instance-name/bin directory.
    Note: On UNIX, script files must be set to executable because archive files do not preserve file permissions.
  6. Supply any OS process environment files containing the environment variables needed by your application.
  7. Configure the PAS for OpenEdge server default features and properties. See TCMAN feature and TCMAN config for more information.

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 must, you can deploy the ABL application's .p and .r files anywhere on the OS's file system, just like in a classic AppServer. However, you lose most, if not all, of the benefits of the PAS for OpenEdge infrastructure for deployment, updates, and security.