Skip to Content

Data storage in IoT Application Enablement and IoT Services CF

Hi,

I have an IoT Application Enablement Infrastructure connected to an IoT Services CF (4.0) system. When I send device data to the cloud, it is available via both APIs (IoT AE and IoT Services).

I would like to know more about the persistency of this data. Where exactly is it stored? Is it replicated from IoT Services to IoT AE or is there only one persistency? I read something about a big data store in IoT AE (hot/warm/cold storage). Where does this come into play? Do I have some influence where exactly the data is stored?

Thanks and best regards
Felix

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • May 08 at 06:15 AM

    Hi Felix,

    in IoT Service CF it is possible to define one or multiple message processing services [1]. You are able to check how your tenant is configured by using the /about API [2]:

    curl -X GET "https://<INSTANCE>.eu10.cp.iot.sap/iot/core/api/v1/about" -H  "accept: application/json" -u "<USER>:<PASSWORD>"

    As per your description I guess that SQL (storing data for x days in IoT Services) and Kafka (forward data to a specific tenant of IoT Application Enablement) processing is enabled.

    Once the sensor data reaches IoT Application Enablement automatic data processing jobs take about storing it in the managed big data store, specifically in an hot store (aggregated time series data), a warm store (data within a retention period) and a cold store (data beyond retention period) [3].
    An architecture about this setup can be find here [4] (Section Architecture Overview).

    Best Regards
    Christian

    [1] https://help.sap.com/viewer/a7172eb02bf54229add4664fff702676/Cloud/en-US
    [2] https://<INSTANCE>.eu10.cp.iot.sap/iot/core/api/v1/doc/#/About/readAbout
    [3] https://help.sap.com/viewer/350cb3262cb8496b9f5e9e8b039b52db/latest/en-US/1a2766042cab4d44b0d49b28ff31f068.html
    [4] https://help.sap.com/viewer/350cb3262cb8496b9f5e9e8b039b52db/latest/en-US

    Add comment
    10|10000 characters needed characters exceeded