Understand the differences between replicated-based and message-based deployment packages.
When deploying a
mobile application project, you must select either replication-based or message-based as the transport. These options do not affect MBO data itself (synchronization and data refresh schedules), but determine transport layer details for the package once deployed to Unwired Server. Separating data (MBO level) details from transport level details allows you to develop a mobile application based on business needs, then select a transport based on how that application is used:
- Replication-based – an application layer service that synchronously pulls data changes from the server. All data is fully replicated. Ideal for applications where data changes (not user actions) determine application use. For example, the device application user synchronizes application data and takes action only if data changes.
- Message-based – uses Sybase Unwired Messaging Service (Messaging Service) that provides a dedicated channel that is always open to asynchronously push data changes, requests, and notifications between client and server. Select this option for use with Mobile Workflow applications. Ideal when several users interact with each other using both replicated and non-replicated (message) data to complete a workflow process. For example, an e-mail based travel application that is initiated by the traveler and requires various levels of approval.
After deployment, packages are decorated with their respective icons depending on the transport option you select.