Data Modeling

After connecting to back-end data sources using connection profiles from Unwired WorkSpace, the MBO developer defines the mobile interaction pattern, which typically involves selecting data subsets.

The MBO is developed to define each data subset, describe the data and the operations on the data.

• The data subset is deployed with the MBO package to Unwired Server where the MBO manages synchronization between the EIS and Unwired Server.
• Artifacts generated from the MBO are then used to develop the mobile application, typically further defining the data subset for data representation on the device.

• Mobility Patterns
  MBO design allows developers to build in support for mobility patterns—interactions between the EIS, the MBO, and the device cache. These patterns include data virtualization, publication, subscription, and operation replay.
• Attributes
  Attributes define the structure for the data associated with the MBO instance on the mobile device.
• Operations
  MBOs may incorporate operations that change the data retrieved from the enterprise information system (EIS).
• Relationships
  Relationships define the data association between two MBOs by linking attributes and parameters in one MBO to attributes and parameters in another MBO.
• Other Key Concepts
  Other key concepts for understanding mobility include object queries, synchronization parameters, result set filters, result checkers, and personalization keys.