Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Setting Up Collection > Native collectors > HP Cloud Service Automation > Mapping data to Cloud Cruiser

Mapping data to Cloud Cruiser

A sequence of calls gathers pertinent information into a single document for data mapping. For each subscription, the subscription detail document provided by CSA is used as the base input document for collection. Each Service Offering is mapped into multiple resources for the initial and recurring prices of the base offering, as well as each option. This provides resource costs as part of the resulting CC Record data by using standard data mapping capabilities controlled by the feed configuration for a CSA collection.

Subscription data is collected by making a series of REST calls to gather data on the subscription itself, as well as all related requests and service instances. All data is then combined into a single XML document that you can map to CC Record output using XPath expressions and standard output field mapping. This works the same as does mapping output from the XML Collector. For information about mapping output for that collector that also applies to the CSA Collector, see Mapping data to Cloud Cruiser.

Format of XML input

The input XML document format is:

           +‐‐(1 to many)‐[ServiceRequest]
           +‐‐(0 or 1)‐[ServiceInstance]
  • ServiceSubscription : Comes from the CSA API as the response to a subscription detail request. Detail for each corresponding service request is then requested from CSA and added to the end of the ServiceSubscription content as a child node. The same is done for service instance data related to the subscription.
  • ServiceRequest : Contains a snapshot of the service offering pricing at the time of the request. This provides passthrough resource costs as part of the resulting CC Record data by using standard data mapping capabilities controlled by the feed configuration for a CSA collection.
  • ServiceInstance : Contains component-level data of the actual service instance that was requested of the service provider. Collection of service instance data is optional because it considerably increases the volume of data coming from CSA and might not be needed in all cases. Service instance data could contain key values that can be used for generating lookup tables to support correlating provider data to CSA subscriptions. This is how MOE and vCenter data can be collected directly from the provider API and mapped to the appropriate account where corresponding subscription costs are contained.

All input document content comes directly from CSA 3.x REST API responses. To prepare for data mapping, the input document(s) can be printed to the console or written to a file by using HPCSA3Collector properties, such as setPrintEntityXML or setXmlOutput .

Feed configuration

The feed configuration for the CSA Collector defines how data is mapped from the subscription document to one or more CC Records. Each record produced by the collector always includes some identifiers for the organization and user, in addition to any data mapped from the subscription XML.

Last modified


This page has no custom tags.


This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP