Content Manager

Overview

You use the Content Manager to define a data model. The data model contains the definition of aggregates and dimensions:

Aggregates are aggregation of sensor data.
Dimensions are properties based on which data is aggregated.

End-to-End Process Flow

The following steps describe the necessary activities for setting up time series data chunks that can then be further analyzed:

Physical devices are modeled and onboarded as Things into SAP IoT. The Things have the master data information of the devices.
Sensor data is measured and sent by the devices.
Using the Content Manager, explore the metadata through catalog API’s.
Define a data model choosing the dimensions and measures from the catalog as well as the required time parameters
Activate the data model. Activation of data model creates and persists aggregate data based on the input parameters.
Incremental aggregation generation happens at regular intervals for newly ingested sensor data and for changes in the thing master data.

Supported Artifacts:

Thing Master Data
Thing Time Series Data

Content Manager Metadata

In order to define a data model, you must understand the metadata that can be used to define it. Content Manager provides Catalog APIs to explore the metadata. These metadata comprise the following categories:

Catalog Type
Catalog
Dataset
Property

Catalog Type

A catalog type defines a static type of an artifact within SAP IoT. The following catalog types are supported:

Catalog Type
Thing Type

Catalog

A catalog defines a business artifact definition of a type. A catalog is based on a catalog type. There can be any number of catalogs inside a single catalog type.

Example

A catalog type named "ThingType" contains user-defined thing types as catalogs. Two thing types ("ThingType1" and "ThingType2") have been created. This constellation is shown in the following table:

Example
Catalog Type	Catalog
ThingType	ThingType1
ThingType	ThingType2

Dataset

Datasets are the actual entities that contain the time series data that can be used to generate aggregates. A dataset is based on a catalog. A catalog can contain one or more datasets.

Example

The previously introduced "ThingType1" has two named property set types assigned, "NPST1", and "NPST2". This results in the following element table:

Example
Catalog Type	Catalog	Dataset
ThingType	ThingType1	NPST1
ThingType	ThingType1	NPST2

Properties

Properties are the attributes of a dataset that can be used in data model definitions. Properties belong to a catalog.

Example

The named property set type "NPST1" contains two properties, "Property1" and "Property2". The element table reflects that as follows:

Example
Catalog Type	Catalog	Dataset	Property
ThingType	ThingType1	NPST1	Property1
ThingType	ThingType1	NPST1	Property2

The following diagram illustrates the mapping of genuine IoT-related entities (such as thing properties and time series data) to the metadata required for integration with SAP Analytics Cloud:

Endpoint

The Content Manager offers an OData endpoint to expose the catalog metadata and to manage the lifecycle of data models:

Resource Endpoint Name Used in Service Keys of a SAP IoT Service Instance: content-manager

Example for a base URL in a cloud foundry environment:

https://sap-iot-noah-live-cm-metadata-management.hana.ondemand.com

Methods

HTTP Method	Action	URI	Scopes
GET	Read Metadata	/metadata/v1/model.svc/$metadata	`<cm>.r`
GET	Read Catalog Types	/metadata/v1/model.svc/CatalogTypes	`<cm>.r`
GET	Read Catalogs	/metadata/v1/model.svc/CatalogTypes('{{CatalogType}}')/Catalogs?$format=json	`<cm>.r`
GET	Read Datasets	/metadata/v1/model.svc/Catalogs(Name='{{Catalog}}',CatalogType='{{CatalogType}}')/Datasets	`<cm>.r`
GET	Read Properties	/metadata/v1/model.svc/Datasets(Name='{{Dataset}}',CatalogType='{{CatalogType}}',CatalogName='{{Catalog}}')/Properties	`<cm>.r`