Mobile Business Objects

Mobile business objects help form the business logic for mobile applications.

You can define MBOs using either a top-down approach—first designing attributes and parameters, then binding them to a data source; or a bottom-up approach—first specifying a data source, then automatically generating attributes and parameters from it.

A mobile application package includes MBOs, roles, and data source connection mappings, and other artifacts that are delivered to the Unwired Server during package deployment.

• Data and Transaction Models
  Mobile business objects (MBOs) implement both a data model and a transaction model.
• Attributes
  Attributes define the structure for the data associated with the MBO instance on the mobile device.
• Operations
  Mobile business objects (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.
• Cache Groups and Synchronization Groups
  The package definition can include cache groups and synchronization groups.
• Roles
  To secure access to an MBO and its operations, developers can assign logical roles, which, together with the physical role (which exists on the underlying security provider repository), helps Unwired Server perform real-time authorization checks against the user identity before allowing the request to go to the enterprise information system (EIS).
• Data Sources
  A data source is the enterprise information system where data is retrieved from and transactions are executed. A connection profile is a design-time connection to a data source. Connection profiles are created to specific data source 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 Unwired Server..
• Data Caching
  Data caching is initial loading (or filling) the consolidated database (CDB, or Unwired Server cache) with enterprise information system (EIS) data, then continuing to refresh the consolidated database with changes from the EIS or mobile device on an ongoing basis.
• EIS to Server Cache Integration
  You can use multiple mechanisms to update the data in the Unwired Server cache.
• Other Key Concepts
  Other key concepts for understanding mobility include object queries, synchronization parameters, result set filters, result set checkers, and personalization keys.
• Object Code Generation
  To access and integrate MBOs in a device application, developers have the option to 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).
• Deployment
  The last step of mobile business object (MBO) development is to deploy the MBO definitions to Unwired Server as a deployment unit generated from a design-time deployment package using Sybase Unwired WorkSpace.