Modeling and mapping of synchronization parameters to load arguments
implicitly generates client defined data partition keys within the SAP Mobile Server cache. Partition keys define subsections of data within an MBO,
enabling parallel data access to large MBO data sets.
For example, you can refresh multiple partitions in parallel, or query one
partition while another is being refreshed. In general, partitions prevent serialized
access to the cache. Some best practices for defining client defined partition keys include:
- Synchronization parameters should be defined and mapped to all
result-affecting load arguments. Failure to do so results in partitions being
continually overwritten/deleted which leads to unexpected results in the mobile
client.
- Result-affecting load arguments are those arguments of the EIS
read operation that affect the results of the operation. Some arguments may be
information needed by the EIS but do not actually affect the results of the read
operation. For example; suppose an MBO is modeled using a Web Service operation
“getAllBooksByAuthor(AuthorName, userKey) where userKey is simply a mechanism to
authenticate a user and does not affect the results of the operation. For a
given “AuthorName” the service will return the same list of books regardless of
the “userKey” value. In this case “userKey” is not result-affecting and
therefore should not be mapped to a synchronization parameter.