Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.0 » MobiLink - Getting Started » MobiLink Tutorials » Tutorial: Using MobiLink with an Adaptive Server Enterprise consolidated database


Lesson 5: Deploy the synchronization model

The Deploy Synchronization Model Wizard allows you to deploy the consolidated database and remote database. You can deploy each of these individually or you can deploy both of them. The Deploy Synchronization Model Wizard takes you through the steps of configuring options for deployment.

 To deploy the synchronization model
  1. In the left pane of Sybase Central under MobiLink 12, expand ase_project, Synchronization Models and then sync_ase.

  2. From the File menu, choose Deploy.

  3. Click Specify The Deployment Details For One Or More Of The Following and select Consolidated Database, Remote Database And Synchronization Client, and MobiLink Server. Click Next.

  4. Perform the following tasks on the Consolidated Database Deployment Destination page:

    1. Check Save Changes To The Following SQL File and accept the default location for the file.

      MobiLink generates a .sql file that makes changes to the consolidated database to set up for synchronization. You can examine the .sql file later and make your own changes. Then, you must run the .sql file yourself.

    2. Immediately apply the changes to the consolidated database.

      Check Connect To The Consolidated Database To Directly Apply The Changes.

    3. Select the ase_cons consolidated database from the list .

    4. Click Next.

    A prompt appears asking if you want to create the consolidated directory. Click Yes.

  5. Click New SQL Anywhere Database, and then click Next.

  6. Perform the following tasks on the New SQL Anywhere Remote Database page:

    1. Check the Make A Command File And A SQL File With Commands To Create The Database option.

      Selecting this option generates another .sql file with the commands to set up the remote database with all schema and synchronization information.

    2. Accept the default location in the SQL File field.

    3. Check the Create A Remote SQL Anywhere Database option.

      You must generate a new remote database and then run the .sql file against it If you do not check this option This option allows you to examine the .sql file later and make your own changes.

    4. Accept the default location in the SQL Anywhere Database File field.

    5. Click Next.

    A prompt appears asking if you want to create the remote directory. Click Yes.

  7. Perform the following tasks on the MobiLink User and Subscription page:

    1. In the What User Name Do You Want To Use For Connecting To The MobiLink Server field, type ase_remote.

    2. In the What Password Do You Want To Use field, type ase_pass.

    3. Click Next.

  8. Select TCP/IP and type 2439 in the Port field. Click Next.

  9. Type localhost in the Host field. Click Next.

    Alternatively, you can type your computer name or IP address, the name or IP address of another network server you want to use, or other client stream options.

  10. Click Next on the Client Stream Parameters, MobiLink Server Stream Parameters and Verbosity For MobiLink Server pages to accept all default settings.

  11. Type ase_mlsrv in the What Name Do You Want To Give The MobiLink Server field. Click Next.

    A message appears asking if you want to create the mlsrv directory. Click Yes.

  12. Choose a verbosity setting for the remote synchronization client and use the default file name of the remote database log file. Click Next.

  13. Click Finish.

  14. Click Close.

Your consolidated database is fully configured for synchronization with many remote clients, and you have successfully deployed one remote client. If you want to deploy other remote clients, you can run this wizard again, making sure to create a new MobiLink user and opt out of deploying the consolidated database and MobiLink server. Since these have already been deployed, all you need to do is deploy other remote synchronization clients.

 Further reading