Mobile business objects, grouped in a project, form the business logic for mobile applications.
A mobile business object (MBO) is derived from a data source (database server, Web Service, SAP server, and so on). When grouped in projects, MBOs form the business logic for mobile applications that can be deployed to an Unwired Server and referenced in mobile devices (clients). MBOs include:
- Implementation-level details – read-only metadata columns that include information about the data in the
implementation. Implementation details also include arguments, which are read-only parameters that
are passed to the back-end data source.
- Abstract-level details – attributes correspond to class-level properties on the
mobile client and map to columns. Parameters correspond to
synchronization parameters on the mobile client and map to arguments. MBOs
can also contain operations, which themselves contain parameters
and arguments, and can be used to update, create, or delete
data.
- Relationships – defined between MBOs, link attributes, and
parameters in one MBO to attributes and parameters in another MBO.
You can define MBOs using either a top-down approach—designing attributes and parameters first, and later binding them to a data source, or a bottom-up approach—specifying a data source, and automatically generating attributes and parameters from it.
A mobile application includes MBOs, as well as role and server mappings, and other artifacts that are delivered to the Unwired Server during deployment.