7.1

The default vRealize Orchestrator server inventory is shared across all tenants and cannot be used per
tenant. For example, if a service architect creates a service blueprint for creating a cluster compute resource,
the consumers from dierent tenants have to browse through the inventory items of all vCenter Server
instances although they might belong to a dierent tenant.
System administrators can install vRealize Orchestrator or deploy the
VMware vRealize ™ Orchestrator Appliance™ separately to set up an external vRealize Orchestrator
instance and congure vRealize Automation to work with that external vRealize Orchestrator instance.
System administrators can also congure vRealize Orchestrator workow categories per tenant and dene
which workows are available to each tenant.
In addition, tenant administrators can also congure an external vRealize Orchestrator instance but only for
their own tenants.
For information about conguring an external vRealize Orchestrator instance and vRealize Orchestrator
workow categories, see Conguring vCenter Orchestrator and Plug-Ins.
List of vRealize Orchestrator Plug-Ins
With plug-ins you can use vRealize Orchestrator to access and control external technologies and
applications. By exposing an external technology in a vRealize Orchestrator plug-in, you can incorporate
objects and functions in workows that access the objects and functions of the external technology.
The external technologies that you can access by using plug-ins can include virtualization management
tools, email systems, databases, directory services, remote control interfaces, and so on.
You can use the standard set of vRealize Orchestrator plug-ins to incorporate external technologies such as
the vCenter Server API and email capabilities into workows. In addition, you can use the
vRealize Orchestrator open plug-in architecture to develop plug-ins to access other applications.
Table 4‑42. Plug-Ins Included by Default in vRealize Orchestrator
Plug-In Purpose
vCenter Server Provides access to the vCenter Server API so that you can incorporate all of
the vCenter Server objects and functions into the management processes
that you automate by using vRealize Orchestrator.
Conguration Provides workows for conguring the vRealize Orchestrator
authentication, database connection, SSL certicates, and so on.
vCO Library Provides workows that act as basic building blocks for customization and
automation of client processes. The workow library includes templates
for life cycle management, provisioning, disaster recovery, hot backup, and
other standard processes. You can copy and edit the templates to modify
them according to your needs.
SQL Provides the Java Database Connectivity (JDBC) API, which is the industry
standard for database-independent connectivity between the Java
programming language and a wide range of databases. The databases
include SQL databases and other tabular data sources, such as
spreadsheets or at les. The JDBC API provides a call-level API for SQL-
based database access from workows.
SSH Provides an implementation of the Secure Shell v2 (SSH-2) protocol.
Allows remote command and le transfer sessions with password and
public key-based authentication in workows. Supports keyboard-
interactive authentication. Optionally, the SSH plug-in can provide remote
le system browsing directly in the vRealize Orchestrator client inventory.
XML A complete Document Object Model (DOM) XML parser that you can
implement in workows. Alternatively, you can use the ECMAScript for
XML (E4X) implementation in the vRealize Orchestrator JavaScript API.
Mail Uses Simple Mail Transfer Protocol (SMTP) to send email from workows.
Configuring vRealize Automation
308 VMware, Inc.