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‑10. Details Tab Options
Options Descriptions
Name By default, the displayed name is the name of the selected
workow.
This name is displayed in the subscription list. The name
must be unique in the tenant.
Priority The order in which the blocking subscriptions run.
Zero is the highest priority. If an event topic has multiple
blocking workow subscriptions with the same priority,
the subscriptions are then processed in alphabetical order
based on the subscription name.
This option is only available for blocking workow
subscriptions.
Timeout (min) Specify the number of minutes the workow has to nish
before it is considered failed.
If the workow fails to nish in the specied amount of
time, the workow is canceled and the message is sent to
the next subscription in the priority list.
If you do not provide a value, the timeout is unlimited.
Services that expect a reply, to blocking or replyable events,
might have their own default timeout values. For example,
IaaS provisioning and life cycle event topics time out at 30
minutes. This value is congured on the IaaS server.
Approval topics have a 24 hour default value. This value is
congured on the system.
Description By default, the displayed description is the workow
description.
Blocking Determines if the workow can block subsequent
workows for the same event topic from receiving an event
message while waiting for a reply.
Subscriptions with blocking enabled receive messages
before subscriptions that are not congured as blocking for
the same event topic, based on priority order. When the
workow is nished, a message is sent to the next
prioritized blocking subscription. After all blocking
subscriptions have processed, the message is sent to all
non-blocking subscriptions simultaneously.
The blocking option is available only if the event topic is
blockable. This information is provided on the Event Topic
tab.
The blocking eligibility is indicated on the Event Topic tab.
n
If you do not select the check box, the event broker
does not block subsequent workows.
n
If you select check box, the event broker calculates
which workow subscriptions are eligible for this
event based on the congured conditions and runs the
workows in priority order. The event broker waits for
a response from each workow before running the next
one. All the changed parameters from the running of
the current workow are passed to the next one in the
queue.
While waiting for a response, no other workows are
notied of the event until the consuming system
responds.
You cannot modify this option after the workow
subscription is published.
Life Cycle Extensibility
20 VMware, Inc.