The client always initiates MobiLink synchronization. For SQL Anywhere clients, synchronization can be initiated using the dbmlsync utility, the dbmlsync API or the SQL SYNCHRONIZE statement. All share similar semantics but offer different interfaces to synchronization and different abilities to integrate synchronization with your own applications.
There are many options available to customize synchronization behavior, however, a few stand out because they are required for virtually any synchronization. These are discussed below.
The -c option lets you specify connection parameters that control how dbmlsync will connect to the remote database. This information is not required when using the SQL synchronize statement because the connection information is taken from the database connection that is executing the statement.
The -s or Subscription option allows you to specify which subscription defined in the remote database will be synchronized.
The CommunicationAddress and CommunicationType extended options let you specify network protocol options that determine how dbmlsync will connect with the MobiLink server during synchronization.
The Script Version clause on the CREATE SYNCHRONIZATION SUBSCRIPTION SQL statement lets you specify the script version to be used when synchronizing a subscription. The script version determines which scripts will be used by the MobiLink Server to control and process the synchronization.
Security considerations with role-based access control and synchronization
dbmlsync extended options
Transaction log files
Concurrency during synchronization
Synchronization initiation from an application
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|