User`s guide

In earlier releases, any user can view any of the vCenter Servers or cost models. However, starting from vCenter
Chargeback 1.5, users must be assigned role with privileges to access the cost models and vCenter Servers.
Only the super user can view all the resources in the application. The vCenter Server users who are added to
the application can view the vCenter Server to which they belong. These users can also view the default
hierarchy of the corresponding vCenter Server.
In earlier releases of vCenter Chargeback, users with the view privilege on a hierarchy have privileges to view
all the reports generated on the hierarchy. After the upgrade, a user can view only the reports that he has
generated. If the user who has generated the report is deleted, then the report is assigned to the super user.
Scheduled report generation might fail after the upgrade is compete. The users who scheduled the reports
must be assigned roles with access privileges on the cost models, chargeback hierarchies, and chargeback
hierarchical entities used for scheduling the reports. vCenter Chargeback does not display any error message
stating the scheduled report generation failed due to lack of privileges.
The Report Viewer role in the earlier versions of vCenter Chargeback is upgraded to the Report Generator role
in vCenter Chargeback 1.5. After upgrade, users with the Report View role are assigned the Report Generator
role, which has more privileges. Assess the privilege requirements for such users and reassign new roles
appropriately.
Any local fixed cost added to a cost template in the existing setup is renamed after the upgrade. If you upgraded
from vCenter Chargeback 1.0, then the fixed cost name is prefixed with
CT_ id_of_cost_template_fixed_cost . If you upgraded from vCenter Chargeback 1.0.1, then the fixed cost
name is prefixed with G_ id_of_cost_template_fixed_cost .
Services Related to the vCenter Chargeback Application
When vCenter Chargeback is installed, by default, a load balancer is installed. You can install one or more data
collector instances too. The services related to vCenter Chargeback and its corresponding components must
be started for the application to function properly.
The services related to the application and the corresponding components are:
VMware vCenter
Chargeback Service
Starting this service starts the application.
VMware vCenter
Chargeback Load
Balancer Service
Starting this service starts the load balancer. This service must be running so
that the load balancer can receive user requests and route them to the
application for them to be serviced.
VMware vCenter
Chargeback
DataCollector-
Embedded
Starting this service starts the Data Collector instance that was installed along
with the vCenter Chargeback application.
VMware vCenter
Chargeback
DataCollector
Starting this service starts the Data Collector instance that was installed
individually (in this case, the name of the instance is DataCollector) and not
with the application.
VMware vCenter
Chargeback - VMware
Cloud Director
DataCollector-
Embedded
Starting this service starts the VMware Cloud Director Data Collector instance
that was installed along with the vCenter Chargeback application.
VMware vCenter
Chargeback - VMware
Cloud Director
DataCollector
Starting this service starts the VMware Cloud Director Data Collector instance
that was installed individually (in this case, the name of the instance is VMware
Cloud Director DataCollector) and not with the application.
vCenter Chargeback User’s Guide
28 VMware, Inc.