1.6

Table Of Contents
6 Choose to install the required data collectors and click Next.
The Install vCenter Chargeback Data Collector option is selected by default. You must have at least one
instance of this data collector running and registered with the application for the database synchronization
jobs to run.
You can optionally choose to install the VMware Cloud Director Data Collector and vShield Manager Data
Collector. All the data collectors can be installed even after a vCenter Chargeback instance is installed. If
you are installing the vShield Manager Data Collector, choose to install the VMware Cloud Director Data
Collector too or ensure that at least one instance of VMware Cloud Director Data Collector is running.
7 (Optional) If you chose to install the VMware Cloud Director Data Collector, enter the VMware Cloud
Director database-related information, and click Next.
Option Description
Database Type
The type of database used to create the VMware Cloud Director database.
The only permissible value is ORACLE.
Database URL
The IP address of the system on which the VMware Cloud Director database
is installed.
The database URL can be in any of the following formats:
IP Address
Host Name
Database Port
(Optional) The port on which the database service is listening for requests.
If the port number is not specified, the installer uses the default port. You
must specify the TNS listener port if you are not using the default port 1521.
Database Name
Name of the database in which VMware Cloud Director stores the
application-specific data. This must be the service name and not the SID.
Database Username
The name of the database user. The database user must have privileges to
read the VMware Cloud Director database objects.
Database Password
Password for the user name that you have provided.
If the installer successfully connects to the database, the next screen is displayed.
8 Provide the password for the administrative account of the existing installation and click Next.
9 Review the information displayed on the Pre-Installation Summary screen, and click Install.
The installer starts upgrading the various components. If the upgrade process is successful, the URL for
accessing the vCenter Chargeback application is displayed.
10 Note the URL, and click Done.
The vCenter Chargeback instance is upgraded.
What to do next
You can now connect to the upgraded vCenter Chargeback setup. Ensure that you clear your Web browser
cache before you access the application.
Post-Upgrade Changes in vCenter Chargeback
When you upgrade an existing vCenter Chargeback 1.0 or 1.0.1 installation to vCenter Chargeback 1.5, the
installer makes changes to the user-defined resources created in the existing installation.
In vCenter Chargeback 1.5, user names are case-insensitive. Therefore, the installer renames users in the
existing setup that have the same name but with different casing. The installer uses the prefix CBM_150_USER_
for the duplicate names. You can rename users with such prefix appropriately.
Unlike earlier release, in vCenter Chargeback 1.5 a user cannot be assigned individual privileges on the entities.
Therefore, privileges assigned to the user on entities are grouped together into roles after upgrade. These roles
have names with the prefix CBM_150_DEFAULT_ROLE_NAME_. You can rename such roles.
Chapter 2 Installing vCenter Chargeback
VMware, Inc. 27