Contents Index Server-Initiated Synchronization Supported platforms

MobiLink Synchronization User's Guide
  Server-Initiated Synchronization

Introduction


MobiLink server-initiated synchronization works as follows:

Example 

For example, a fleet of truck drivers uses mobile databases to determine routes and delivery points. A driver synchronizes a report of a traffic disruption. The Notifier detects the change in the consolidated database and automatically sends a message to the remote device of every driver whose route is affected, which causes the drivers' remote databases to synchronize so that the drivers will use an alternate route.

The notification process 

In the following illustration, the Notifier polls a consolidated database and detects a change that it has been configured to look for. In this scenario, the Notifier sends a message to a single remote device, resulting in the remote database being updated via synchronization.

The process of server-initiated synchronization.

Following are the steps that occur in this example:

  1. Using a query based on business logic, the Notifier polls the consolidated database to detect any change that needs to be synchronized to the remote.

  2. When a change is detected, the Notifier prepares a message to send to the remote device.

  3. The Notifier sends a message over UDP or SMTP. Most telecommunication providers have a service that lets you send SMS messages by sending e-mails via SMTP to a special address.

  4. The Listener checks the contents and sender of the message against a filter.

  5. If the message matches the filter, the Listener runs a program that has been associated with the filter. For example, the Listener runs dbmlsync or it launches an UltraLite application.


Contents Index Server-Initiated Synchronization Supported platforms