MI upgrade from 2.5 to 7.1: backcompatible?
We consider upgrading from MI2.5 SP14 to MI7.1 when it is released. Today, we have about 100 PDAs distributed to our partners, running a generic sync application.
As I have understood, we must also upgrade the MI clients as soon as we have upgraded the server because the server is non-backcompatible with MI2.5 clients?As far as I can see there will be some huge logistics problems as all PDAs are distributed to partners all around.
Anyone who know if the only solution is to install a completely new MI7.1 server and then switch clients to the new server one after another? This way we will have almost no downtime throughot the upgrading-process, but is this a preferred solution?
Oliver Kaluscha replied
in my understanding you have to switch the Client to MI7.1 if you switch the Middleware Server to MI7.1. Well, because it is not available yet we have not really seen it - but it is really unlikely that a MI2.5 or MI7.1 client is running with a MI7.1 server. You can upgrade a Middleware Server in the normal version line and have clients that are on an older patch level, but a complete switch to a new version requests a switch of clients as well. Especially because a lot of the architekture inside MI has changed. So just to say this again, it is in my understanding not possible to run a MI2.5 or MI7.0 client against a MI7.1 Server.
I was doing some upgrade from MI2.1 to MI2.5 and I will do some from MI2.5 to MI7.1 as soon as 7.1 is available. All Customers plan a smooth update. This means, they will have two servers - well, these will be two virtual servers running on the same machine, but that is another point. Ok, so they have two servers running with the same Backend. One is the actual live MI2.5 Server with all users, the other one will be the MI7.1 server. Both Middleware servers have the most up to date data from the backend. The MI2.5 client continues to run with its old server - sp nothing has changed for the user. Then they start the upgrade in chunks of 5 to 10 devides to the new middleware. Fom the logistic handable and it gives them the ability to see, if the new system behaves as expected. Switching in a big bang is really a nightmare for the administrator. Setting up several 100 devices from one second to the next and then guarante that the new system is completely stable from the start - I think this is not really the thing you would like.
Another question: most changes are around SmartSync and the UI in MI7.1. So if you want to benefit most from MI7.1 you have to upgrade your App as well I think. This is another point where it would make sence to switch in chunks - because your actual App is running stable and with the smooth method you will have time to learn the more user you have on the system.
I hope this helped to answer your question.