VMware VCENTER CHARGEBACK 1.5 - API Manual de usuario descargar pdf (Pagina 42)

Option Description

Database Username

The name of the database user. The database user must have privileges to

read the vCloud Director database objects. If you have provided a JDBC

URL with Windows Authentication for an SQL Server database, this

database user account is not used for logging in to the database. However,

you must provide the database user account information.

Database Password

Password for the user name that you have provided.

If the installer successfully connects to the database, the next screen is displayed.

10 Provide the password for the administrative account of the existing installation and click Next.

11 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 Manager is displayed.

12 Note the URL, and click Done.

The vCenter Chargeback Manager instance is upgraded.

What to do next

Check the install log. If the upgrade is successful but the database partitioning fails, refer to the

troubleshooting topic Upgrade Succeeded but Database Partitioning Failed in the vCenter Chargeback Manager

Best Practices and Troubleshooting Guide.

You can now connect to the upgraded vCenter Chargeback Manager setup. Ensure that you clear your Web

browser cache before accessing the vCenter Chargeback Manager.

Check whether the data collectors are running successfully. Ensure that the vCenter Server user used to add

the vCenter Server to vCenter Chargeback Manager has the appropriate privileges assigned on the root

folder of the vCenter Server. For more information on the privileges, refer to the Add vCenter Server

Information section in the vCenter Chargeback Manager User's Guide.

Upgrading vCenter Chargeback Manager and Configuring in DMZ

You can upgrade an existing vCenter Chargeback Manager setup to version 2.5.1 such that the load balancer

runs in the DMZ and the vCenter Chargeback Manager instance is in a secured internal network.

If you have a vCenter Chargeback Manager 2.0 or later setup and want the load balancer and the vCenter

Chargeback Manager to run on different machines post-upgrade, then you must perform the following

tasks.

Procedure

1 Perform the pre-upgrade tasks listed in “Pre-Upgrade Tasks for vCenter Chargeback Manager,” on

page 39.

2 Stop all the vCenter Chargeback Manager related services.

You must stop the load balancer, database, and all the data collector services along with the vCenter

Chargeback Manager service.

3 Uninstall the existing vCenter Chargeback Manager setup but retain the database.

Ensure that you do not select the option to empty the database during uninstallation.

4 Run the vCenter Chargeback Manager installer on the machine on which you want to install the load

balancer.

During the install provide the details of the retained vCenter Chargeback Manager database. Do not

select the Install vCenter Chargeback Server option during the installation.

vCenter Chargeback Manager Installation and Upgrade Guide

42 VMware, Inc.

1 2 ... 37 38 39 40 41 42 43 44 45 46 47 ... 59 60

Comentarios a estos manuales

Sin comentarios

VMware VCENTER CHARGEBACK 1.5 - API Manual de usuario Pagina 42

Comentarios a estos manuales