A package represents a deployable application or content. It contains URIs, properties, and configuration data that help define how the application is constructed and deployed. To deploy a package, you create an instance that represents a version of this content, with its referenced URI content fetched and stored in the database. Storing this information ensures that the application version is protected from any external influences. 


A reference represents a link to the content (file, directory, archive, and so on) which you use for the deployment process. To deploy a package, you need to create in it at least one reference. Package without reference cannot be deployed. 


When the system creates a package instance, it looks first at the package instance definition for the action name, and it goes to the action library only if no specific action is referenced in the definition. You can add a reference to a package definition that names a piece of content identically to the action that you are calling, which enables the system to use the reference content as the action, meaning that you can retrieve actions from an external repository to use during deployment.


Package references and repository content are associated with a dependency tree. This tree dictates the deployment order for the content.


If you do not identify dependencies, all content for an instance is deployed in parallel.

Specify dependencies to:

  • Deploy the content of an instance in a particular order
  • Deploy multiple pieces of instance content at the same time

For more information, see To add a dependency between two references in a package and To add a dependency between two pieces of content in a repository.


Analyzers identify modules that break down fetched content. They are invoked after a URI has been fetched into the package instance. You configure analyzers to perform specific actions.

Analyzers are associated with references in a package. When an associated reference is fetched, the analyzers are run to further process it. You can assign multiple analyzers in a certain order to a given reference to create a processing chain of events. For more information and a list of available analyzers, see Using analyzers.

Automatic name generation for instances

The name generated for an instance can contain automatically created values, such as a number that automatically increases for each instance constructed or values that represent the time and date that the instance was created. You can specify where to use these automatic values.

Related topic

Creating and viewing package or repository instances

Working with packages

Creating and managing deployments

Enabling role-based access permissions for a package

Was this page helpful? Yes No Submitting... Thank you