Mobile Business Object Design

Design the mobile business objects (MBOs) to connect to a data source, and to implement business logic.

A major consideration for designing MBOs is how to get data out of the enterprise information system (EIS) that is specific enough for the mobile device application or workflow package. Strategies include:

Loading schemes to populate MBOs.
Cache update policies to keep the MBO current.
SQL-based object queries to filter out unneeded data.
Application-side personalization keys to narrow the search.
Object queries to access the local device database, as well as the back-end system, when Unwired Server is not available on demand.

More advanced strategies may implement the result-set filter and result checker APIs and coding to fine-tune processing.

Also consider how to perform back-end EIS operations (such as creating, editing, and deleting data), process transactions between the EIS and the mobile device, keep data up-to-date without putting undue load on system processing, and establish relationships between MBOs. You may also need to consider role mapping, logical roles, and security access in your design.

Sybase Unwired WorkSpace provides the development tools for creating MBOs that can meet these needs.

See Sybase Unwired WorkSpace – Mobile Business Object Development for information about developing and working with MBOs.

See Developer Guide for Unwired Server for API information.