Try OpenEdge Now
skip to main content
Administration Guide
Application deployment and management : OpenEdge Web application deployment : Packaging web applications

Packaging web applications

The Progress Application Server supports a number of different ways for packaging web applications. Web applications can be packaged as:
*a .war file
*a .zip file that includes the necessary directory structure (see below for more information)
*a UNIX .tar file that includes the necessary directory structure
*a deep copy of the web application's directory
*a soft link (symbolic link) to the web application's directory
The standard directory structure for a web application is:
*/exampleapp - The root directory for the application is located in the server's /webapps directory (default) or another location configured by the administrator. The root directory contains the /WEB-INF folder and any files that have to be visible to the client browser, like HTML and JSP pages. These files can be organized into a subdirectory for more complicated applications.
*/exampleapp/WEB-INF - In addition to the directories listed below, this folder contains the Web Application Deployment Descriptor (web.xml), which contains the configuration information for the application in a standard format
*/exampleapp/WEB-INF/classes - This folder contains any Java class files that are not organized into .jar files, including servlet classes.
*/exampleapp/WEB-INF/lib - This folder contains any .jar libraries needed for the application.
Note: The minimum directory structure required for a web application includes the /exampleapp/WEB-INF directory and the web.xml file. The /WEB-INF/classes and /lib directories are only required when distributing loose Java class files and .jar files.
For more information on Tomcat directory structure, see