Cache Partitions

Partitioning the Unwired Server cache (CDB) divides it into segments that can be refreshed individually, which provides faster system performance than refreshing the entire CDB.

Cache partitioning is determined by one or more partition keys, which is one or more load arguments used by the operation to load data into the cache from the enterprise information system (EIS).

Define a load argument (cache partition key) from a mobile business object (MBO) attribute column in the Properties view by selecting the MBO's Attributes > Load Argument tab. A device application user can specify a value for synchronization parameters that are mapped to load arguments when synchronizing his or her client application, possibly through a personalization key that is also used as a synchronization parameter.

All cache partitions require a load argument:

Create cache partitions through a load argument specified by the client, for example, a load argument that maps to a synchronization parameter and uses a personalization key.
Refresh a cache partition if data in the partition is:
- Expired
- Invalidated
- Inconsistent – if a client has multiple partitions, refresh all partitions even if only one partition expires.
If the MBO is defined with something other than "=" in the where clause, manually edit, in the synchronization tab, the SQL code for the customized download data.