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
Table 1‑7. Event Topic Options (Continued)
Option Description
Blockable Indicates whether you can create a blocking subscription
for this event topic.
Blocking subscriptions are used to change the event's
payload or to synchonously run your custom logic when
the results of a second workow for the same event depend
on the results of the rst workow.
Replyable Indicates whether an event topic subscription can publish a
reply event to the service that originally produced the
event. If the value is yes, a reply is sent to the service that
published the original event when the workow nishes.
The reply contains the output of the vRealize Orchestrator
workow and any error details.
Schema Describes the structure of the event's payload.
You can use the schema to create workows that can use
the payload information.
Workflow Subscription Conditions Tab Settings
The conditions you congure for the subscription determine whether the workow is triggered to run based
on the event data.
If you select Run based on conditions, the available options can include:
n
Data. Information in the event message that is specic to the selected event topic. For example, if you
create a condition for the machine life cycle event topic, the data elds are related to blueprints and
machines. If you select a pre-approval event topic, the data elds are related to approval policies.
You can also add conditions for elds that are not included in the schema by entering the path in the
text box above the tree. Use the format ${PATH}. PATH is the path in the schema. Separate the nodes
using ~. For example, ${data~machine~properties~SomeCustomProperty}.
n
Core event message values. General information about the event message. For example, the event type,
time stamp, or user name.
To select an event topic for your workow subscriptions, select Administration > Events > Subscriptions.
Click New.
Life Cycle Extensibility
18 VMware, Inc.