On Premise Upgrade checklist from Pega 8.2.5 to Pega 8.4.x
We are on premise and have one mobile application as well running in hybrid client.
We recently upgraded from Pega 731 to Pega 825.We had few hiccups in performances as there are some configurations that was not explicitly mentioned in Pega documentations. E.g.: MaxDOP, Elastic Search introduction and gzip parameter at server side, requestor passivation issue, etc.,
We are planning for our next upgrade to Pega 8.4.x along with UI-Kit from 9 to 14 and we are looking for your experiences on the same. Like issues faced during upgrade, any additional configurations at Server or DB (any infra change), open issues (other than known issues from Pega release notes), any involvement of Pega needed before upgrade(for assessment on existing infra), key challenges, lesson learnt etc.,
***Edited by Moderator Marissa to update Support Case Details: SR-88101; changed Discussion to Question***
Below are some helpful community links which can help you in doing the upgrade assessment.
Refer Platform Support Guide for assessment of Infrastructure:For tested and supported Operating Systems, Databases, Applications Servers, Client Operating Systems, Browsers and Integration Service Components with pega release.
Thanks for your reply, we also want to know the PEGA recommendation's for Upgrade project (Upgrading from Pega 827 To Pega 841) when we have active development is going on.
1. Whether skimming should be done by which team?
2. When the code should be retrofitted ? Dev & Upgrade team's code base?
3. Until the code is retrofitted/merge happens, will the upgrade changes should be part of branches? Could you please suggest the best approach?