Synchronization Triggers

Define synchronization through mobile business object (MBO) and device application configuration and programming, or after deployment, through Unwired Server settings.

Synchronization Methods and Triggers
Method	Description
Push	For the push method, either the the MBO developer or the administrator configures synchronization timing (on-demand or scheduled). Typically a refresh schedule or data change notification (DCN) is paired with a subscription template for a given MBO with push synchronization enabled. When MBO data in the CDB changes: Notifications are sent at a set interval. The default is one minute and ends when the client acknowledges it has received notification. Unwired Server determines when individual clients need to be notified of changes and can override device application settings and synchronize the device application with the contents of the CDB. If Unwired Server does not force a synchronization, device application logic determines how to respond to the push notification. The device application developer can: Register to receive push notifications from Unwired Server. Implement a push listener. Implement logic to react to push notifications. For example, if certain data changes the device application synchronizes with the CDB. Note: Unwired Server initiates notifications only for replicated-based synchronization, while messaging-based synchronization pushes data to the device without notification.
Pull	For the pull method, the MBO developer configures the amount of data that is to be synchronized (through a combination of settings such as Synchronization group, synchronization parameters, data filter, and so on), and the device application developer adds the screens and logic that allows a user to pass synchronization parameters and attributes to trigger and control synchronization, including: Starting the device application – this can automatically trigger synchronization. Adding a synchronization event button to the device application – allows the device application user to synchronize based on how the synchronization event is configured. For example, the MBO developer could include a synchronization parameter that filters data displayed by the device application, or supply client parameters (for example, by using the system personalization keys "username" and "password") by which the device synchronizes. Device application logic – the device application developer adds logic that triggers synchronization based on an event.