7.0
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
7 Specify the Model Manager service user credentials.
8 Click Next.
The installer validates the combination of Model Manager host and credentials by attempting to
access to the Model Manager. If an error is returned, you must provide the correct combination of
Model Manager host and credentials before proceeding.
9 Click Install.
10 Click Finish.
What to do next
You can launch the vRealize Automation Designer from the Windows Start menu by navigating to the
installation directory.
Configuring vRealize Orchestrator Endpoints
If you are using vRealize Automation workflows to call vRealize Orchestrator workflows, you must
configure 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 workflows 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
workflows 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 workflows to execute vRealize Orchestrator workflows that have
input or output parameters of type VC:VirtualMachine, verify that you have the vRealize Orchestrator
workflows for converting virtual machine types between vRealize Orchestrator and IaaS.
The required workflows are included by default in vRealize Orchestrator 5.5 and later as part of the
vCenter plugin.
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
http://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 configure multiple endpoints to connect to different vRealize Orchestrator servers, but you must
configure a priority for each endpoint.
Life Cycle Extensibility
VMware, Inc. 59