5.5.2

Table Of Contents
An asynchronous proxy workflow returns immediately a result that is a local wrapper of the remote
workflow token object. The proxy workflow uses this token to check the state of the run and to retrieve the
output parameters when the remote workflow completes its run. The output parameters can be used
directly by other workflows on the local Orchestrator server when they are of simple type, such as, boolean,
number, string, and similar.
Remote Execution Workflows
The Remote Execution workflow category contains workflows that allow you to manage proxy workflows.
Remote Execution Standart Workflows
You can access the workflows to create proxy workflows from Library > Orchestrator > Remote Execution
on the Workflows view in the Orchestrator client.
Workflow Name Description
Create a multi proxy action Creates a multi-proxy action to run workflows on multiple servers.
Create a proxy workflow Creates a proxy workflow that you can use to start a workflow on a remote
Orchestrator server.
Create proxy workflows from a folder Creates proxy workflows for all workflows in a folder on the remote
Orchestrator server.
Server Proxies
You can access the workflows for managing server proxies from Library > Orchestrator > Remote Execution
> Server Proxies on the Workflows view in the Orchestrator client.
Workflow Name Description
Create proxy workflows for a vCO server Creates proxy workflows on the local Orchestrator server by mirroring the
remote server's structure.
Delete proxy workflows for a vCO server Removes the proxy workflows for the local Orchestrator server and deletes
all generated workflows.
Refresh proxy workflows for a vCO server Regenerates all proxy workflows for the local Orchestrator server from the
remote server.
Using the Multi-Node Plug-In Inventory
The Multi-Node plug-in mirrors all inventories of the connected vCenter Orchestrator servers in the
Inventory view. You can use the Inventory view to add authorization elements or to run workflows on
remote Orchestrator servers.
You can enable the Use contextual menu in inventory option to display the workflows that are available for
an inventory object. After the option is enabled, when you right-click an object in the Orchestrator
inventory, all available workflows for the object are displayed.
The inventory for a single remote server consist of two major parts, system objects and plug-in objects. Both
objects are wrappers of the remote objects into locally usable types:
System object
System objects are under a top-level group called System.They contain
configurations, packages, workflows, actions, and related folders. Remote
system objects have individual wrapper types.
Plug-in objects
Plug-in objects mirror the inventories of all plug-ins attached to the remote
Orchestrator server. Remote plug-in objects are all wrapped into a single
local type VCO:RemotePluginObject.
Chapter 19 Configuring and Using the Multi-Node Plug-In
VMware, Inc. 113