MobiLink is designed to synchronize data among many remote applications that connect intermittently with one or more central data sources. In a basic MobiLink application, your remote clients are SQL Anywhere or UltraLite databases, and your central data source is one of the supported ODBC-compliant relational databases. This architecture can be extended using the MobiLink server API so that there are virtually no restrictions on what you synchronize to on the server side.
In all MobiLink applications, the MobiLink server is the key to the synchronization process. Synchronization typically begins when a MobiLink remote site opens a connection to a MobiLink server. During synchronization, the MobiLink client at the remote site can upload database changes that were made to the remote database since the previous synchronization. On receiving this data, the MobiLink server updates the consolidated database, and then can download changes from the consolidated database to the remote database.
The quickest way to start developing a MobiLink application is to use the Create Synchronization Model Wizard. When you use the wizard, most of the steps outlined below are handled for you. See Introduction to MobiLink models.
However, even when using a MobiLink model, you need to understand the process and components of MobiLink synchronization.
To create a MobiLink application
Set up a consolidated database.
Set up remote databases.
To determine the upload in an UltraLite remote, create publications. See Publications in UltraLite.
To determine how the upload is applied, create server synchronization logic. See Introduction to synchronization scripts.
To download data that has changed since the last download, set up timestamp based synchronization. See Timestamp-based downloads.
Start the MobiLink server. See MobiLink server.
Initiate synchronization on the client.
|Send feedback about this page via email or DocCommentXchange||Copyright © 2008, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.0|