4.1

Creating Packages 6
Packages are the vehicle for transporting content from one Orchestrator server to another. Packages can contain
workflows, actions, policies, Web views, configurations, or 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 contents 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 package, or choose specific elements to import.
Packages use 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 can track which users
export and redistribute elements by using X509 certificates.
IMPORTANT Packages that Orchestrator 3.2 generates are upwardly compatible with Orchestrator 4.x. You can
import a package from an Orchestrator 3.2 server into an Orchestrator 4.x server. Packages from Orchestrator
4.x are not backwards compatible with Orchestrator 3.2. You cannot import into an Orchestrator 3.2 server a
package that an Orchestrator 4.x server generates.
For more information about using packages, see .
n
Create a Package on page 135
You export workflows, policies, actions, plug-in references, resources, Web views, and configuration
elements in packages. All elements that an element implements are added to the package automatically,
to ensure compatibility between versions. If you don't want to add the referenced elements, you can
delete them in the package editor.
n
Set User Permissions on a Package on page 136
You set different levels of permission on a package to limit the access that different users or user groups
can have to the contents of that package.
Create a Package
You export workflows, policies, actions, plug-in references, resources, Web views, and configuration elements
in packages. All elements that an element implements are added to the package automatically, to ensure
compatibility between versions. If you don't want to add the referenced elements, you can delete them in the
package editor.
Prerequisites
Elements such as workflows, actions, and policies to add to a package.
VMware, Inc.
135