7.3

Procedure
1 Select Infrastructure > Endpoints > Endpoints.
2 Select New > Orchestration > vRealize Orchestrator.
3 Enter a name and, optionally, a description.
4 Enter a URL with the fully qualied 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 specied, 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 Provide your vRealize Orchestrator credentials in the User name and Password text boxes to connect to
the vRealize Orchestrator endpoint.
The credentials you use should have Execute permissions for any vRealize Orchestrator workows to
call from IaaS.
To use the default vRealize Orchestrator instance embedded in the vRealize Automation appliance, the
user name is [e-mail] and the password is the administrator password that was
specied when conguring SSO.
6 Enter an integer greater than or equal to 1 in Priority text box.
A lower value species a higher priority.
7 (Optional) Click Properties and add supplied custom properties, property groups, or your own
property denitions for the endpoint.
8 Click OK.
Customizing IaaS Workflows By Using vRealize Orchestrator
You use a single workow in vRealize Orchestrator to inject your custom logic into the IaaS workow stubs
and assign your customized life cycles to machine blueprints.
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.
You must design your custom vRealize Orchestrator workows to accept string inputs. If your custom
workow expects a complex data type, create a wrapper workow that looks up this complex value and
translates it to a string. For an example wrapping workow, see the sample Workow template, provided in
Library > vRealize Automation > Infrastructure > Extensibility.
Assign a State Change Workflow to a Blueprint and Its Virtual Machines
You congure custom vRealize Orchestrator workows to run at specic stages in the master machine
workow by associating your custom workow with a state change workow stub and assigning the
workows to a blueprint.
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.
Chapter 1 Life Cycle Extensibility
VMware, Inc. 11