Users Guide

9
Workow and Actions
The Dell ASM vRO Integration is prepackaged with a set of sample workows and actions. These can be used as out of the box to
immediately enable common use cases. They may also be used to serve as examples that can be extended by advanced users.
Underlying actions and API’s are updated, but the workows provide the same user experience as with versions 1.0 and 1.1.
Workow
The prepackaged ASM vRO Integration workow is divided into two types:
Conguration workow — These can be used to store and remove ASM appliance congurations within vRO. Appliances can
be viewed in the Inventory panel once it is stored.
Sample workow — These samples illustrate the various capabilities of the integration. They are designed to allow users to
immediately begin testing the integration between vRO and their ASM appliance. These samples can also be used by advanced
users to develop or modify workows.
Conguration Workows
Add ASM Appliance:
This workow asks the user to provide various conguration parameters for the ASM appliance and subsequently persists the
conguration as a vRO resource. Once this workow has been run successfully, the appliance appears in the inventory and can be
selected as an input for any of the other sample workows.
Remove ASM Appliance:
This workow removes the selected appliance from the inventory.
Sample Workows
The sample workow is divided into four categories:
AsynchronousWorkows are designed to make API calls without waiting for the completion of the corresponding operations.
The immediate result of the API calls is reported.
Non-interactiveWorkows that are designed to run without any user inputs fall under this category. These workows are
examples for vRA integration or other automation purposes.
Synchronous — The synchronous workows make use of the asynchronous counterparts but include polling functionality to
defer completion and status update until the corresponding operation either succeeds or fails on the ASM appliance.
XaaS — These workows are designed specically to help with the vRA integration. The XaaS workows are based on the
synchronous workows and report the result after the ASM server completes handling the task; unless the API call fails
immediately. In addition, the user inputs are submitted at the beginning of the run to allow simple importation of the workows
into vRA as XaaS Blueprints.
NOTE: On applications with plugin 2.0.1, new workows under XaaS folder are bundled in addition to preexisting
workows from version 2.0.0.
Asynchronous
Deploy service
20