7.0
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
Table 4‑3. vRealize Orchestrator and IaaS Object Types (Continued)
vRealize Orchestrator Type IaaS Type
Date DateTime
VC:VirtualMachine VirtualMachine
Note If you are using vRealize Orchestrator 5.1, you must have installed the vRealize Automation
integration package to enable the conversion of VC:VirtualMachine object types to VirtualMachine.
All other vRealize Orchestrator types are converted to the IaaS type VcoSdkObject.
Configure a Blueprint to Call a State Change Workflow
After you create a custom state change workflow, a tenant administrator or business group manager must
enable it for specific blueprints by adding a custom property.
Each state change workflow is associated with a specific custom property. When a machine is entering a
state with a corresponding state change workflow, IaaS checks to see if the machine has the
corresponding custom property; if so, the associated workflow is executed. For example, if a machine has
the custom property ExternalWFStubs.MachineProvisioned, the WFStubMachineProvisioned
workflow is executed before the master workflow enters the MachineProvisioned state.
While custom properties can be applied to a machine from a number of sources, typically the property for
a state change workflow is specified in a blueprint, enabling the workflow for all machines provisioned
from that blueprint.
Prerequisites
Log in to the vRealize Automation console as a tenant administrator or business group manager.
Procedure
1 Select Design > Blueprints.
2 Point to the name of a blueprint and click Edit.
3 Click the Properties tab.
4 Click New Property.
5 Type the name of the custom property associated with the workflow you want to enable in the Name
text box.
Customizable Workflow Name Associated Property Name
WFStubMachineProvisioned ExternalWFStubs.MachineProvisioned
WFStubBuildingMachine ExternalWFStubs.BuildingMachine
WFStubMachineDisposing ExternalWFStubs.MachineDisposing
WFStubUnprovisionMachine ExternalWFStubs.UnprovisionMachine
WFStubMachineRegistered ExternalWFStubs.MachineRegistered
WFStubMachineExpired ExternalWFStubs.MachineExpired
Life Cycle Extensibility
VMware, Inc. 71