Setting up Push Synchronization for Replication

(Not applicable to Online Data Proxy)If your device application requires push synchronization, you must configure the device and the runtime accordingly. Push notifications for synchronization requires coordination between developers and platform administrators.

The developer creates the application using MBO packages. The application must be modeled for push synchronization using available callbacks. See Mobile Data Models: Using Mobile Business Objects.
The administrator creates one or more subscription templates for each MBO package used in Sybase Control Center. See Creating Replication Subscription Templates in Sybase Control Center online help.

Subscriptions are processed differently depending on the type of application and device:

For MBOs – When the application user synchronizes the package, a subscription is created on Unwired Server. Subscription properties (derived from the template) enable Unwired Server to send notifications when MBO data changes are detected. The change detection frequency is based on the synchronization group property to which the MBO belongs. Developers can push EIS data updates to the cache using DCNs. Administrators can configure cache groups to automatically refresh the cache per the schedule defined.
When Unwired Server identifies data changes are identified, it generates data notifications for the client, and sends them according to the client's subscription properties. Delivery occurs when the application is online and connected to Unwired Server. The client application developer is expected to handle the notification by initiating a synchronization request to pull the changes down (with or without user prompt).
For iOS platform applications or older messaging applications – Messaging subscriptions are created upon receiving subscription request from the client application and data synchronization messages are sent to the device.