7.2

Table Of Contents
vRealize Automation Installation
Overview 1
You can install vRealize Automation through dierent means, each with varying levels of interactivity.
To install, you deploy a vRealize Automation appliance and then complete the bulk of the installation using
one of the following options:
n
A consolidated, browser-based Installation Wizard
n
Separate browser-based appliance conguration, and separate Windows installations for IaaS server
components
n
A command line based, silent installer that accepts input from an answer properties le
n
An installation REST API that accepts JSON formaed input
After installation, you start using vRealize Automation by customizing the environment and conguring
one or more tenants, which sets up access to self-service provisioning and life-cycle management of cloud
services.
If you installed earlier versions of vRealize Automation, note the following changes before you begin.
n
This release of vRealize Automation introduces an installation API that uses a JSON formaed version
of the silent installation seings.
See “The vRealize Automation Installation API,” on page 151.
n
This release supports the changing of vRealize Automation appliance host names.
See “Change the Master vRealize Automation Appliance Host Name,” on page 122.
n
This release of the vRealize Automation Installation Wizard introduces a post-installation option to
migrate data from an older deployment.
This chapter includes the following topics:
n
“vRealize Automation Installation Components,” on page 11
n
“Deployment Type,” on page 14
n
“Choosing Your Installation Method,” on page 17
vRealize Automation Installation Components
A typical vRealize Automation installation consists of a vRealize Automation appliance and one or more
Windows servers that, taken together, provide vRealize Automation Infrastructure as a Service (IaaS).
VMware, Inc.
11