About the AppPackager and AppDeployer Tools

The command line tool consists of the following two parts:

AppPackager — This component packages Business Process Server applications and its dependant components into a single ZIP file. In order to use AppPackager, you need to create an application metadata file, which is an XML file containing the details of all the applications that need to be published. The metadata XML file also contains the information about the application folders that need to be copied.

AppDeployer — This is the application publisher component that publishes the Business Process Server applications on existing Business Process Server servers.

Important: If https is enabled, then valid certificate needs to be added to the JDK within BP Server. If valid certificates are not added then publishing of applications and many other operations using WebServices will fail. For more information on how to add the certificate, refer to your Application Server documentation on which BP Server is installed.

Both the AppPackager and AppDeployer components use the Apache ANT build tool that is packaged with Business Process Server or is available as a plug-in with Eclipse in Progress Developer Studio for OpenEdge. This tool uses the appbuild.xml file with various targets to package and publish applications.

For BP Server: appbuild.xml file is located in the OEBPS_HOME\apppackager directory.

For Progress Developer Studio for OpenEdge: appbuild.xml file is located in the DeveloperStudio3.7\eclipse\plugins\com.savvion.studio.resources_<version>.<timestamp>\apppackager directory.

The AppPackager component uses the application metadata file as the input and packages the applications into a single ZIP file (see Applicationpackage details). The AppDeployer component uses the ZIP file as the input and publishes all the applications. It also copies the resource files specified in the XML metadata file.

In this section:

Application metadata

Application package details

Setting properties