7.0

3 Enter a name and, optionally, a description.
4 Type a URL with the fully qualified name or IP address of the vRealize Orchestrator server and the
vRealize Orchestrator port number.
The transport protocol must be HTTPS. If no port is specified, the default port 443 is used.
To use the default vRealize Orchestrator instance embedded in the vRealize Automation appliance,
type https://vrealize-automation-appliance-hostname:443/vco.
5 Specify the endpoint priority.
a Click New Property.
b Type VMware.VCenterOrchestrator.Priority in the Name text box.
The property name is case sensitive.
c Type an integer greater than or equal to 1 in the Value text box.
Lower value means higher priority.
d
Click the Save icon ( ).
6 Click OK.
Customizing IaaS Workflows By Using
vRealize Orchestrator
You use a single workflow in vRealize Orchestrator to inject your custom logic into the IaaS workflow
stubs and assign your customized life cycles to machine blueprints.
Note The workflow stubs are being 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 Chapter 3 Configuring Workflow Subscriptions to
Extend vRealize Automation.
You must design your custom vRealize Orchestrator workflows to accept string inputs. If your custom
workflow expects a complex data type, create a wrapper workflow that looks up this complex value and
translates it to a string. For an example wrapping workflow, see the sample Workflow template, provided
in Library > vRealize Automation > Infrastructure > Extensibility.
Life Cycle Extensibility
VMware, Inc. 17