Cache groups and synchronization groups are part of the MBO package definition and define how data is preserved in CDB and updated in the mobile application..
A cache group is a collection of mobile business objects (MBOs) that share the same cache policy, which defines how the data in the Unwired Server cache is refreshed and validated for related MBOs. A cache group specifies the data refresh behavior for every mobile business object (MBO) within that group.
During development, MBOs are grouped based on their data refresh requirements.
- Cache group – includes a cache policy and the MBOs that share that policy.
- Cache – MBO data in the Unwired Server cache (also called the consolidated database, or CDB) can be refreshed according to a cache policy, along with other mechanisms, such as data change notification (DCN).
- Cache policy – defines the cache refresh behavior and properties for the MBOs within the cache group based on the policy:
- On demand –
the cache expires after a certain period of time such as 10 minutes. The cache is not updated until a request is made of the cache and the cache has expired. If a request is made of the cache and it is expired, there may be a delay responding to the request while the cache is refreshed.
- Scheduled – the cache is refreshed according to a schedule such as 7:00 am, 1:00 pm, or 6:00 pm.
- DCN – the cache never expires. Data refresh is triggered by an enterprise information system (EIS) Data Change Notification.
- Online – only used with mobile workflow applications, data is not cached and a no cache policy is assigned. EIS data is essentially accessed real-time.
A synchronization group is also a collection of MBOs that defines a unit of synchronization so that data and changes are transmitted as a unit to and from the device. Synchronization determines the amount of data (filter), and under what conditions (timing and triggers), mobile business objects (MBOs) upload data to and download data from Unwired Server.