Pega platform upgrade - Pega 7.x to Pega 8.x with specific app and db servers
Hi Team - For our client we need to perform Pega upgrades. We could not find the specific documents (with below combinations) in PDN. Request you to guide us in providing 4 documents /Upgrade guides each to these specific combinations.
1. On-Premise to On-Premise | App server - Web logic Proprietary information hidden | DB - Oracle Proprietary information hidden | From Pega 7.1.9 to Pega 8.5
2. On-Premise to On-Premise | App server - Web logic Proprietary information hidden | DB - Oracle Proprietary information hidden | From Pega 7.1.9 to Pega 8.6
3. On-Premise to Azure (cloud) | App server - Web logic Proprietary information hidden | DB – DB2 | From Pega 7.1.9 to Pega 8.5
4. On-Premise to Azure (cloud) | App server - Web logic Proprietary information hidden | DB – DB2 | From Pega 7.1.9 to Pega 8.6
Pegasystems Inc.
IN
Can you complete the form in below mentioned link. It will provide you documents/steps for the upgrade.
https://community.pega.com/upgrade
Thank you
Tech Mahindra Ltd
CA
@patwk Hi Kanchan, Thanks for the prompt reply. I filled that form, but it says no specific doc available. Could you please guide. Attached is the image
Pegasystems Inc.
IN
Could you please refer to the below link:
Also, please raise a Support request if you need further help on this
Thank you
Pegasystems Inc.
US
Hi @AnantaKiran,
If you open a Support ticket please reference this thread and also let us know the ID so that we may track for you.
Thank you!
Tech Mahindra Ltd
CA
@MarissaRogers , @patwk - Thanks both. Basic question - While i'm trying to check all those articles, any quick response on below question would be of real help.
If we need to migrate from On-Premise to On-Premise | App server - Web logic Proprietary information hidden | DB - Oracle Proprietary information hidden | From Pega 7.1.9 to Pega 8.6 ?
From below approaches which one we need to take ? and supporting guides please. Option 1 : Existing Pega 7.1.9 --> upgrade tools --> upgrade to Pega 8.6 and run any post upgrade steps ? Option 2 : Take fresh Pega 8.6 --> Migrate RAPs , etc other rules from Pega 7.1.9 to Pega 8.1.6 --> run any post upgrade steps ?
Thanks in advance
Pegasystems Inc.
IN
Option 1 (In-place Upgrade) will have a longer production downtime as you would need to upgrade both rules and data schema during the downtime. Rules upgrade takes significantly longer time than data upgrade.
Option 2(out-of-place upgrade) allows you to upgrade rules while your production users continue to use the application. The real downtime is needed to point to upgraded rules schema and for data only upgrade. It will enable you to have a shorter code freeze window by having parallel development in order to be able to send production releases in current system and make upgrade fixes in another system. Merging the code may be another task. A longer code freeze may help you minimize the effort for parallel development and code merge tasks.
Option 1 is preferable if you can afford longer downtime and longer code freeze (as you wouldn't be able to deploy code from upgraded 8.6 dev system to Pega 7.1.9 production system). Please note you may need more time to fix application upgrade issues if you've a complex application with a lot of customizations.
Option 2 is preferable if you're willing to carry out additional steps to keep the downtime window and code freeze duration shorter.
Whichever option you choose, you should follow the same in the lower environments as well as production because you will be better prepared for go live.
Pleaser refer below links for the supporting documentation
Option 1 (In-place Upgrade) will have a longer production downtime as you would need to upgrade both rules and data schema during the downtime. Rules upgrade takes significantly longer time than data upgrade.
Option 2(out-of-place upgrade) allows you to upgrade rules while your production users continue to use the application. The real downtime is needed to point to upgraded rules schema and for data only upgrade. It will enable you to have a shorter code freeze window by having parallel development in order to be able to send production releases in current system and make upgrade fixes in another system. Merging the code may be another task. A longer code freeze may help you minimize the effort for parallel development and code merge tasks.
Option 1 is preferable if you can afford longer downtime and longer code freeze (as you wouldn't be able to deploy code from upgraded 8.6 dev system to Pega 7.1.9 production system). Please note you may need more time to fix application upgrade issues if you've a complex application with a lot of customizations.
Option 2 is preferable if you're willing to carry out additional steps to keep the downtime window and code freeze duration shorter.
Whichever option you choose, you should follow the same in the lower environments as well as production because you will be better prepared for go live.
Pleaser refer below links for the supporting documentation
Thanks