Using vRealize Orchestrator Packages

Use the vRealize Orchestrator Client to create, export, and import packages. Packages can be used to export workflow objects for use on other vRealize Orchestrator instances.

Packages can contain workflows, actions, policies, configuration elements, or resources elements.

When you add an element to a package, vRealize Orchestrator checks for dependencies and adds any dependent elements to the package. For example, if you add a workflow that uses actions or other workflows, vRealize Orchestrator adds those actions and workflows to the package.

When you import a package, the server compares the versions of the different elements of its contents to matching local elements. The comparison shows the differences in versions between the local and imported elements. The user can decide whether to import the package, or can select specific elements to import.

For most objects created in the vRealize Orchestrator Client, aside from resource elements, packages are the only way to export and import these objects.

Packages use digital rights management to control how the receiving server can use the contents of the package. vRealize Orchestrator signs packages and encrypts the packages for data protection. Packages can track which users export and redistribute elements by using X509 certificates.

Note: The vRealize Orchestrator Client does not support the creation, import, or export of encrypted packages. To use encrypted packages in the vRealize Orchestrator Client, you must import them to the Orchestrator Java Client and remove the package encryption.