Understanding Fundamental Mobile Development Concepts

This provides basic information for understanding mobile development using Unwired Platform.

• Learning Unwired WorkSpace Basics
  If you are already familiar with Eclipse, you will find Sybase Unwired Platform features are well integrated. If you are not familiar, you can quickly learn the basic layout of Unwired Workspace and the location of online help.
• Basic and Advanced Developer Profiles
  Optionally you can set Basic and Advanced developer profile preferences for Unwired WorkSpace. You can select the specific features to enable or disable from each of the profiles. Features that are disabled are grayed out. You can also right-click in Mobile Object Diagram, and select Switch Developer Profile Basic/Advanced to switch.
• Mobile Business Objects
  A mobile business object (MBO) is derived from a data source, and helps form the business logic for mobile applications. When grouped in projects, MBOs allow mobile applications to be deployed to an Unwired Server and referenced in mobile devices (clients).
• 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..
• Application Types
  Sybase Unwired Platform supports two choices for application type. First is the native application type, and the other is the container-based business workflow type.
• Deployment to Unwired Server
  Deploy mobile business objects (MBOs) in a deployment package to Unwired Server.
• Data Synchronization and Data Refresh
  Since dataset variations occur between multiple clients and the enterprise information system (EIS) data to which mobile business object (MBO) data is bound, synchronization is required to reconcile differences and bring each client into coherence with the working copy of the EIS data maintained in the consolidated database (CDB), before writing updates back to the EIS.