Data Modeling

After connecting to datasources using connection profiles from SAP Mobile 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 SAP Mobile Server where the MBO manages synchronization between the EIS and SAP Mobile 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.

• Datasources
  A datasource is the enterprise information system (EIS) where data is retrieved from and transactions are executed. A connection profile is a design-time connection to a datasource. Connection profiles are created to specific datasources by providing connection information such as host, port, login, and password among others. The connection profiles are used to define MBOs and operations, and mapped to existing, or used to create new, server connections when the package is deployed to SAP Mobile Server.
• MBO Attributes
  MBO 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 load arguments (the read operation's parameters) in one MBO to attributes and load arguments 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.