Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in August and this forum will be retired.

We are using version 12 Mobilink and we have a production environment and a test environment. Each environment consists of a webserver, DB, and a Mobilink server.

We took a copy of the production DB and Mobilink scripts and copied them into our test environment. We then made a number of changes to the database to accommodate some new types of work that our product will support. This required some minor changes to the DB (added a few tables and also added some fields to existing tables) - nothing major. We then created a new Mobilink Synchronization Model and modified our existing ones. Everything is working just fine in our test environment. My question is - is there an easy way to get the Mobilink changes into production without hand doing everything like we did in the test environment? I'm fine with making all the DB changes in the database server (we would do that first) but it would be awesome to just be able to right click on the new Synchronization Model and click "copy" and then paste it into the production Mobilink server. Kind of like you can do with SQL Anywhere tables.

Is there any type of backup / restore option for Mobilink that might make this easier to deploy to production? Looking to somehow copy these Synchronization models up to production.


asked 19 Feb '18, 10:50

Codecranker's gravatar image

accept rate: 20%

Hm, personally, I would always use SQL scripts to do the upgrades, both on the database schema and the ML scripts, and manage those via source code control. By that, I can easily make sure that updates in the test and production environment are identical.

That being said, I have not used Sync Models myself, so I hope there is a way to generate such scripts automatically...

(19 Feb '18, 15:33) Volker Barth
Replies hidden

> a way to generate such scripts automatically

If the scripts already exist inside the test consolidated database, the best approach is to UNLOAD SELECT ... TO *.sql files to extract the scripts into text files which can then be used to load them into the production database.

...the reality is a bit more complicated than that, of course.

I agree with Volker, however, that *.sql files are better than the MobiLink models for maintaining and enhancing synchronization setups. With scripts you are aware of (and have control of) every aspect of synchronization, PLUS scripts allow customizations the model feature can't handle.

The downside is, scripts are harder to construct than the models, when starting out. Plus, with scripts you must understand every aspect of synchronization, whereas with models you can skip over many of the details.

(20 Feb '18, 07:21) Breck Carter
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 19 Feb '18, 10:50

question was seen: 811 times

last updated: 20 Feb '18, 07:21