7.4
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 1‑26. (Continued)
Argument Description
-h | --humanreadable (Optional) Input file contains the virtual machine names and not
the GUIDs.
-i | - -ignore (Optional) Ignore registered or managed virtual machines.
-n | - -name Specify the name of the work queue to perform the import to the
target vRealize Automation.
- -repository (Optional) The root URI of the Model Manager, for example,
http://hostname/repository. Default is specified in the CloudUtil
config file in the repositoryAddress key under the <appSettings>
section.
-s | - -skipUser (Optional) Sets a machine's owner to the value listed in the
Owner column of the CSV data file without verifying that the
user exists. Selecting this option can decrease the time required
for import.
-t | - -time Specify the workflow start time in the format MM/DD/YYYY
hh:mm GMT, for example, 04/18/2014 10:01 GMT. The specified
start time is assumed to be the server's local time and not the
local time of the user's workstation.
-u | - -user Specify the Fabric Administrator who performs the bulk
registration.
-v | - -verbose (Optional) If an error occurs, outputs a stack trace instead of just
the exception message.
whatif (Optional) Set to validate the CSV file but do not import any
virtual machines.
vRealize Automation Workflow Activity Reference
VMware provides a library of workflow activities with vRealize Automation Designer for use in customizing
workflows.
Note The CDK is deprecated beginning with vRealize Automation 7.0. You can use the
vRealize Orchestrator workflows to address use cases that you previously addressed with CDK.
Five categories of Windows Workflow Foundation activities are also included in vRealize Automation
Designer, including Control Flow, Flowchart, Primitives, Collection and Error Handling.
This section provides a reference to the IaaS workflow activities included with vRealize Automation
Designer in the DynamicOps.Repository.Activities and DynamicOps.Cdk.Activities
namespaces. Activities related to calling vRealize Orchestrator workflows are described in Using vRealize
Orchestrator Workflow Activities.
Note In the IaaS activity library, the Model Manager is referred to as the repository.
Life Cycle Extensibility
VMware, Inc. 84