Skip to Content

In SMP 3.0 how can i configure to update data from Backend to SMP 3.0 CDB automatically?

Hello All,

Earlier in SMP 2.3 we had Cache group policy to be used by all MBOs particularly 'Scheduled Cache Refreshes' for information fetching from the enterprise information server (EIS) and populated into the cache DB on either of these hourly or daily frequencies automatically according to the schedule and range of time configured.

How to configure for Automatic Data Update from Backend to SMP 3.0 Cache DB (CDB) regardless of Client requests?

looking for help!



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jul 10, 2017 at 01:58 PM

    Hello Vikram,

    SAP Mobile Platform 3.0 platform is based on open standard like OData, REST, OSGI, HTML5, Cordova (unlike propriety MBO based, however as part of SMP 3.0 runtime & SDK offering, you will also see MBO runtime and MBO Toolkit to support all existing MBO based projects/applications)

    There is no concept of cache DB in SMP30 like in SMP23,

    For your information, any SMP 3.0 OData offline app, there could be below 3 possibilities of data flow:

    1. Initial data download: (online store)- transfer data between SMP server and device via HTTP(s) protocol, will create a local ultra DB on device.

    2&3, now, Assuming you are working being in offline mode, you may do some local transactions (CRUD) and want to push them back to backend. This method is called FLUSH. At the same time, there might be few records could have updated at backend and you would want to download it in the device Ultra DB to have latest data. This method is called as REFRESH. for both FLUSH & REFRESH, mobilink protocol is used (to transfer data between SMP server and device)

    I would suggest you to go through this series of blogs:


    JK (Moderator)

    Add comment
    10|10000 characters needed characters exceeded