Users Guide

12. Click Add to complete creating the XaaS Blueprint.
A new XaaS Blueprint should appear on the right pane with its given name, description, and the status.
13. Select this item, and click Publish.
The XaaS Blueprint is now visible as a catalog item.
NOTE: It still has to be added to an entitled Service else, the catalog item has to be added to an entitlement
individually.
14. Select the Administration tab and click Catalog Management, then click Catalog Items from the left pane.
NOTE: The XaaS Blueprint is available here for additional configuration. Its source is set to Advanced Designer
Service where it was published.
15. Select the catalog item, and click Configure.
16. When the Configure Catalog Item page loads edit the description and upload a custom icon (optional), and select the Service
to put the catalog item in.
Now the catalog item can be used by the users but it must have the correct entitlement settings.
To make sure that the users have access to the new self-service catalog item, check if an entitlement exists for the users or the
user group. This entitlement must include the service that contains the XaaS Blueprint or the catalog item individually.
NOTE: When an user requests the service from this kind of catalog item, only the description of the request is required.
The attributes on the workflow provide the rest of the information which is required to call ASM.
Interactive Workflow as vRA XaaS Blueprints
To embed interactive workflows in vRA XaaS Blueprints, all required data must be processed as input parameters, which requires
that most of the workflow bundled with the integration cannot be populated to vRA directly. To populate the workflow to vRA, the
workflow must be modified. Consider the ASM configuration workflow and add ASM Appliance. This workflow can be encapsulated
as a vRA XaaS Blueprint without any issue as all required data are passed as input parameters. Most sample workflows contain user
interaction in their schema. This causes the workflow to pause and wait when it is called through vRA.
As example, deploy Service (Asynchronous) workflow is chosen. To convert the ASM sample workflow (Interactive workflow) to
vRA-friendly workflow, do the following:
1. Log in to vRO with privileged credential.
2. Duplicate the sample workflow into a folder where the vRA tenant has access.
3. Edit the duplicated workflow.
4. Remove all the attributes from the workflow.
5. Create input parameters for ServiceTemplate (ASM:Template type), DeploymentName (string), and DeploymentDescription
(string). There should be four input parameters in total.
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 XaaS Blueprint.
9. Go back to the vRA tenant console, create a XaaS Blueprint by choosing the modified workflow. Proceed until the new XaaS
Blueprint is added.
NOTE: The blueprint form has auto populated fields. Updating the fields is not mandatory.
10. Publish the XaaS 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 Adding a New ASM Appliance Object to 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).
26