Home > Cloud Cruiser 4 > Collecting, transforming, and publishing > Microsoft System Center

Microsoft System Center

The Microsoft System Center Collector queries managed data using Operations Manager class libraries. There are two separate collectors: one for the Service Manager components, and the other for the Operations Manager components. Both collectors are based on the System Center 2012 SP1 SDK.

Because these collectors use Windows libraries, they cannot run in a Cloud Cruiser instance installed on Linux. However, you can still run Cloud Cruiser on Linux and collect System Center data.

Copy the collector files to a Windows computer and run them there, writing CC Record files to a shared drive that is accessible to a Linux computer running Cloud Cruiser. Contact HPE for help implementing this deployment architecture.

The following diagram shows the high-level flow for the Service Manager and Operations Manager collectors:

System Center collection flow

Cloud Cruiser connects to a management group and queries for monitoring objects by management class. Each object instance is then translated into a data record and fed into a processing pipeline for transformation and loading into the cost accounting database. At this time, the data collection is a snapshot and represents a point in time. Multiple snapshots can be taken at regular intervals for a more accurate capture of short term resource allocations.

This section contains the following articles:


System requirements

Your System Center environment must:

  • Run on a Microsoft Windows system with the .NET 4.0 Framework installed
  • Include System Center 2012 - Virtual Machine Manager

Operations Manager class model

The Management Class Model is a hierarchical object model with a base type of System.Entity. Cloud Cruiser data collection targets one or more classes in the model with the option of including all derived classes in the collection scope. For example, a collection for type System.Database that includes derived types would also collect data for all instances of type Microsoft.SQLServer.Database .

Data transformation

Sample data from Operations Manager

MonitoringClass: Microsoft.Windows.Computer
DisplayName: WIN‐IR8A2MABCCG.scomlab.net
IPAddress: ", fe80::68f1:bce4:b5ff:4c3b"
LogicalProcessors: 4
NetbiosComputerName: WIN‐IR8A2MABCCG
NetbiosDomainName: SCOMLAB
NetworkName: WIN‐IR8A2MABCCG.scomlab.net
PhysicalProcessors: 1
PrincipalName: WIN‐IR8A2MABCCG.scomlab.net

MonitoringClass: Microsoft.Windows.OperatingSystem
DisplayName: Microsoft Windows Server 2008 R2 Enterprise
LogicalProcessors: 4
OSVersion: 6.1.7601
PhysicalMemory: 4078832
PrincipalName: WIN‐IR8A2MABCCG.scomlab.net
ServicePackVersion: 1.0

Sample transformation steps

<!‐‐ pull in OS memory as billable resource ‐‐>
<bean class="com.cloudcruiser.batch.transform.CreateResourceFromIdentifier">
  <property name="filter">
    <bean class="com.cloudcruiser.batch.filter.ResourceExistsCondition">
      <property name="resourceId" value="Microsoft.Windows.OperatingSystem" />
  <property name="targetResource" value="Computer_MemoryKB" />
  <property name="sourceIdentifier" value="PhysicalMemory" />
  <property name="valuePattern" value=".*" />
<!‐‐ convert memory from KB to MB ‐‐>
<bean class="com.cloudcruiser.batch.transform.CalculateResource">
  <property name="filter">
    <bean class="com.cloudcruiser.batch.filter.ResourceExistsCondition">
      <property name="resourceId" value="Computer_MemoryKB" />
  <property name="targetResource" value="Microsoft.Windows.Computer_Memory" />
  <property name="expression" value="Computer_MemoryKB / 1024" />
<!‐‐ assign charge account based on 'PrincipalName' identifier ‐‐>
<bean class="com.cloudcruiser.batch.transform.CreateIdentifierFromTable">
  <property name="translateTitle" value="Accounts by Host"/>
  <property name="sourceIdentifier" value="PrincipalName"/>
  <property name="targetIdentifier" value="@acctid"/>

System Center collectors

The Service Manager collector includes objects of management class type System.WorkItem.ServiceRequest that have a CompletedDate matching the select date specified when running the job.

The list of identifiers included in the output record produced by the Operations Manager collector is a list of properties for the object in the record and are dependent on the management class type of the object.

Sample jobs

The following sample job files are located in the <install_dir>/job_samples directory:

  • systemcenter-collect.xml
  • systemcenter-load.xml

Spring Batch XML example

<batch:step id="collect_feed1">
    <bean class="com.cloudcruiser.batch.microsoft.SCOMCollectTasklet">
      <property name="active" value="true"/>
      <property name="feedName" value="operations_manager"/>
      <property name="dataSourceConfig">
        <bean class="com.cloudcruiser.batch.collect.microsoft.SCDataSourceConfig">
          <property name="server" value=""/>
          <property name="domain" value="LAB"/>
          <property name="username" value="username"/>
          <property name="password" value="password"/>
      <property name="feedConfig">
        <bean class="com.cloudcruiser.batch.collect.microsoft.om.SCOMFeedConfig">
          <property name="managementClassName" value="Microsoft.SystemCenter.VirtualMachineManager.2012.VirtualMachine"/>
          <property name="collectAllProperties" value="true"/>
Last modified



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