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

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 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 machines such as name, description, and so on.

vRealize Automation includes vRealize Orchestrator resource mapping script actions and resource mapping workflows 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. Workflows for the provided resource mappings are located in the vRealize Automation > XaaS > Resource Mappings workflows folder of the embedded vRealize Orchestrator server.

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