After you develop Business Process Server applications, you need to package these applications into a single ZIP or JAR file, before sending them to your Business Process Server administrator. The administrator needs to unpack the ZIP or JAR file in order to publish the applications on the production systems.
This method of packaging and publishing Business Process Server applications manually can be error-prone because of the following reasons:
While packaging the applications, you need to ensure that all the dependant JAR files, third-party libraries, adapter classes, and generated files are included.
During publishing, the Business Process Server administrator needs to ensure that all BP Server and Web subprocesses are packaged along with the parent applications.
The administrator must also ensure that all the application folders are copied.
In order to prevent these errors, Business Process Server has developed a command line tool that automates the process of packaging and publishing applications. In this chapter, you will learn about this command line tool and how you can use this tool to package and publish Business Process Server applications.
Note: After developing the application using Progress Developer Studio for OpenEdge, we recommend you to build the project (in Progress Developer Studio for OpenEdge, click Project > Build Project) before trying to package it.
While packaging the applications, you need to ensure that all the dependant JAR files, third-party libraries, adapter classes, and generated files are included.
