Deployment Guide

7. Click the Add button on the right pane to add a new service blueprint.
8. First select the Deploy Service workflow that was modified earlier in vRO.
9. Click the Next button.
10. Edit the details as needed, then proceed.
NOTE: A blueprint form is not required for a non-interactive workflow.
11. Click Next, and make sure no resource is provisioned after running the workflow.
12. Click Add button to complete creating the service blueprint.
A new service blueprint should appear on the right pane with its given name, description, and the
current status.
13. Select this item, and click the Publish button.
The service 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 the Catalog Items from the
left pane.
NOTE: The Service Blueprint is available here for additional configuration. At this point, 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 end users but it must have the correct entitlement settings.
To make sure that the end 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 service
blueprint or the catalog item individually.
NOTE: When an end 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 Service Blueprints
To embed interactive workflows in vRA Service Blueprints, all required data must be processed as input
parameters. It means the most of the workflow bundled with the integration cannot be populated to vRA.
To populate the workflow to vRA, workflow must be modified. Consider the ASM configuration workflow
and add ASM Appliance. This workflow can be encapsulated as a vRA Service Blueprint without any issue
as all required data are passed as input parameters. Most sample workflow contain user interaction in
their schema. This will cause the workflow to pause and wait when it is called through vRA.
As example, deploy Service (Asynchronous) workflow is chosen. The following instruction describes how
to convert the ASM sample workflow (Interactive workflow) to vRA-friendly workflow:
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 new 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.
25