Cloud Cruiser became HPE Consumption Analytics on Nov. 1st. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation

Home > Cloud Cruiser 3 > Setting Up Collection > Native collectors > VMware vCenter - deprecated > Data source configuration

Data source configuration

Table of contents
No headers

A data source is required to provide a VMware vCenter endpoint URL and credentials. You can provide this in Cloud Cruiser as a managed data source, or you can embed connection details in the job file as an explicit data source.

The explicit data source requires that all connection information be set directly on the bean, which means credentials are embedded in one or more job files. To specify the data source for data collection directly in the job XML, use the VCenterDataSourceConfig bean to provide the endpoint URL using the following syntax:

<bean class="com.cloudcruiser.batch.collect.vcenter.VCenterDataSourceConfig">
  <property name="endpoint" value="endpointURL"/>
  <property name="user" value="user"/>
  <property name="password" value="password"/>
  <property name="cnCheckDisabled" value="false"/>
</bean>

This is convenient when developing jobs, but not necessarily secure and can increase maintenance complexity when credentials change.

Alternatively, a managed data source is securely maintained in the application and is referenced by one or more jobs using a unique data source name. You can set the data source connection in Cloud Cruiser and refer to the data source by name (see Managed data source for more information). For example, with the data source managed by the application, the ManagedVCenterDataSource bean in the job file can fetch the data source vc1 by name:

<bean class="com.cloudcruiser.batch.collect.ManagedVCenterDataSource">
  <property name="name" value="vc1"/>
</bean>
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP