The vRealize Orchestrator configuration includes guidance on client configuration, database configuration, SSL certificates, and plug-ins.

vRealize Orchestrator Client

The vRealize Orchestrator client is a desktop application that lets you import packages, create, run, and schedule workflows, and manage user permissions.

You can install the standalone version of the vRealize Orchestrator Client on a desktop system. Download the vRealize Orchestrator Client installation files from the vRealize Orchestrator appliance page at https://vRA_hostname/vco. Alternatively, you can run the vRealize Orchestrator Client using Java WebStart directly from the homepage of the vRealize Automation appliance console.

vRealize Orchestrator Database

vRealize Orchestrator requires a database. This design uses the PostgreSQL database embedded within the vRealize Automation appliance.

Table 1. Design Decisions on the vRealize Orchestrator Database

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-CMP-VRO-008

Use the PostgreSQL database that is embedded in the vRealize Automation appliance.

Provides the following advantages:

  • Performance improvement

  • Design simplification

None.

vRealize Orchestrator Plug-Ins

You use plug-ins to 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 workflows that access the objects and functions of the external technology. The external technologies that you can access using plug-ins can include virtualization management tools, email systems, databases, directory services, and remote control interfaces. vRealize Orchestrator provides a set of standard plug-ins for technologies as the vCenter Server API and email capabilities.

vCenter Server Plug-In

You can use the vCenter Server plug-in to manage multiple vCenter Server instances. You can create workflows that use the vCenter Server plug-in API to automate tasks in your vCenter Server environment. The vCenter Server plug-in maps the vCenter Server API to JavaScript code that you can use in workflows. The plug-in also provides actions that perform individual vCenter Server tasks that you can include in workflows.

The vCenter Server plug-in provides a library of standard workflows that automate vCenter Server operations. For example, you can run workflows that create, clone, migrate, or delete virtual machines. Before managing and running workflows on the objects in your vSphere inventory, you must configure the vCenter Server plug-in and connect vRealize Orchestrator to the vCenter Server instances you want to orchestrate.

Table 2. Design Decisions on the vCenter Server Plug-In of vRealize Orchestrator

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-CMP-VRO-009

Configure the vCenter Server plug-in to control communication with the vCenter Server instances.

Required for communication to vCenter Server instances, and as such required for workflows.

None.

Multi-Tenancy in vRealize Orchestrator

vRealize Orchestrator introduces a multi-tenant architecture where several vRealize Automation tenants can share a single external or embedded vRealize Automation instance. The Orchestrator multi-tenancy feature provides isolation between tenants.

After you enable multi-tenancy, the objects that the Orchestrator instance manages are assigned a system scope or a tenant-specific scope. Тhe tenant-specific objects in Orchestrator are isolated between the vRealize Automation tenants and from the system-scope objects. Tenant users access their tenant-specific content in the Orchestrator client.

For backwards compatibility and simplified user experience with the product, the multi-tenancy feature in vRealize Orchestrator is disabled by default. Enabling multi-tenancy is an irreversible change.

Table 3. Design Decision on Multi-Tenancy in vRealize Orchestrator

Decision ID

Design Decision

Design Justification

Design Implication

CSDDC-CMP-VRO-010

If required by your organization, enable the multi-tenancy feature of vRealize Orchestrator.

Multiple vRealize Automation tenants can share the embedded vRealize Orchestrator cluster.

To provide isolation between tenant objects, the objects that Orchestrator manages are assigned a system scope or a tenant-specific scope.

Enabling the multi-tenancy feature of vRealize Orchestrator is irreversible.