7.2

Standardization in Software
With Software, you can create reusable services using standardized conguration properties to meet strict
requirements for IT compliance. Software includes the following standardized conguration properties:
n
Model-driven architecture that enables adding IT certied machine blueprints and middleware services
within the application blueprint.
n
A delegation model for overriding conguration name value pairs between software architect,
application architect, and end user to standardize conguration values for application and middleware
service.
Software Extensibility and Open Architecture
You can download predened Software components for a variety of middleware services and applications
from the VMware Solution Exchange. Using either the vRealize CloudClient or vRealize Automation REST
API , you can programmatically import predened Software components into your vRealize Automation
instance.
n
To visit the VMware Solution Exchange, see
hps://solutionexchange.vmware.com/store/category_groups/cloud-management.
n
For information about vRealize Automation REST API, see Programming Guide and vRealize Automation
API Reference.
n
For information about vRealize CloudClient, see hps://developercenter.vmware.com/tool/cloudclient.
XaaS Overview
With the XaaS, XaaS architects can create XaaS blueprints and resource action, and publish them as catalog
items.
With XaaS, you can provide anything as a service using the capabilities of
VMware vRealize ™ Orchestrator ™. For example, you can create a blueprint that allows a user to request a
backup of a database. After completing and submiing a backup request, the user receives a backup le of
the database they specied.
An XaaS architect can create custom resource types mapped to vRealize Orchestrator object types and dene
them as items to be provisioned. A XaaS architect can then create blueprints from vRealize Orchestrator
workows and publish the blueprints as catalog items. The vRealize Orchestrator workows can be either
predened or independently developed by workow developers.
You can also use the XaaS to design additional actions that the consumer can perform on the provisioned
items. These additional actions are connected to vRealize Orchestrator workows and take the provisioned
item as input to the workow. To use this function for items provisioned by sources other than the XaaS, you
must create resource mappings to dene their resource types in vRealize Orchestrator.
For more information about vRealize Orchestrator and its capabilities, see the vRealize Orchestrator
documentation.
Service Catalog Overview
The service catalog provides a unied self-service portal for consuming IT services. Users can browse the
catalog to request items they need, track their requests, and manage their provisioned items.
Service architects and administrators can dene new services and publish them to the common catalog.
When dening a service, the architect can specify the kind of item that can be requested, and what options
are available to the consumer as part of submiing the request.
Group managers or line-of-business administrators can specify business policies such as who is entitled to
request specic catalog items or perform specic actions on provisioned items. They can also apply
congurable approval policies to catalog requests.
Foundations and Concepts
10 VMware, Inc.