To reuse workflows, actions, policies, Web views, and configuration elements from one Orchestrator server on another server, you can import them as a package.
Important
Packages that Orchestrator 3.2 generates are upwardly compatible with Orchestrator 4.x and 5.1. You can import a package from an Orchestrator 3.2 server to an Orchestrator 4.x or 5.1 server. Packages from Orchestrator 4.x and 5.1 are not backward compatible with Orchestrator 3.2. You cannot import to an Orchestrator 3.2 server a package that an Orchestrator 4.x or 5.1 server generates.
Prerequisites
■
|
Back up any standard Orchestrator elements that you have modified. If the imported package contains elements whose version number is later than the version number of the elements stored in the Orchestrator database, your changes might be lost.
|
■
|
On the remote server, create a package and add the necessary elements to it.
|
Procedure
1 | From the drop-down menu in the Orchestrator client, select Administer. |
2 | Click the Packages view. |
3 | Right-click within the left pane and select Import package. |
4 | Browse to select the package that you want to import and click Open.
Certificate information about the exporter appears.
|
5 | Review the package import details and select Import or Import and trust provider.
The Import package view appears. If the version of the imported package element is later than the version on the server, the system selects the element for import.
|
6 | (Optional) Deselect the elements that you do not want to import.
For example, deselect custom elements for which later versions exist.
|
7 | Click Import selected elements. |
The imported package appears in the list of packages.
What to do next
You can use all the workflows, actions, policies, Web views, and configuration elements from the imported package as new building blocks on your Orchestrator server.