5.5

Using Packages 4
You can use packages to transport content from one Orchestrator server to another. Packages can contain
workflows, actions, policies, Web views, configurations, and resources.
When you add an element to a package, 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,
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 content to
matching local elements. The comparison shows the differences in versions between the local and imported
elements. The administrator can decide whether to import the whole package, or choose specific elements to
import.
Packages feature digital rights management to control how the receiving server can use the content of the
package. Orchestrator signs packages and encrypts the packages for data protection. Packages use X509
certificates to monitor which users export and redistribute elements.
This chapter includes the following topics:
n
“Create a Package,” on page 25
n
“Set User Permissions on a Package,” on page 26
n
“Export a Package,” on page 27
n
“Import a Package,” on page 28
n
“Get a Remote Package,” on page 28
n
“Synchronize a Remote Package,” on page 29
n
“Remove a Package,” on page 30
Create a Package
You can export workflows, policies, actions, plug-in references, resources, Web views, and configuration
elements in packages. All elements that an element in a package implements are added to the package
automatically, to ensure compatibility between versions. If you do not want to add the referenced elements,
you can delete them in the package editor.
Prerequisites
Verify that the Orchestrator server contains elements such as workflows, actions, and policies that you can
add to a package.
Procedure
1 From the drop-down menu in the Orchestrator client, select Administer.
VMware, Inc.
25