7.3

Table Of Contents
Table 117. Extending Machine Lifecycles By Using vRealize Automation Designer Checklist (Continued)
Task Details
Using vRealize Automation Designer
activities, customize an IaaS Workow stub.
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.
Optionally, you can use vRealize Orchestrator
workow activities to call out to custom
vRealize Orchestrator workows.
“Customize an IaaS Workow,” on page 52
After you create a custom state change
workow, a tenant administrator or business
group manager must enable it for specic
blueprints by adding a custom property.
“Congure a Blueprint to Call a State Change Workow,” on
page 57
Installing and Configuring vRealize Automation Designer
You can install vRealize Automation Designer on a Windows machine and congure it to communicate with
a remote Model Manager instance. If you are using IaaS workows to call vRealize Orchestrator workows,
you must also congure the vRealize Orchestrator instance in IaaS.
Installing vRealize Automation Designer
You can install vRealize Automation Designer on a Windows machine and congure it to communicate with
a remote Model Manager instance.
vRealize Automation Designer Prerequisites
vRealize Automation Designer is typically installed on a development machine rather than a server.
Supported Operating Systems
Supported operating systems for vRealize Automation Designer are listed in the vRealize Automation Support
Matrix on the VMware vRealize Automation Documentation page.
System Configuration Requirements
See the vRealize Automation Support Matrix for your vRealize Automation version for potential updates to
this information.
n
.NET Framework 4.5 must be installed.
n
The vRealize Automation Designer host must have network access to the IaaS Website components
(specically, the Model Manager Web component).
n
If the Model Manager is installed remotely, the certicate used for the Model Manager Web component
must be trusted on the vRealize Automation Designer host.
Chapter 1 Life Cycle Extensibility
VMware, Inc. 45