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 Unwired WorkSpace graphical tools, which are provided with Sybase 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.

When deployed using Sybase Unwired Platform, MBOs provide a layer of abstraction from Unwired Server's interaction with heterogenous EIS/devices, as shown in the following diagram.

• Data Modeling
  After connecting to datasources using connection profiles from Sybase Unwired WorkSpace, the MBO developer defines the mobile interaction pattern, which typically involves selecting data subsets.
• Data Caching
  Data caching is initial loading, or filling, the Unwired Server cache with enterprise information system (EIS) data, then continuing to refresh the cache with changes from the EIS or mobile device on an ongoing basis.
• Object API Code Generation
  To access and integrate MBOs in a device application, developers generate object code for the target device platform, and then use their IDE of choice to build the native device application. The object code generation step is the bridge from the Unwired Server server-side development (MBOs) to client-side development (device applications).
• Package Deployment
  The last step of mobile business object (MBO) development is to deploy the MBO definitions to Unwired Server as a deployment package using Unwired WorkSpace .