Installation

Table Of Contents
Add an ODBC Data Source to Oracle 12c or 11g
After you add a View Composer database to an Oracle 12c or 11g instance, you must congure an ODBC
connection to the new database to make this data source visible to the View Composer service.
When you congure an ODBC DSN for View Composer, secure the underlying database connection to an
appropriate level for your environment. For information about securing database connections, see the
Oracle database documentation.
If the underlying database connection uses SSL encryption, we recommend that you congure your
database servers with SSL certicates signed by a trusted CA. If you use self-signed certicates, your
database connections might be susceptible to man-in-the-middle aacks.
Prerequisites
Verify that you completed the steps described in Add a View Composer Database to Oracle 12c or 11g,” on
page 42 or “Use a SQL Statement to Add a View Composer Database to an Oracle Instance,” on page 42.
Procedure
1 On the View Composer database computer, select Start > Administrative Tools > Data Source (ODBC).
2 From the Microsoft ODBC Data Source Administrator wizard, select the System DSN tab.
3 Click Add and select the appropriate Oracle driver from the list.
For example: OraDb11g_home
4 Click Finish.
5 In the Oracle ODBC Driver Conguration dialog box, type a DSN to use with View Composer, a
description of the data source, and a user ID to connect to the database.
If you congured an Oracle database user ID with specic security permissions, specify this user ID.
N You use the DSN when you install the View Composer service.
6 Specify a TNS Service Name by selecting the Global Database Name from the drop-down menu.
The Oracle Database Conguration Assistant species the Global Database Name.
7 To verify the data source, click Test Connection and click OK.
What to do next
Install the new View Composer service. See “Install the View Composer Service,” on page 45.
Configuring an SSL Certificate for View Composer
By default, a self-signed certicate is installed with View Composer. You can use the default certicate for
testing purposes, but for production use you should replace it with a certicate that is signed by a Certicate
Authority (CA).
You can congure a certicate before or after you install View Composer. In View 5.1 and later releases, you
congure a certicate by importing it into the Windows local computer certicate store on the Windows
Server computer where View Composer is, or will be, installed.
n
If you import a CA-signed certicate before you install View Composer, you can select the signed
certicate during the View Composer installation. This approach eliminates the manual task of
replacing the default certicate after the installation.
n
If you intend to replace an existing certicate or the default, self-signed certicate with a new certicate
after you install View Composer, you must import the new certicate and run the SviConfig
ReplaceCertificate utility to bind your new certicate to the port used by View Composer.
View Installation
44 VMware, Inc.