Installation

Table Of Contents
Installing View Composer 5
To use View Composer, you create a View Composer database, install the View Composer service, and
optimize your View infrastructure to support View Composer. You can install the View Composer service
on the same host as vCenter Server or on a separate host.
View Composer is an optional feature. Install View Composer if you intend to deploy linked-clone desktop
pools.
You must have a license to install and use the View Composer feature.
This chapter includes the following topics:
n
“Prepare a View Composer Database,” on page 33
n
“Configuring an SSL Certificate for View Composer,” on page 40
n
“Install the View Composer Service,” on page 41
n
“Configuring Your Infrastructure for View Composer,” on page 43
Prepare a View Composer Database
You must create a database and data source name (DSN) to store View Composer data.
The View Composer service does not include a database. If a database instance does not exist in your
network environment, you must install one. After you install a database instance, you add the View
Composer database to the instance.
You can add the View Composer database to the instance on which the vCenter Server database is located.
You can configure the database locally, or remotely, on a network-connected Linux, UNIX, or Windows
Server computer.
The View Composer database stores information about connections and components that are used by View
Composer:
n
vCenter Server connections
n
Active Directory connections
n
Linked-clone desktops that are deployed by View Composer
n
Replicas that are created by View Composer
Each instance of the View Composer service must have its own View Composer database. Multiple View
Composer services cannot share a View Composer database.
For a list of supported database versions, see “Database Requirements for View Composer,” on page 11.
To add a View Composer database to an installed database instance, choose one of these procedures.
VMware, Inc.
33