7.2

Resource Mappings
You create resource mappings between the vRealize Automation catalog resource type and the
vRealize Orchestrator inventory type to manage resources provisioned outside of XaaS.
For example, you might want to create an action so that users can take a snapshot of their Amazon
machines. For this action to work on an Amazon machine provisioned, the three components involved,
XaaS, vRealize Orchestrator, and IaaS, need a common language You create that common language by
adding a resource mapping in XaaS that runs a vRealize Orchestrator scripting action or workow to map
the IaaS Cloud Machine resource type to the vRealize Orchestrator AWS:EC2Instance inventory type.
vRealize Automation provides resource mappings, and the underlying vRealize Orchestrator script actions
and workows, for vSphere, vCloud Director, and vCloud Air machines.
XaaS Blueprints
An XaaS blueprint is a complete specication of a resource.
With XaaS blueprints, you publish predened and custom vRealize Orchestrator workows as catalog items
for either requesting or provisioning. Blueprints for requesting run workows with no provisioning and
provide no options for managing a provisioned item. Before you create a blueprint for provisioning, you
must map the workow output parameter as a custom resource. Then you can assign resource actions that
dene post-provisioning operations.
Resource Actions
You can create custom resource actions to congure the post-provisioning operations that the consumers can
perform.
To create post-provisioning operations, you must publish vRealize Orchestrator workows as resource
actions. To create a resource action for an item provisioned by using XaaS, you use a custom resource as an
input parameter for the workow. To create a resource action for an item that is provisioned by a source
dierent from XaaS, you use a resource mapping as an input parameter for the workow. When you entitle
the resource actions, they appear in the Actions drop-down menu of the provisioned items on the Items tab.
Designing Forms for XaaS Blueprints and Actions
The XaaS includes a form designer that you can use to design submission and details forms for blueprints
and resources actions. Based on the presentation of the workows, the form designer dynamically generates
default forms and elds you can use to modify the default forms.
You can create interactive forms that the users can complete for submission of catalog items and resource
actions. You can also create read-only forms that dene what information the users can see on the details
view for a catalog item or a provisioned resource.
As you create XaaS custom resources, XaaS blueprints, and resource actions, forms are generated for
common use cases.
Foundations and Concepts
VMware, Inc. 35