7.1
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
Table 5‑1. Extending Machine Lifecycles By Using vRealize Automation Designer Checklist
(Continued)
Task Details
Using vRealize Automation Designer activities,
customize an IaaS Workflow stub.
Note The workflow stubs are 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 4 Configuring Workflow
Subscriptions to Extend vRealize Automation.
Optionally, you can use vRealize Orchestrator
workflow activities to call out to custom
vRealize Orchestrator workflows.
Customize an IaaS Workflow
After you create a custom state change workflow, a
tenant administrator or business group manager must
enable it for specific blueprints by adding a custom
property.
Configure a Blueprint to Call a State Change Workflow
Installing and Configuring vRealize Automation Designer
You can install vRealize Automation Designer on a Windows machine and configure it to communicate
with a remote Model Manager instance. If you are using IaaS workflows to call vRealize Orchestrator
workflows, you must also configure the vRealize Orchestrator instance in IaaS.
Installing vRealize Automation Designer
You can install vRealize Automation Designer on a Windows machine and configure 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.
Life Cycle Extensibility
VMware, Inc. 57