7.3
Table Of Contents
- Life Cycle Extensibility
- Contents
- Life Cycle Extensibility
- Machine Extensibility Overview
- Extending Machine Lifecycles By Using vRealize Orchestrator
- Configuring Workflow Subscriptions to Extend vRealize Automation
- Event Topics Provided With vRealize Automation
- Workflow Subscriptions and Event Broker Terminology
- Blockable and Replyable Event Topics
- Best Practices for Creating vRealize Orchestrator Workflows for Workflow Subscriptions
- Workflow Subscription Settings
- Working with Provisioning and Life Cycle Workflow Subscriptions
- Configuring vRealize Orchestrator Workflows for Provisioning and Life Cycle Workflows
- Workflow Subscription Life Cycle State Definitions
- Configuring the Timeout Values for States and Events
- Configuring the Error Behavior for States and Events
- Scenario: Take a Post-Provisioning Snapshot of a Virtual Machine
- Working with Approval Workflow Subscriptions
- Troubleshooting Workflow Subscriptions
- Troubleshooting vRealize Orchestrator Workflows That Do Not Start
- Troubleshooting Provisioning Requests That Take Too Much Time
- Troubleshooting a vRealize Orchestrator Workflow That Does Not Run for an Approval Request
- Troubleshooting a Rejected Approval Request That Should Be Approved
- Troubleshooting a Rejected Approval Request
- Extending Machine Life Cycles By Using vRealize Automation Designer
- Extending Machine Life Cycles By Using vRealize Automation Designer Checklist
- Installing and Configuring vRealize Automation Designer
- Customizing IaaS Workflows By Using vRealize Automation Designer
- Workflows and Distributed Execution Management
- CloudUtil Command Reference
- vRealize Automation Workflow Activity Reference
- Index
Configuring vRealize Orchestrator Endpoints
If you are using vRealize Automation workows to call vRealize Orchestrator workows, you must
congure the vRealize Orchestrator instance or server as an endpoint.
You can associate a vRealize Orchestrator endpoint with a machine blueprint to make sure that all of the
vRealize Orchestrator workows for machines provisioned from that blueprint are run using that endpoint.
vRealize Automation by default includes an embedded vRealize Orchestrator instance. It is recommended
that you use this as your vRealize Orchestrator endpoint for running vRealize Automation workows in a
test environment or creating a proof of concept.
You can also install a plug-in on an external vRealize Orchestrator server.
vCenter Orchestrator Integration Prerequisites
If you are using vRealize Automation workows to execute vRealize Orchestrator workows that have
input or output parameters of type VC:VirtualMachine, verify that you have the vRealize Orchestrator
workows for converting virtual machine types between vRealize Orchestrator and IaaS.
The required workows are included by default in vRealize Orchestrator 5.5 and later as part of the vCenter
plug-in.
If you are using vRealize Orchestrator 5.1, install the vRealize Automation integration package for
vRealize Orchestrator. Download the package com.vmware.library.vcenter.vcac-integration.package
from thevRealize Orchestrator community site at
hp://communities.vmware.com/community/vmtn/server/vcenter/orchestrator. Import the package on each
vRealize Orchestrator server that you set up as an endpoint in IaaS.
For information about importing packages to vRealize Orchestrator, refer to the vRealize Orchestrator
documentation.
Create a vRealize Orchestrator Endpoint
You can create a vRealize Orchestrator endpoint to connect to a vRealize Orchestrator server.
You can congure multiple endpoints to connect to dierent vRealize Orchestrator servers, but you must
congure a priority for each endpoint.
When executing vRealize Orchestrator workows, vRealize Automation tries the highest priority
vRealize Orchestrator endpoint rst. If that endpoint is not reachable, then it proceeds to try the next highest
priority endpoint until a vRealize Orchestrator server is available to run the workow.
Prerequisites
n
Log in to the vRealize Automation console as an IaaS administrator.
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 qualied 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 specied, 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.
Chapter 1 Life Cycle Extensibility
VMware, Inc. 47