Question
John Deere
IN
Last activity: 13 Jun 2018 3:23 EDT
Move rules schema from lower env to production
Hi,
We are upgrading our application from Pega 6.2 SP1 to Pega 7.3.1 version. We are using splits schema approach. As part of our release managment activity, we refresh our UAT env from Prod database and we are using one of the UAT schema to perform an upgrade activity. Could you let me know will there be any issue if we migrate rules schema created in UAT env to production and perform only data upgrade in production?
Thanks and Regards
Sandip
Accepted Solution
Citicorp Services India Private Limited
IN
Hello,
I hope you have gone through the Platform-support-guide https://collaborate.pega.com/discussion/prpc-5x-6x-platform-support-guide-easy-find. I suggest that analysis of infrastructure requirement is required before proceeding with the upgrade.
Yes you can refresh UAT env from Prod database, Upgrade UAT and migrate UAT rule schema to Production and perform data only update in production. However I would suggest the following.
1. Refresh the UAT env from Production database, split the schemas, before performing the upgrade in UAT. Copy the seperated rule schema from UAT to Dev environment.
2. Upgrade the Dev environment, test and fix upgrade related issues / application related issue. Once the Dev environment is good without any issues. Copy the Dev rule schema to higher environments and do the appropriate testing at each higher environment(regression, performance, UAT testing) and fix any issues and make those environment stable. (PS: You will be doing Data only upgrade for higher environments, because rule schema we are copying from lower environments).
Hello,
I hope you have gone through the Platform-support-guide https://collaborate.pega.com/discussion/prpc-5x-6x-platform-support-guide-easy-find. I suggest that analysis of infrastructure requirement is required before proceeding with the upgrade.
Yes you can refresh UAT env from Prod database, Upgrade UAT and migrate UAT rule schema to Production and perform data only update in production. However I would suggest the following.
1. Refresh the UAT env from Production database, split the schemas, before performing the upgrade in UAT. Copy the seperated rule schema from UAT to Dev environment.
2. Upgrade the Dev environment, test and fix upgrade related issues / application related issue. Once the Dev environment is good without any issues. Copy the Dev rule schema to higher environments and do the appropriate testing at each higher environment(regression, performance, UAT testing) and fix any issues and make those environment stable. (PS: You will be doing Data only upgrade for higher environments, because rule schema we are copying from lower environments).
3. Once we move to UAT, Copy the Rule schema from the next lower environment (Say Test/Staging) and perform data only update in UAT. Test the application and if there are no issues found perform step 4.
4. Copy the rule schema from UAT to Prod and perform data only upgrade in Production.
Since the upgrade is from Pega 6.2 SP1 to Pega 7.3.1, the Upgrade estimator tool will help you plan the upgrade. You can download the upgrade estimator tool from Pega Exchangehttps://pdn.pega.com/exchange/components/upgrade-estimator-tool
Please let us know if this helps,
Thanks,
Gowrishankar.
John Deere
IN
Thanks for the reply. Because of our security constraint, we can't move anything from our UAT env to SIT env and vice-a-versa. So we have upgraded our UAT env. So it has now new rule schema. We upgraded our lower env as well and whatever fixes we have done for upgrade issues, those rules we are moving to higher env's using normal 'Import' process.So from your above comments, it is quite clear that we can move rules schema from UAT env to prod env and perform data upgrade in Prod env.