An XaaS blueprint is a specification to run a vRealize Orchestrator workflow that makes a change to a target system in your environment. The blueprint includes the workflow, and it can include the input parameters, submission and read-only forms, sequence of actions, and the provisioning or non-provisioning operation.
You can create XaaS blueprints that you use in one or more of the following ways:
Create an XaaS blueprint component. A component blueprint is a provisioning or non-provisioning blueprint that you can use in the blueprint design canvas as part of a composite blueprint. If you are using it as a component, you must configure the component life cycle options that support scale-in and scale-out operations on the deployed composite blueprint.
This blueprint type might also be published as a standalone blueprint.
Create a standalone XaaS blueprint. A standalone blueprint is a provisioning or non-provisioning blueprint that is published and entitled directly to the service catalog.
For an example of how to create Active Directory users using an XaaS blueprint, see Create an XaaS Blueprint and Action for Creating and Modifying a User.
Log in to vRealize Automation as an XaaS architect.
If the blueprint must provision resources, create a custom resource corresponding to the output parameter of the service blueprint. See Add an XaaS Custom Resource. If it does not use a vRealize Orchestrator plug-in API, you do not need to configure a custom resource.
By creating an XaaS blueprint, you publish a vRealize Orchestrator workflow as a potential component blueprint or catalog item. The blueprint includes a form that you might edit. See Designing an XaaS Blueprint Form.
Use the detailed options information to configure the blueprint. See XaaS Blueprint New or Edit Wizard Options.
- Select .
- Click the New icon ().
- On the Workflow tab, select the workflow that runs when the blueprint provisions the resource.
This tab is not available if you are editing a blueprint.
- Navigate through the vRealize Orchestrator workflow library and select a workflow relevant to your custom resource.
- Review the input and output parameters to ensure that you can later provide the correct values.
- Click Next.
- On the General tab, configure the options and click Next.
- In the Name text box, enter a name that differentiates this blueprint from similar blueprints.
- If you do not want to use this blueprint as a component in a composite blueprint, deselect the Make available as a component in the design canvas check box.
- On the Blueprint Form tab, edit the form as needed and click Next.
- On the Provisioned Resource page, select a value and click Next.
If the workflow does not provision resources, you can select this option or leave the field empty.
<A custom resource that you previously created>
Select the custom resource that supports this provisioning workflow.
- On the Component Lifecycle tab, define how this blueprint behaves during scale-in, scale-out, and destroy operations.
These workflows run on a deployed composite blueprint where this blueprint is a component. The availability of the different options depends on blueprint. Not all blueprint workflows support or require all the options.
- Click Finish.
- Select the row for you blueprint and click Publish.
You created and published an XaaS blueprint.