When you deploy a model, directories and files are optionally created in the location you chose on the first page of the Create Synchronization Model Wizard. The files and directories are named according to the model name you chose at that time.
Assume you named your model MyModel and saved it under c:\SyncModels. Depending on the deployment options you chose, you might have the following files:
|Directories (based on example name and location)||Description and contents (based on example name)|
|c:\SyncModels||Contains your model file, saved as MyModel.mlsm.|
|c:\SyncModels\MyModel||Contains folders holding your deployment files.|
Contains deployment files for the consolidated database:
Contains deployment files for the MobiLink server:
Contains deployment files for the remote databases:
You must run the batch files that are created by the Deploy Synchronization Model Wizard from the command line, and you must include connection information. You may need to create ODBC data sources before running these batch files.
If you have not yet run MobiLink setup scripts on consolidated database, run them before deploying.
When you ran the Deploy Synchronization Model Wizard, if you chose to create a file to run later (on the Consolidated Database Deployment Destination page), you must run the batch file that is located in the consolidated sub-folder of your model. This file creates all the objects you chose to have created in the consolidated database, including synchronization scripts, shadow tables, and triggers. It can also register MobiLink users in the consolidated database.
To run this file, navigate to the consolidated directory and run the file that ends with _consolidated.bat. You must include connection information. For example, run:
When you ran the Deploy Synchronization Model Wizard, if you chose to create a file to run later (on the New SQL Anywhere Remote Database page or New UltraLite Remote Database page), you must run the batch file in the remote directory. This file creates all the objects you chose to have created in the remote database, including tables, publications, subscriptions, and MobiLink users.
To run this file, navigate to the remote directory and run the file that ends with _remote.bat. For example, run:
You are prompted for a password if you are using an existing remote database.
Start the MobiLink server by running mlsrv\MyModel_mlsrv.bat. If you set up server-initiated synchronization, this also starts the Notifier. You must include connection information. For example, run:
For a SQL Anywhere remote database:
Grant REMOTE DBA authority to a user other than DBA (recommended). For example, execute the following in Interactive SQL:
GRANT REMOTE DBA TO userid, IDENTIFIED BY password
Connect as the user with REMOTE DBA authority.
Start the remote database that is located in the remote directory. For example, run:
Start dbmlsync, the SQL Anywhere MobiLink client. Run the file that ends with _dbmlsync.bat in the remote directory. You must include connection information. For example, run:
For an UltraLite remote database:
To test your synchronization, run the file that ends with _ulsync.bat in the remote directory.
Alternatively, run your UltraLite application.
If you set up server-initiated synchronization, you need to perform a first synchronization and then start the Listener. The first synchronization is required to create a remote ID file. To start the Listener, run the file that ends with _dblsn.bat in the remote directory. For example, run:
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|