Synchronization subscription creation

After creating MobiLink users and publications, you must subscribe at least one MobiLink user to one or more pre-existing publications. You do this by creating synchronization subscriptions.

Note

You must ensure that all subscriptions for a MobiLink user are synchronized to only one consolidated database. Otherwise, you may experience data loss and unpredictable behavior.

A synchronization subscription links a particular MobiLink user with a publication. It can also contain other information needed for synchronization. For example, you can specify the address of the MobiLink server and options for a synchronization subscription. Values for a specific synchronization subscription override those set for MobiLink users.

Synchronization subscriptions are required only in MobiLink SQL Anywhere remote databases. Server logic is implemented through synchronization scripts, stored in the MobiLink system tables in the consolidated database.

A single SQL Anywhere database can synchronize with more than one MobiLink server. To allow synchronization with multiple servers, create different MobiLink users for each server.

See CREATE SYNCHRONIZATION SUBSCRIPTION statement [MobiLink].

Example

To synchronize the Customers and SalesOrders tables in the SQL Anywhere sample database, you could use the following statements.

First, create a publication containing the Customers and SalesOrders tables. Give the publication the name testpub.

CREATE PUBLICATION testpub
 (TABLE Customers, TABLE SalesOrders)

Next, create a MobiLink user. In this case, the MobiLink user is demo_ml_user.
CREATE SYNCHRONIZATION USER demo_ml_user

To complete the process, create a synchronization subscription named my_sub that links the user and the publication.

CREATE SYNCHRONIZATION SUBSCRIPTION my_sub TO testpub
 FOR demo_ml_user
 TYPE tcpip
 ADDRESS 'host=localhost;port=2439;'
 SCRIPT VERSION 'version1'