7.0
Table Of Contents
- Foundations and Concepts
- Contents
- Foundations and Concepts
- Using Scenarios
- Using the Goal Navigator
- Introducing vRealize Automation
- Tenancy and User Roles
- Service Catalog
- Infrastructure as a Service
- XaaS Blueprints and Resource Actions
- Common Components
- Life Cycle Extensibility
- vRealize Automation Extensibility Options
- Leveraging Existing and Future Infrastructure
- Configuring Business-Relevant Services
- Extending vRealize Automation with Event-Based Workflows
- Integrating with Third-Party Management Systems
- Adding New IT Services and Creating New Actions
- Calling vRealize Automation Services from External Applications
- Distributed Execution
n
Promotes efficiencies in the virtual infrastructure by making it possible to compare the costs,
efficiency, and availability of their private cloud with public cloud providers and industry benchmark
data.
n
Optimizes decisions about placement for virtual workloads and tradeoffs between buying new
hardware and using public cloud providers.
For more information about vRealize Business Standard Edition, see the
vRealize Business Standard Edition documentation set.
Tenancy and User Roles
vRealize Automation supports multiple tenants in the same installation. Users always log in and perform
their tasks in a specific tenant. Some administrator roles can manage configuration that affects multiple
tenants.
Tenancy Overview
A tenant is an organizational unit in a vRealize Automation deployment. A tenant can represent a
business unit in an enterprise or a company that subscribes to cloud services from a service provider.
Each tenant has its own dedicated configuration. Some system-level configuration is shared across
tenants.
Table 1. Tenant Configuration
Configuration Area Description
Login URL Each tenant has a unique URL to the vRealize Automation console.
n
The default tenant URL is in the following format: https://hostname/vcac
n
The URL for additional tenants is in the following format:
https://hostname/vcac/org/tenantURL
Identity stores Each tenant requires access to one or more directory services, such as OpenLDAP or
Microsoft Active Directory servers, that are configured to authenticate users. You can
use the same directory service for more than one tenant, but you must configure it
separately for each tenant.
Branding A tenant administrator can configure the branding of the vRealize Automation console
including the logo, background color, and information in the header and footer. System
administrators control the default branding for all tenants.
Notification providers System administrators can configure global email servers that process email
notifications. Tenant administrators can override the system default servers, or add
their own servers if no global servers are specified.
Business policies Administrators in each tenant can configure business policies such as approval
workflows and entitlements. Business policies are always specific to a tenant.
Foundations and Concepts
VMware, Inc. 11