7.4

Table Of Contents
2 Click Blueprints.
3 Point to the blueprint to publish and click Publish.
4 Click OK.
The blueprint is published as a catalog item but you must first entitle it to make it available to users in the
service catalog.
What to do next
Add the blueprint to the catalog service and entitle users to request the catalog item for machine
provisioning as defined in the blueprint.
Working with Blueprints Programmatically
In addition to the user interface-driven method of creating vRealize Automation blueprints, you can also
work programmatically using tools such as vRealize CloudClient, with standalone supplied or otherwise
sourced blueprints, and in concert with other developers by using workflows, including
vRealize Orchestrator workflows, and third-party tools.
For information about these methods, see the following topics:
n
Exporting and Importing Blueprints and Content
n
Downloading and Configuring the Supplied Standalone Blueprint
Exporting and Importing Blueprints and Content
You can programmatically export blueprints and 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 can import a property definition from a community forum into
your active vRealize Automation tenant instance.
You can programmatically import and export any of the following vRealize Automation content items:
n
Application blueprints and all their components
n
IaaS machine blueprints
n
Software components
n
XaaS blueprints
n
Component profiles
n
Property groups
Property group information is tenant-specific and is only imported with the blueprint if the property
group already exists in the target vRealize Automation instance.
Configuring vRealize Automation
VMware, Inc. 507