If the workflow that you develop calls another workflow that resides on a remote Automation Orchestrator server, certain prerequisites must be fulfilled so that the remote workflow can run successfully.
- All input parameters of the remote workflow must be resolvable on the remote Automation Orchestrator server.
- All output parameters of the remote workflow must be resolvable on the local Automation Orchestrator server.
To ensure that the parameters of the remote workflow are resolvable, the inventory objects that the workflow uses must be available both in the remote and the local Automation Orchestrator servers. In case the remote workflow uses objects from a plug-in, the same plug-in must be available on both Automation Orchestrator servers. The inventories of the remote plug-in and the local plug-in must be identical. In case the remote workflow uses library objects in Automation Orchestrator, like workflows and actions, the same workflows and actions must exist in the inventories of the remote and the local Automation Orchestrator servers.
For example, suppose that you insert the Rename virtual machine workflow in a Nested workflow element in the test workflow that you develop. You want to run the Rename virtual machine workflow in a remote Automation Orchestrator server. When you run the test workflow, the Rename virtual machine workflow is called within the run of the test workflow. You specify a virtual machine to rename from the inventory of the local Automation Orchestrator server. Because the Rename virtual machine workflow runs on the remote Automation Orchestrator server, the same virtual machine must be available in the inventory of that server. Otherwise, the Rename virtual machine workflow cannot resolve its vm input parameter. Therefore, the vCenter Server plug-in on the local and the remote Automation Orchestrator servers must be connected to the same vCenter Server instance.
