7.3

Cause
One possible cause is an internal error when vRealize Orchestrator tried to run the workow. For example,
the workow is missing or the vRealize Orchestrator server is not running.
Solution
1 Select Administration > Events > Event Logs.
2 Review the logs for messages related to approvals.
Extending Machine Life Cycles By Using vRealize Automation
Designer
You can inject custom logic into predetermined stages of the IaaS machine life cycle by using vRealize
Automation Designer to directly edit the state change workow stubs and, optionally, call out to custom
vRealize Orchestrator workows.
N The workow stubs are replaced by the event broker workow 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 workow subscriptions to run custom
workows based on state changes. See “Conguring Workow Subscriptions to Extend vRealize
Automation,” on page 12.
Extending Machine Life Cycles By Using vRealize Automation Designer
Checklist
The Extending Machine Life Cycles By Using vRealize Automation Designer Checklist provides a high-level
overview of the steps required to install and congure vRealize Automation Designer to customize IaaS
machine life cycles.
Table 1‑17. Extending Machine Lifecycles By Using vRealize Automation Designer Checklist
Task Details
Download and install vRealize Automation
Designer.
“Installing vRealize Automation Designer,” on page 45
Create a vRealize Automation endpoint for
your vRealize Orchestrator instance.
“Create a vRealize Orchestrator Endpoint,” on page 47
Associate your vRealize Orchestrator endpoint
with a machine blueprint.
“Associate a vRealize Orchestrator Endpoint with a Blueprint,” on
page 48
Life Cycle Extensibility
44 VMware, Inc.