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
Argument Description
- -repository (Optional) The root URI of the Model Manager, for example, hp://hostname/repository.
Default is specied in the CloudUtil cong le in the repositoryAddress key under the
<appSeings> section.
-v | - -verbose (Optional) If an error occurs, outputs a stack trace instead of just the exception message.
File-Rollback
Reverts a le in the Model Manager to a specied revision.
Synopsis
CloudUtil.exe File-Rollback -n|--name <Name> -r|--revision <Revision> [-i|--iteration
<Iteration>] [--repository <Model Manager Root URI>] [-v|--verbose]
File-Rollback Arguments
Table 1‑21.
Argument Description
-i | - -iteration
(Optional) Version string of the le in the Model Manager. Default is 0.0.
-n | - -name Friendly name of the le in the Model Manager.
-r | - -revision Revision of the le to revert to.
- -repository (Optional) The root URI of the Model Manager, for example, hp://hostname/repository.
Default is specied in the CloudUtil cong le in the repositoryAddress key under the
<appSeings> section.
-v | - -verbose (Optional) If an error occurs, outputs a stack trace instead of just the exception message.
File-Update
Updates a previously imported le in the Model Manager with a new revision.
Synopsis
CloudUtil.exe File-Update -n|--name <Name> -f|--filename <File Name> [-i|--iteration
<Iteration>] [--repository <Model Manager Root URI>] [-v|--verbose]
File-Update Arguments
Argument Description
-f | - -lename Path to the updated le.
-i | - -iteration
(Optional) Version string of the le in the Model Manager. Default is 0.0.
-n | - -name Friendly name of the le in the Model Manager.
- -repository (Optional) The root URI of the Model Manager, for example, hp://hostname/repository.
Default is specied in the CloudUtil cong le in the repositoryAddress key under the
<appSeings> section.
-v | - -verbose (Optional) If an error occurs, outputs a stack trace instead of just the exception message.
Operation Commands
The Operation commands enable you to manage custom operations in the Model Manager.
Chapter 1 Life Cycle Extensibility
VMware, Inc. 67