Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 3 > Setting Up Collection > Native collectors > Cisco Process Orchestrator > Mapping data to Cloud Cruiser

Mapping data to Cloud Cruiser

Because you are collecting from both Cisco Process Orchestrator and Cisco IAC, you must map data from both data sources. This section provides considerations for each.

Mapping Cisco Process Orchestrator data

Because Cloud Cruiser uses the XML Collector to collect Cisco Process Orchestrator data, you map this data the same way as other data collected by the XML Collector. For more information, see Mapping data to Cloud Cruiser.

Each Cisco Process Orchestrator request submitted from IAC contains a block of XML populated with data from IAC. This is referred to as NewScale XML and is included in the exported request data as an element named nsxml . Data mapping primarily deals with this section of the available data.

The data mapping for Cisco Process Orchestrator request events assumes one feed will contain many request types and that specific outputs are needed per request type. This is easily done with the XML feed configuration by defining an XPathOutputMapping for the root node per request type (per action classID ). The following data mapping requirements apply:

  • For each type of service or offering, one or more identifiers must serve as a unique instance key.
  • These key identifiers must be captured from all requests for a given type of service so that request data can be properly correlated.
  • Mapping of create and update requests must include a usage start time, the key identifiers, and additional identifiers and resources.
  • Create and update requests for the same type of service must provide the same record content.
  • Mapping of delete requests must include a usage end time and the key identifiers.

Mapping Cisco IAC data

For general instructions for mapping Cisco IAC data, see Data mapping. When using Cisco IAC as a companion to Cisco Process Orchestrator, you must map specific attributes from Cisco IAC data depending on the service type instead of retaining all attributes as identifiers in the output. This ensures that the same output is produced for the same service instance from both Cisco IAC and Cisco Process Orchestrator.

Last modified


This page has no custom tags.


This page has no classifications.

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