7.3
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
- Index
5 When you are nished editing the workow, update the workow in the Model Manager by clicking
Send.
The workow is saved and appears as a new revision in the list the next time you load a workow. You
can access an earlier version of a workow at any time. See “Revert to a Previous Revision of a
Workow,” on page 61.
Using vRealize Orchestrator Workflow Activities
You can use vRealize Automation Designer activities to call vRealize Orchestrator workows either
synchronously or asynchronously.
A vRealize Orchestrator endpoint is specied in one of the following ways:
n
VirtualMachineId is the name of the variable representing the virtual machine ID. A virtual machine
with this ID is selected and the value that is retrieved from the
VMware.VCenterOrchestrator.EndpointName custom property for a virtual machine is used as the
vRealize Orchestrator endpoint name.
n
GetVcoEndpointByManagementEndpoint returns the value of a custom property on a specied
ManagementEndpoint object. If the CustomPropertyName is not specied, the value of the
VMware.VCenterOrchestrator.EndpointName property is used.
n
GetVcoEndpointByHost returns the value of a custom property on a specied host. If the
CustomPropertyName is not specied, the value of the VMware.VCenterOrchestrator.EndpointName
property is used.
Synchronous Execution
The InvokeVcoWorkflow activity calls a vRealize Orchestrator workow and blocks further execution of its
parent IaaS workow until the vRealize Orchestrator workow completes. The activity returns the output
parameters for the vRealize Orchestrator workow.
In addition, the synchronous execution supports the following property:
n
WorkflowTimeout is a timeout value in seconds. If the vRealize Orchestrator workow does not nish in
the specied time, an exception is generated rather than blocking the workow until a response is
returned. If no value is dened or a value of zero is supplied, the timeout is not activated. The workow
status is checked every 10 seconds during that period unless the polling time is modied for the
endpoint by specifying a value in the VMware.VCenterOrchestrator.PollingInterval custom property.
Asynchronous Execution
The InvokeVcoWorkflowAsync activity is a “re and forget” activity that calls a vRealize Orchestrator
workow and continues to execute activities in the IaaS workow without waiting for the
vRealize Orchestrator workow to complete.
The activity returns either a unique workow execution token that can be used to monitor the workow or
an error if the REST API call to the vRealize Orchestrator server failed (for example, if the server could not
be reached).
Two additional activities are available for use with this activity:
n
GetVcoWorkflowExecutionStatus enables you to poll the vRealize Orchestrator workow for its status.
n
WaitForVcoWorkflowCompletion enables you to block further execution of the IaaS workow until the
vRealize Orchestrator workow has completed or timed out. You can use this activity to retrieve the
results of a vRealize Orchestrator workow that you execute asynchronously.
Chapter 1 Life Cycle Extensibility
VMware, Inc. 53