Posted: 10 Jan 2017 1:15 EST Last activity: 6 Apr 2018 19:26 EDT
Data Schema Upgrade for X out of Y applications
Lets take a scenario where we are updating multiple applications (say Y) hosted on a 7.1.6 environment and we do not want to update all of the Y applications at the same time (say we only want to update X applications - so users for these X applications will continue to use the new Production environment, whereas users for the rest of the applications will continue to use the old Prod environment).
In such a scenario, how do we handle the data update as and when we decide to migrate the rest of the applications (Y-X) to the new Production environment (by then users in both environments would have worked in their respective applications)
Any inputs would be highly appreciated
Thanks in advance.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
When you initially move X applications, just clone the environment and update, this way you will have two set of environment in production (one running in 7.1.6 another in 7.2.2), X applications can be accessed only from 7.2.2 server and Y-X applications can be accessed only from 7.1.6 server.
Now in some later point of time you want to update Y-X applications to 7.2.2, in that case you can create a RAP and package Y-X applications (from 7.1.6) into that and import it into 7.2.2 server. In this way we can perform this upgrade.
Note: If we package data instances into RAP, the size might be huge, in that case we might need to create multiple RAPs containing blocks of data instances.
When you say "create a RAP and package Y-X applications (from 7.1.6) into that and import it into 7.2.2 server" - Are you talking about packaging work objects and associated data instances (assignments, attachments etc) and move them from 7.1.6 Prod to the 7.2.2 prod server?
Yes, I am talking about packaging rule as well as data instances, but you need to perform a proper assessment before doing this. This method works best if your DB size is moderate and less number of cases present.