What is Cache Policy? Various Types of Cache Policies in SUP 2.1.2

In Enterprise Mobility by NLN3 Comments

If you are either learning Sybase Unwired Platform(SUP) or being part of a discussion with SUP developers, you may have encountered technical jargon called Cache Policy. Let me try to explain what a Cache policy stands for and various types of them in SUP 2.1.2.

What is Cache Policy ?

Cache policy is a logical grouping of MBOs that determines which set of MBOs need to retrieve data together from the backend system to CDB. An application can have multiple Cache groups of same type or different types of Cache policies.

The following are the cache groups available in SUP 2.1.2

On Demand: The MBOs in this cache group will refresh data when request is raised from the device. When a mobile device requests for data, the request will reach the SUP server and the SUP Server will send the request to the backend EIS Server (could be any back-end system) . When the EIS responds to the request with the data, the data will be first stored into the CDB of SUP Server and the same will be sent to the device cache and the same will be displayed in the Application.    

Online: This cache group will behave similar to the On Demand cache, the only difference is that the data received from the EIS will be sent directly to the client by the SUP Server without storing it in CDB.  

Scheduled: The MBOs in this Cache group will not wait for any requests from the device. The data retrieval will start when the application is deployed and will refresh at the specified interval, which will be defined at the time of Cache Group creation. If the MBO contains any input then the first cache update will happen when the first request from the device is triggered.

DCN: The MBOs in this cache group will not have any data source. The data update will happen using a Data Change Notification (DCN) request which will be triggered by the back-end system.

Do you know how to create a cache group ?

If not, check out  How to create Cache Group in SUP

Do you have any question on Cache Policy ?

 


Comments ( 3 )

  1. Pingback: How to create Cache Groups in SUP 2.1.2 ? Step by Step guide | |

  2. P. M.

    Hello.

    We’re using SUP 2.1 #2 with a SAP R/3 backend and Android devices.

    In SUP Control Center we have a scheduled cache group to be refreshed every 8 hours.

    The cache group refresh takes at least 20 mins. The problem is: if we try to synchronize a RBS based client (Android) during this period, the synchronization hangs until it fails with an exception.

    The cache group refreshing “blocks” clients synchronization. This is a showstopper for us.

    Do we have to wait until it ends before synchronizing? Can’t it be processed in parallel?

Leave a Comment

Comments Policy :
  • Comments are to drive conversation, add your thoughts, experiences, ask questions!
  • Do NOT write hate speech, swear words, or get into fight. Maintain etiquette
  • Enter your Name, valid Email, URL(optional - Facebook, LinkedIn profile URLs).
  • Your email will NOT be published. Do NOT post any phone numbers, email-ids
  • Do NOT post any links from other websites, unless official sites, University websites.
  • By submitting your comment, you agree to Term and Conditions of our website.

This site uses Akismet to reduce spam. Learn how your comment data is processed.