7.1
Table Of Contents
- Life Cycle Extensibility
- Contents
- Life Cycle Extensibility
- Machine Extensibility Overview
- Extending Machine Lifecycles By Using vRealize Orchestrator
- Configuring Workflow Subscriptions to Extend vRealize Automation
- Event Topics Provided with vRealize Automation
- Workflow Subscriptions and Event Broker Terminology
- Blockable and Replyable Event Topics
- Best Practices for Creating vRealize Orchestrator Workflows for Workflow Subscriptions
- Workflow Subscription Settings
- Working with Provisioning and Life Cycle Workflow Subscriptions
- Configuring vRealize Orchestrator Workflows for Provisioning and Life Cycle Workflows
- Workflow Subscription Life Cycle State Definitions
- Configuring the Timeout Values for States and Events
- Configuring the Error Behavior for States and Events
- Scenario: Take a Post-Provisioning Snapshot of a Virtual Machine
- Working with Approval Workflow Subscriptions
- Troubleshooting Workflow Subscriptions
- Troubleshooting vRealize Orchestrator Workflows That Do Not Start
- Troubleshooting Provisioning Requests That Take Too Much Time
- Troubleshooting a vRealize Orchestrator Workflow That Does Not Run for an Approval Request
- Troubleshooting a Rejected Approval Request That Should Be Approved
- Troubleshooting a Rejected Approval Request
- Extending Machine Life Cycles By Using vRealize Automation Designer
- Extending Machine Life Cycles By Using vRealize Automation Designer Checklist
- Installing and Configuring vRealize Automation Designer
- Customizing IaaS Workflows By Using vRealize Automation Designer
- Workflows and Distributed Execution Management
- CloudUtil Command Reference
- vRealize Automation Workflow Activity Reference
3 Drag the WaitForVcoWorkflowCompletion activity into the Designer pane.
4 In the Properties pane, specify the name of the variable representing the virtual machine ID in
VirtualMachineId.
The customizable workflows contain a variable by default named virtualMachineId that is set
during initialization.
5 Create a variable of type DynamicOps.VcoModel.Common.VcoWorkflowExecutionToken.
6 Create a variable of type DynamicOps.VcoModel.Common.VcoWorkflowExecutionToken.
7 Specify the name of the token variable as the executionToken output parameter on the
InvokeVcoWorkflowAsync activity.
8 Specify the same variable name as the WorkflowExecutionToken property of the
WaitForVcoWorkflowCompletion activity.
9 Retrieve the output of the vRealize Orchestrator workflow.
a Create a variable of type DynamicOps.VcoModel.Common.VcoWorkflowExecutionResult.
b Specify the name of the results variable as the WorkflowOutput property of the
WaitForVcoWorkflowCompletion activity.
When the workflow runs, the value of the variable is set to the results of the vRealize Orchestrator
workflow, if any.
vRealize Orchestrator and IaaS Object Types
When you use either the InvokeVcoWorkflow or the InvokeVcoWorkflowAsync activity in vRealize
Automation Designer, input and output properties for the activity are automatically populated based on
the parameters of the vRealize Orchestrator workflow that you select.
vRealize Orchestrator primitive types are converted into the following IaaS types:
Table 5‑3. vRealize Orchestrator and IaaS Object Types
vRealize Orchestrator Type IaaS Type
string string
boolean bool
number decimal
SecureString string
Text string
Array/T Array<T>
Properties Dictionary<string,object>
Life Cycle Extensibility
VMware, Inc. 70