Question
1
Replies
152
Views
Adqura
Posted: April 28, 2016
Last activity: May 2, 2016
Closed
Interaction History Migration
Hi Everyone!
Just keen on having someones opinion on the following migration approach.
At our current client, we have to "upgrade" a Pega NBA production environment to a Pega NBA + BN environment which has in the meantime been built and configured on separate servers, from the same starting position.
Considering the amount of rule sets, data instances and database structures to be aligned, we think the best approach is to "simply" take a database backup, discard the old database, dump the new data back in and then migrate back the interaction history.
Is there any other major caveat other than aligning the interaction history (and keeping sequences aligned).
Thanks!
Moderation Team has archived post,
Close popover
This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Can you please elaborate on what you are trying to do? It looks like you have 2 systems. One that has been collecting interaction history in production. What is the other system? It is new and does not have any history? You want to stop the old production system and start the new system but want the history from the old system to become the history of the new system - is that right?
Are you just turning the old system off and the new one on (a switch?) or will you run the old system along side the new system (parallel?)
You state that the new system started as a copy of the new system...is that right? Was ruleset versioning used in updating the new system? Is an enterprise production release using ruleset migration not available to you?