vCenter chargeback manager is a tool from VMware that adds both chargeback and showback capabilities to the cloud suite of products. Its integration with most of the products in the vCloud suite makes it easy to pull usage and resource allocation data which in turn lets the user to obtain granular level of control in billing and charging the customers.
In this blog post we will be going through the steps involved in the installation of vCenter chargeback 2.5.
So lets jump into the installation process assuming the chargeback manager ISO is downloaded from the VMware site.
Mount the vCENTER-CBM-2.5-826950.iso
into the virtual machine which contains the installation image of Chargeback installation file at D:\vCENTER-CBM-2.5-826950\
Run the installer.
Accept the License agreement and proceed.
Choose a destination folder. Unless required, leave it as default.
Enter the details of the Database server and also the instance name. Choose the SQL server Authentication and enter the credentials for the user created for the particular chargeback instance.
Check if the Chargeback VM is able to establish a connection to the DB server by clicking on “Test Connection”
Enter the details of a Load-balancer Server If any or choose the local machine as the load balancer server. This will install the load-balancer on the localhost.
Enter the details for the chargeback manager server. This will install the Manager server on the specified host.
Create an Administrative account to access Chargeback manager. Enter the Administrative Username and Password.
Check in the boxes of the related collectors to install the collectors for vCloud Director, vShield Manager and Chargeback manager.
Enter the IP Details for the vCloud Director and also the credentials to reach vCD so as to installl the data Collector.
Check if all the provided details are correct in the Pre-Installation summary. If correct,then click “Install”
The installation will proceed and the required packages will be installed.
That completes the Chargeback installation successfully.
This blog post can also be found on my blog at