|
Any issues with migrating from 11 to 17? I am using mobilink and have a SA consolidated DB. Can both versions of dbmlsync connect to a 17 consolidated db? |
|
Basically yes. DBMLsync does not connect to the Consolidated database directly, it does connect to the remote databases and the MobiLink server so the version of the MobiLink server needs to be the same version or higher than the version of dbmlsync. There is a number of degrees of backward compatibility built in so do check out the upgrade order recommendations documented to help guide you. You are saying that v11 mlserv can connect to a v17 remote DB? If so then things should work just fine. Now all I need to do is get my v17 license key so I can test. Seems the temp key does not install mobilink. Thanks
(26 Feb '16, 15:20)
jimboidaho_g...
Replies hidden
No, he isn't saying that. Confine the doc Nick has linked to:
In my understanding, you will have to upgrade the server side (consolidated database and MobiLink server) and the client at the same time, as neither the v17 ML Server can connect with a v11 ML client nor a V11 ML server can connect with a v17 ML client. Here's a further doc quote on MobiLink upgrades:
Given that, you could upgrade the server side to v17 first and use a v12 or v16 ML server as these can be used with a v11 ML client, and then could upgrade the remote databases and ML clients to v17 lateron. When using a v12 ML server temporarily, you would have to run v12 ML server (for v11 clients) and v17 ML server (for v17 clients) in parallel. When using a v16 ML server, that one could be used with old and new clients. Note, I assume you have several (or lots) of ML clients so upgrading them will be a longer process. If there's only one ML client, you could of course "sync" the upgrade on server and remote side and upgrade both in parallel, reducing the need of an interim v12 or v16 ML server...
(27 Feb '16, 06:30)
Volker Barth
Thanks for your help.
(27 Feb '16, 10:29)
jimboidaho_g...
|
