Mobile Data Models

There are multiple ways to model enterprise data so that mobile applications can be developed to access data in your enterprise: Mobile Business Objects using the SAP Mobile SDK, Data Objects using SAP Data Orchestration Engine (DOE), OData using SAP® NetWeaver Gateway, and  Object, Transaction, and Synchronization definitions using Agentry Editor.

Based on your data model and business logic, the EIS interface must be defined. This process eventually involves adapting existing services exposing data from the EIS. Your data models connect with your EIS using these data services.

• Mobile Business Objects
  Mobile Business Objects (MBOs) are developed to define the mobile data model to be used by Object API Applications and HTML5/JS Hybrid Apps. Developers build the data model using the Mobile WorkSpace graphical tools, which are provided with SAP Mobile SDK. These tools simplify and abstract EIS connections, and provide a uniform view of transactional objects. MBOs are reusable, allowing you to leverage them across multiple mobile device types.
• OData
  The SAP NetWeaver Gateway exposes OData with extensions specific to SAP. Service documents, that describe service interaction and data, allow users to interact with the SAP application.
• Data Orchestration Engine
  When the back-end enterprise system includes the Data Orchestration Engine (DOE) component of SAP NetWeaver Mobile, DOE data objects define the mobile data model for Object API Applications. DOE consolidates data from diverse SAP back-end sources and distributes it to applications via SAP Mobile Platform messaging.
• Agentry
  Agentry applications handle data modeling and development in a single task. The developer creates Object, Transaction, and Synchronization definitions within the application project using the Agentry Editor’s 4GL development interface.