Users Guide

6. Select the Schema tab, and remove all the design elements except for the action element,
DeployService.
7. Edit the DeployService element. Bind the local parameters and source parameters accordingly.
8. Save the workflow and close the editor mode.
NOTE: This workflow is ready to be encapsulated into a vRA Service Blueprint.
9. Go back to the vRA tenant console, create a service blueprint by choosing the modified workflow.
Proceed until the new Service Blueprint is added.
NOTE: The blueprint form has auto populated fields. Updating the fields is not mandatory.
10. Publish the Service Blueprint, and grant access to the users to this catalog item.
11. The input parameters are required to grant access to user to use the catalog items. It can only be
chosen from the vRO inventory for any ASM vRO Integration API objects, (for more information, see
the
Add ASM Appliance workflow and vRO inventory).
12. As the User Interaction elements are removed from the workflow, the vRA user has to carefully select
the ASM:Template object that is in the selected ASM:Appliance object.
NOTE: Mismatching in selection will make the ASM server to refuse the deployment.
13. Provide the service name and description to complete all the fields (Optional).
14. Click Submit.
The vRA triggers the vRO workflow to call the ASM server for a new service deployment.
Workflow Output
The ASM vRO sample workflow may have an output parameter with a custom API object type. If the vRA
needs to use the information in the output parameter, it cannot be parsed easily in the vRA layer.
Therefore, the workflow should be modified to parse the parameter into primitive data type objects
before running it (For example: Add a script action that takes the custom API object and outputs string
objects). In this way the output data can be easily used by vRA.
27