Deploying a Workflow to an External Orchestrator Instance

Development and production machines can directly deploy a workflow from one Orchestrator instance to another, without having to first export from the source machine and then import into the destination machine.

You can deploy a workflow either in the UI or with the Orchestrator API. This section discusses deployment using the UI; for information on the API methods, see Export a Workflow and Import a Workflow.Requirements:
  • Both Orchestrator instances must be v. 3.1.0 or newer.
  • You must have a remote note that is configured with node type Aspera Orchestrator.
  • The workflow must be in a "Published" state.
  1. In the top menu, click Workflows.
  2. In the list of workflows, click the More icon (), then click Deploy.
  3. From the Target Orchestrator dropdown, select the target Orchestrator node.
  4. If you want the workflow to be published when it deploys, select Publish workflow on Deploy. If you do not select this option, it will remain in a "Draft" state.
  5. Click Deploy.
    A confirmation message, "Successfully deployed workflow" appears.