7.1

Table 4‑3. Virtual Appliances and Appliance Database
Component Description
vRealize Automation appliance A precongured virtual appliance that deploys the
vRealize Automation server. The server includes the
vRealize Automation console, which provides a single
portal for self-service provisioning and management of
cloud services, as well as authoring and administration.
Appliance Database Stores information required by the virtual appliances. The
database is embedded on one or two instances of vRealize
Automation appliance.
You can select the individual IaaS components you want to install and specify the installation location.
Table 4‑4. IaaS Components
Component Description
Website Provides the infrastructure administration and service
authoring capabilities to the vRealize Automation console.
The Website component communicates with the Model
Manager, which provides it with updates from the
Distributed Execution Manager (DEM), proxy agents and
database.
Manager Service The Manager Service coordinates communication between
agents, the database, Active Directory, and SMTP. The
Manager Service communicates with the console Web site
through the Model Manager. This service requires
administrative privileges to run.
Model Manager The Model Manager communicates with the database, the
DEMs, and the portal website. The Model Manager is
divided into two separately installable components — the
Model Manager Web service and the Model Manager data
component.
Distributed Execution Managers (Orchestrator and Worker) A Distributed Execution Manager (DEM) executes the
business logic of custom models, interacting with the IaaS
database and external databases. DEMs also manage cloud
and physical machines.
Agents Virtualization, integration, and WMI agents that
communicate with infrastructure resources.
Disabling Load Balancer Health Checks
Health checks ensure that a load balancer sends trac only to nodes that are working. The load balancer
sends a health check at a specied frequency to every node. Nodes that exceed the failure threshold become
ineligible for new trac.
For workload distribution and failover, you may place multiple vRealize Automation appliances behind a
load balancer. In addition, you may place multiple IaaS Web servers and multiple IaaS Manager Service
servers behind their respective load balancers.
When using load balancers, do not allow the load balancers to send health checks at any time during
installation. Health checks might interfere with installation or cause the installation to behave unpredictably.
n
When deploying vRealize Automation appliance or IaaS components behind existing load balancers,
disable health checks on all load balancers in the proposed conguration before installing any
components.
n
After installing and conguring all of vRealize Automation, including all vRealize Automation
appliance and IaaS components, you may re-enable health checks.
Installing vRealize Automation
62 VMware, Inc.