Try OpenEdge Now
skip to main content
Application Migration and Development Guide
Migrating AppServer and WebSpeed Applications : Migrating server configuration and management : Application packaging and installation : Distribution packaging : Basic Web application packaging
Basic Web application packaging
You can deploy an ABL application as one or more OE ABL Web applications. One OE ABL Web application is packaged as one Web Application Archive (.war) file that follows the layout outlined previously (see ABL application structure). For improved performance and resource consumption, you deploy an ABL application using a single OE ABL Web application—making the full application accessible from a single server URL. There are situations where deploying an ABL application as multiple OE ABL Web applications (where the application is accessible across multiple server URLs) is the correct path to follow. Since using multiple OE ABL Web applications slows performance and consumes more OS process resources, use this approach only when:
*Your OE ABL Web application is designed as a set of discrete, individually deployed, services, where the OE ABL Web application encapsulates "service set" within your ABL application.
*You must avoid interrupting classic AppServer clients until they can be upgraded to use a single URL.
When deploying OE ABL Web applications, you can pre-deploy and configure SOAP, REST, and Spring Security. You also have the option of deploying the SOAP, REST, and APSV service interface API's .p and .r files as part of each Web application's WEB-INF/openedge directories. Using the optional embedding of .r and .p modules in the Web application, you ensure that the version of the SOAP, REST, and APSV service interfaces remains consistent with their transport (URI) definitions. You might need to change the ABL application's PROPATH to include the OE ABL Web application's WEB-INF/openedge path.