7.3
Table Of Contents
- Installing vRealize Automation
- Contents
- vRealize Automation Installation
- Updated Information
- Installation Overview
- Preparing for Installation
- Deploying the vRealize Automation Appliance
- Installing with the Installation Wizard
- The Standard Installation Interfaces
- Using the Standard Interfaces for Minimal Deployments
- Using the Standard Interfaces for Distributed Deployments
- Distributed Deployment Checklist
- Disabling Load Balancer Health Checks
- Certificate Trust Requirements in a Distributed Deployment
- Configure Web Component, Manager Service and DEM Host Certificate Trust
- Installation Worksheets
- Configuring Your Load Balancer
- Configuring Appliances for vRealize Automation
- Install the IaaS Components in a Distributed Configuration
- Install IaaS Certificates
- Download the IaaS Installer
- Choosing an IaaS Database Scenario
- Install an IaaS Website Component and Model Manager Data
- Install Additional IaaS Web Server Components
- Install the Active Manager Service
- Install a Backup Manager Service Component
- Installing Distributed Execution Managers
- Configuring Windows Service to Access the IaaS Database
- Verify IaaS Services
- Installing Agents
- Set the PowerShell Execution Policy to RemoteSigned
- Choosing the Agent Installation Scenario
- Agent Installation Location and Requirements
- Installing and Configuring the Proxy Agent for vSphere
- Installing the Proxy Agent for Hyper-V or XenServer
- Installing the VDI Agent for XenDesktop
- Installing the EPI Agent for Citrix
- Installing the EPI Agent for Visual Basic Scripting
- Installing the WMI Agent for Remote WMI Requests
- Silent Installation
- Post-Installation Tasks
- Configure FIPS Compliant Encryption
- Enable Automatic Manager Service Failover
- Automatic PostgreSQL Database Failover
- Replacing Self-Signed Certificates with Certificates Provided by an Authority
- Changing Host Names and IP Addresses
- Removing a vRealize Automation Appliance from a Cluster
- Licensing vRealize Code Stream
- Installing the vRealize Log Insight Agent
- Change an Appliance FQDN Back to the Original FQDN
- Configure SQL AlwaysOn Availability Group
- Configure Access to the Default Tenant
- Troubleshooting an Installation
- Default Log Locations
- Rolling Back a Failed Installation
- Create a Support Bundle
- General Installation Troubleshooting
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Server Times Are Not Synchronized
- Blank Pages May Appear When Using Internet Explorer 9 or 10 on Windows 7
- Cannot Establish Trust Relationship for the SSL/TLS Secure Channel
- Connect to the Network Through a Proxy Server
- Console Steps for Initial Content Configuration
- Cannot Downgrade vRealize Automation Licenses
- Troubleshooting the vRealize Automation Appliance
- Installers Fail to Download
- Encryption.key File has Incorrect Permissions
- Directories Management Identity Manager Fails to Start After Horizon-Workspace Restart
- Incorrect Appliance Role Assignments After Failover
- Failures After Promotion of Replica and Master Nodes
- Incorrect Component Service Registrations
- Additional NIC Causes Management Interface Errors
- Cannot Promote a Secondary Virtual Appliance to Master
- Active Directory Sync Log Retention Time Is Too Short
- RabbitMQ Cannot Resolve Host Names
- Troubleshooting IaaS Components
- Prerequisite Fixer Cannot Install .NET Features
- Validating Server Certificates for IaaS
- Credentials Error When Running the IaaS Installer
- Save Settings Warning Appears During IaaS Installation
- Website Server and Distributed Execution Managers Fail to Install
- IaaS Authentication Fails During IaaS Web and Model Management Installation
- Failed to Install Model Manager Data and Web Components
- IaaS Windows Servers Do Not Support FIPS
- Adding an XaaS Endpoint Causes an Internal Error
- Uninstalling a Proxy Agent Fails
- Machine Requests Fail When Remote Transactions Are Disabled
- Error in Manager Service Communication
- Email Customization Behavior Has Changed
- Troubleshooting Log-In Errors
SQL Server Database
IaaS uses a Microsoft SQL Server database to maintain information about the machines it manages, plus
its own elements and policies. Most users allow vRealize Automation to create the database during
installation. Alternatively, you may create the database separately if site policies require it.
Distributed Execution Manager
The IaaS DEM component runs the business logic of custom models, interacting with the IaaS SQL
Server database, and with external databases and systems. A common approach is to install DEMs on
the IaaS Windows server that hosts the active Manager Service, but it is not required.
Each DEM instance acts as a worker or orchestrator. The roles can be installed on the same or separate
servers.
DEM Worker—A DEM worker has one function, to run workflows. Multiple DEM workers increase
capacity and can be installed on the same or separate servers.
DEM Orchestrator—A DEM orchestrator performs the following oversight functions.
n
Monitors DEM workers. If a worker stops or loses its connection to Model Manager, the DEM
orchestrator moves the workflows to another DEM worker.
n
Schedules workflows by creating new workflow instances at the scheduled time.
n
Ensures that only one instance of a scheduled workflow is running at a given time.
n
Preprocesses workflows before they run. Preprocessing includes checking preconditions for
workflows and creating the workflow execution history.
The active DEM orchestrator needs a strong network connection to the Model Manager host. In large
deployments with multiple DEM orchestrators on separate servers, the secondary orchestrators serve as
backups by monitoring the active DEM orchestrator, and provide redundancy and failover if a problem
occurs with the active DEM orchestrator. For this kind of failover configuration, you might consider
installing the active DEM orchestrator with the active Manager Service host, and secondary DEM
orchestrators with the standby Manager Service hosts.
Agents
vRealize Automation IaaS uses agents to integrate with external systems and to manage information
among vRealize Automation components.
A common approach is to install vRealize Automation agents on the IaaS Windows server that hosts the
active Manager Service, but it is not required. Multiple agents increase capacity and can be installed on
the same or separate servers.
Virtualization Proxy Agents
vRealize Automation creates and manages virtual machines on virtualization hosts. Virtualization proxy
agents send commands to, and collect data from, vSphere ESX Server, XenServer, and Hyper-V hosts,
and the virtual machines provisioned on them.
Installing vRealize Automation
VMware, Inc. 13