7.2
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
2 Run the CloudUtil.exe command with the following arguments.
n
CloudUtil.exe Operation-Create -c <path to operation definition file>
n
Optionally, you can specify a Model Manager host and request a stack trace in case of error.
CloudUtil.exe Operation-Create -c <path to operation definition file>
--repository <Model Manager Root URI> -v
What to do next
If the menu operation is intended to be used in the service catalog, it must be registered with the service
catalog so that it can be entitled to users. Register New Menu Operations with the Service Catalog.
Register New Menu Operations with the Service Catalog
After installing new menu operations, the workflow developer must register them with the service catalog
so they can be entitled to users.
Prerequisites
n
Configure a Menu Operation.
n
Log in to the IaaS Model Manager host as a local user with administrator privileges.
Procedure
1 Open an elevated command prompt.
2 Navigate to the IaaS root installation directory.
In a typical installation, this is C:\Program Files (x86)\VMware\vCAC.
3 Navigate to Server\Model Manager Data\Cafe.
4 Execute the following command:
Vcac-Config.exe RegisterCatalogTypes -v
What to do next
A tenant administrator or business group manager must entitle the new action before it is available to
users in the service catalog. For more information, see Tenant Administration.
Configure a Blueprint to Enable a Menu Operation Workflow
You enable a menu operation workflow for machines provisioned from a specific blueprint by updating the
security configuration for the blueprint.
Prerequisites
Log in to the vRealize Automation console as a tenant administrator or business group manager.
Life Cycle Extensibility
VMware, Inc. 75