Migrating an application to PAS for OpenEdge means reorganizing your application structure with the goal of making applications easier to deploy, scale, and extend. PAS for OpenEdge is a web server, and your applications will move toward a web server application structure. Code can be organized at the following levels:
  • Install directories
  • Instance directories
  • Application directories
  • Service directories

Install directories

The PAS for OpenEdge install directory enables you to have a default behavior across all instances. Having this behavior separated into the installation directory structure makes it easier to upgrade to a new version of the PAS for OpenEdge server without losing the customizations that were made to the individual instances.

Instance directories

The instance directories enable you to customize each instance. Changes made at the instance level override those at the installation level. Each instance contains the following structures and related content:
  • bin—OpenEdge and custom utilities and libraries that are tailored to that specific instance. For example, OpenEdge utilities are tailored to use the file space of the local instance but load and use installed shared libraries and utilities.
  • common/lib—Java libraries and files that are shared across all of the web applications in the instance.
    Note: The server installation directory also has a common/lib directory that holds java libraries and files shared by all web applications across all instances.
  • conf—The Tomcat, OpenEdge, and custom configuration files for the instance that control only the applications deployed into the instance.
  • logs—The log files for the server instance, including all of the server, web application, OpenEdge, and ABL application log files.
  • openedge—The .p and .r files and supporting files only for ABL applications. Other Progress and third-party web applications cannot write or read from this directory.
  • temp—Application-generated temporary files. These files can be deleted by an administrator as part of cleaning up before restarting the server instance.
  • webapps | webapps-ref—A directory, or a reference to a directory, that contains the Tomcat, OpenEdge, and customer-written ABL web applications for the instance.
  • work —Application-generated persistent working files.
    Note: These files should not be deleted by an administrator as part of cleaning up before restarting an application.

For more information about PAS for OpenEdge instances, see Instances.

Application directories

A typical ABL web application directory structure may follow the model set by the OpenEdge ABL web application (oeabl.war). Copies of oeabl.war can be deployed to your instance from the $DLC/servers/pasoe/extras directory.
  • /apsv—A URI path reserved for OpenEdge client connections (can be disabled).
  • /soap—A URI path reserved for OpenEdge soap client connections (can be disabled).
  • /rest—A URI path reserved for OpenEdge REST clients (can be disabled).
  • /web—A URI path reserved for classic WebSpeed applications and new REST clients (can be disabled).
  • static—A directory that contains static files, including images, style sheets, and HTML pages.
  • META-INF—A required directory that contains metadata and context.xml definitions specific to the web application. OpenEdge uses a tailored context.xml file for the web application, and can be tailored by the deployment site to meet security requirements.
  • WEB-INF—A required directory holding the web application's configuration file (web.xml), Spring Security configuration files, and other application private files.
    • adapters—OpenEdge directory tree that contains the REST and SOAP deployment files.
    • lib—Required directory that contains any Java libraries specific to the web application.
    • classes—Required directory that contains any Java classes or data files specific to the web application.
    • openedge—Directory provided by OpenEdge where ABL developers can distribute their ABL application files that apply specifically to the web application

For more information about ABL web applications on PAS for OpenEdge instances, see Web applications.

While an ABL application could physically locate their files anywhere in the OS's file system, locating them inside of the PAS for OpenEdge web application instances promotes scaling, extensibility, and deployment. By organizing files, it is easier to:

  • Deploy an ABL application (identified by name) to an existing PAS for OpenEdge instance.
  • Secure an application by configuring it as read-only. For example, common .r and .p files used across multiple web applications located in the openedge/* directories of the instance.
  • One or more web applications like oeabl.war that may be deployed to an existing PAS for OpenEdge instance. They are used to host APSV, SOAP, REST, and WEB transport access to ABL business logic.

For more information about ABL applications on PAS for OpenEdge instances, see ABL applications.

ABL service directories

An ABL service is a transport-dependent path into an ABL application's business logic (business entities). The ABL service names are defined at development time and do not change at deployment.