7.0

Table Of Contents
XaaS Blueprints
You can publish your vRealize Orchestrator workflows as XaaS blueprints. For example, you can create a
custom resource for Active Directory users, and design an XaaS blueprint to allow managers to provision
new users in their Active Directory group. You create and manage XaaS components outside of the
design tab. You can reuse published XaaS blueprints to create application blueprints, but only in
combination with at least one machine component.
Application Blueprints with Multi-Machine, XaaS , and Software
Components.
You can add any number of machine components, Software components, and XaaS blueprints to a
machine blueprint to deliver elaborate functionality to your users. For example, you can create a blueprint
for managers to provision a new hire setup. You can combine multiple machine components, software
components, and a XaaS blueprint for provisioning new Active Directory users. The QE Manager can
request your New Hire catalog item, and their new quality engineering employee is provisioned in Active
Directory and given two working virtual machines, one Windows and one Linux, each with all the required
software for running test cases in these environments.
Exporting and Importing Blueprints
You can programmatically export content from one vRealize Automation environment to another by using
the vRealize Automation REST API or by using the vRealize CloudClient.
For example, you can create and test your blueprints in a development environment and then import them
into your production environment, or you could import a property definition from a community forum. You
can programmatically import and export any of the following vRealize Automation content:
n
Application blueprints and all their components
n
IaaS machine blueprints
n
Software components
n
XaaS blueprints
n
Property definitions
n
Property groups
Configuring vRealize Automation
VMware, Inc. 255