7.4

Table Of Contents
Extending Machine Lifecycles By Using
vRealize Orchestrator
You can inject custom logic into predetermined stages of the IaaS machine lifecycle by creating custom
vRealize Orchestrator workflows and then using vRealize Orchestrator to insert the custom workflows into
the lifecycle of machines built from specific blueprints.
Extending Machine Lifecycles by Using vRealize Orchestrator
Checklist
The extending machine lifecycles by using vRealize Orchestrator checklist provides a high-level overview
of the steps required to install and configure vRealize Orchestrator to customize IaaS machine lifecycles.
Table 13. Extending Machine Lifecycles by Using vRealize Orchestrator Checklist
Task Details
Configure a vRealize Automation host for your
vRealize Orchestrator.
Add a vRealize Automation Host
Configure an IaaS host for your
vRealize Orchestrator.
Add an IaaS Host
Install the vRealize Orchestrator customizations for
extending IaaS machine lifecycles.
Install vRealize Orchestrator Customization
Create a vRealize Automation endpoint for your
vRealize Orchestrator instance.
Create a vRealize Orchestrator Endpoint
Use the workflow template provided in the
Extensibility subdirectory of the vRealize Automation
plug-in library to create a custom
vRealize Orchestrator workflow to run during the
machine lifecycle. You can run multiple workflows in
the same state for the same blueprint as long as you
nest them under a single wrapper workflow.
For information about developing workflows with vRealize Orchestrator,
see the vRealize Orchestrator documentation. For training in
vRealize Orchestrator development for vRealize Automation integrations,
see the training courses available from VMware Education and the
instructional material provided by VMware Learning.
Run the provided workflow that inserts your custom
workflow into an IaaS workflow stub and configures a
blueprint to call the IaaS workflow stub.
Note The workflow stubs are replaced by the event
broker workflow subscriptions. They are still available,
supported, and they can be used, but expect them to
be removed in a future version of
vRealize Automation. To ensure future product
compatibility, you should use the workflow
subscriptions to run custom workflows based on state
changes. See Configuring Workflow Subscriptions to
Extend vRealize Automation.
Assign a State Change Workflow to a Blueprint and Its Virtual Machines
Life Cycle Extensibility
VMware, Inc. 7