Client Defined Cache Partitions

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

Client defined 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) in the Attributes > Load Arguments tab of the MBO's Properties view. A device application user can specify values for synchronization parameters that are mapped to load arguments when synchronizing his or her client application, possibly through personalization keys or default values.

All client defined 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 which uses a personalization key or default value.
• 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.

• Examples: Parameters and Client Defined Cache Partitions
  Create client defined cache partitions based on mobile business object (MBO) and load argument definitions.