Previous page Previous page

Next page Next page

Locate page Locate page

Print this page

Packaging Overview

This chapter provides general information on what steps should be taken to create and test an application package. It also contains references to the chapters which describe how to perform each step.

It is supposed that you already have a working application. To pack the application in compliance with the APS, do the following:

  1. Consider how the technologies used by the application will be recognized by Controllers. For details, refer to the Before Creating Application Package chapter.
  2. Check if your application complies with the content organization requirements declared in the Specification and update the application content if needed. For details on the requirements, refer to the Creating Application Package Physical Structure chapter.
    This step is regulated by the Specification in sections 1. Introduction, 4.2. Files, 5.3. Additional files and 5.5. Additional scripts.
  3. (Optional) Write scripts that will manage the application package and its instances. For details, refer to the Creating Application Package Scripts chapter.
    This step is regulated by the Specification in sections 4.6. Configuration script and 5.5. Additional scripts.
  4. Create the metadata file that describes the package. For details on how to do it, refer to the Creating Application Package Metadata File chapter.
    This step is regulated by the Specification in sections 4.3. Metadata Descriptor, 4.4. Requirements, 4.5. URL mapping, 5. Points of Extensibility.
  5. Archive the application package files. The package should be a ZIP archive with the .app.zip extension (according to the 4.1. File format section of the Specification).

After you created an application package, you can check if it conforms to APS by using a specific command-line utility. For details on the utility and its usage, refer to the Validating Application Package section.

If an application package is APS-compatible, you can check if it is properly managed by Controllers. To do this, examine the Controller operations that require application package data. The operations are described in Appendix C. Controller Operations on Packages.