The Packages view provides a way to synchronize a package on one Orchestrator server with an existing package on another server.
Synchronizing packages is the only way to obtain all the elements from the remote server. If you synchronize individual elements, Orchestrator only synchronizes elements that already exist on the local server. To obtain any new elements from the remote server, you must synchronize the package that contains those elements.
Procedure
1 | From the drop-down menu in the Orchestrator client, select Administer. |
2 | Click the Packages view. |
3 | Right-click the package that you want to synchronize and select Synchronize. |
4 | Log in to the remote server.
The Orchestrator Synchronization dialog box opens. It displays the differences between the package elements. To view only elements that are different on the local and remote server, select Hide identical from the drop-down menu.
|
5 | View the comparison between the local and remote package elements and select an option.
|
|
|---|
|
None
|
The local and remote elements have the same version number. No synchronization is required.
|
|
Commit
|
The version of the local element is later. The remote element is overwritten.
|
|
Update
|
The version of the remote element is later. The local element is updated. If an element does not exist locally, it is imported from the remote server to the local server.
|
|
Merge
|
The local and remote packages are overwritten with a merged list of references. The referenced elements remain unchanged.
|
Note
If the remote server does not recognize your certificate, you cannot commit elements.
|
6 | Click Synchronize. |
The synchronized package is reloaded.
What to do next
You can use the updated package content in workflows, actions, policies, and Web views.