Mobile Business Object Mobility Properties

To understand how to customize MBOs to meet your device application needs, you must first understand the concepts that affect end-to-end data flow between client, Unwired Server cache (CDB), and the enterprise information system (EIS) to which the MBOs are bound.

• Load Arguments
  Load arguments control the amount of data refreshed between the enterprise information system (EIS) and the cache database (CDB), and each load argument creates its own partition in the CDB based on load argument value (partition key). Partitions are refreshed concurrently, thus improving performance. In contrast, synchronization parameters filter CDB data downloaded to the mobile device during device application synchronization.
• Synchronization
  Determine the amount of data (filter), and under what conditions (timing and triggers), mobile devices upload MBO data to and download data from the Unwired Server cache (CDB).
• Cache Groups
  A cache group specifies the data refresh behavior for every mobile business object (MBO) within that group.
• Operation Cache Policies
  Setting an operation cache policy for mobile business object (MBO) operations gives you more control of Unwired Server interactions with the enterprise information system (EIS) to which the MBO is bound, and Unwired Server cache (CDB) updates. Fine-tuning these interactions and updates improves both Unwired Server and device application performance.
• Object Queries
  Object queries are SQL statements associated with a mobile business object (MBO), against the persistent store on the device that returns a subset of a result set. For example, an object query is used to filter data already downloaded from the CDB to display a single row of a table when triggered.