You can use the provided resource mappings for vSphere, vCloud Director, or vCloud Air virtual machines or you can create custom vRealize Orchestrator script actions or workflows to map other vRealize Automation catalog resource types to vRealize Orchestrator inventory types.

Resource Mappings Provided With vRealize Automation

vRealize Automation includes resource mappings for IaaS vSphere virtual machines, IaaS vCloud Director, and deployments.

vRealize Automation includes vRealize Orchestrator resource mapping script actions for each of the provided XaaS resource mappings. Script actions for the provided resource mappings are located in the com.vmware.vcac.asd.mappings package of the embedded vRealize Orchestrator server.

When you create a resource action that runs on a deployed composite blueprint that uses a vRealize Orchestrator workflow with vCACAFE:CatalogResource as an input parameter, the Deployment mapping is applied as the input resource type. The Deployment mapping is applied only if the selected workflow includes vCACAFE:CatalogResource as an input parameter. For example, if you create an action to request a resource action on behalf of a user, the resource type on the Input Resource tab is Deployment because this workflow uses vCACAFE:CatalogResource.

The IaaS vCD VM and IaaS VC VirtualMachine resource mappings are used by an action to map the virtual machines that match the IaaS resource to the vRealize Orchestrator vSphere or vCloud Director virtual machine.

Developing Resource Mappings

Depending on your version of vRealize Orchestrator, you can create either a vRealize Orchestrator workflow or a script action to map resources between vRealize Orchestrator and vRealize Automation.

To develop the resource mapping, you use an input parameter of type Properties, which contains a key-value pair defining the provisioned resource, and an output parameter of a vRealize Orchestrator inventory type expected by the corresponding vRealize Orchestrator plug-in. The properties available for the mapping depend on the type of resource. For example, the EXTERNAL_REFERENCE_ID property is a common key parameter that defines individual virtual machines, and you can use this property to query a catalog resource. If you are creating a mapping for a resource that does not use an EXTERNAL_REFERENCE_ID, you can use one of the other properties that are passed for the individual virtual machines. For example, name, description, and so on.

For more information about developing workflows and script actions, see Developing with VMware vCenter Orchestrator.