Discussion
SberBank Russia
RU
Last activity: 6 Apr 2018 19:26 EDT
Migration from 6.3 to 7,1 questions
Hi all !
We are embarked to the migration an application from PRPC 6.3 to PRPC 7.1, therefore, please ALL to share the experience such migration in terms of following questions:
1. How automate the migration process ? How much manual work is there (in percentage ratio)?
2. How much do we need to re-create the UI and cases ?
3. How many iterations does the migration process takes during database migrate (with business data) ? In really
4. What are common pitfalls during migration?
Thanks.
**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.
Pegasystems Inc.
IN
Alexander,
Are you following the out-of-place split schema upgrade provide Pega7 or is it your own custom upgrade process?
If it is out-place-upgrade then all the steps are automated and there is no impact on your existing work objects.
https://collaborate.pega.com/question/how-find-pega-718-upgrade-guide-actually-i-found-it-feedback-some-pesky-pdn-behavior ( check for "Upgrading from a single-schema to splitschema" in upgrade guide)
Thanks,
Dhev
Horizon Systems
US
Hi,
The first step before estimating for the effort required is to get fixed on the scope of upgrade. Moving to Pega7 is not same for all applications. It depends on the current app setup and what the client is expecting from Pega7. At a high-level, please decide on the upgrade you are targetting:
Tolerance - as-is upgrade with very minimal changes. Not suitable for Production systems
Compliance Level-1 upgrade - upgrade all deprecated controls and take all necessary steps to make the application HTML5 compatible
Compliance Level-2 upgrade - convert all layouts and components to achieve UI responsiveness so that the App has a responsive UI to be usable across devices - laptops, mobiles etc.
Exploitation upgrade - leverage new features in Pega7 - Stage-based Case management, Data pages etc.
The efforts vary a lot based on the upgrade
Wipro Limited
CA
Hi Alexander,
For Out of the place upgrade, process is automated except the DB preparation part before upgrade and configuring properties file during upgrade process
UI and testing efforts depend on rule size and upgrade scope.It can be least for tolerance upgrade and maximum for exploitation upgrade.
Common pitfalls can be incorrect DB privileges to user. Also make sure you incorporate all custom DB changes from previous version.
Regards
Ashish
FTB
US
Hi Alex,
Hi Alex,
We need to know the business vision and upgrade road map on which Pega 7.x features most we would like to leverage on the upgraded application. Based on this the effort and type of upgrade (Tolerance/ Compliance L1 / Compliance L2 / Exploitation) will vary. To your point on how much it takes to recreate the UI, depends on whether the upgrade is targeting IE 11.x or Cross browser or Cross device compatibility. If the upgrade is targeting for Pega 7's High Availability feature, efforts will vary. Is there any Pega frame works (SI/ SD/ CPM) used in existing PRPC 6.3 application? If yes, it plays a significant role in terms of effort during upgrade.
Best Regards,
Cognizant
IN
If your P6.3 application has Oracle DB and you have plans to upgrade it from 11g to 12c then remember these...
- Pega6 does not support ORA 12c (Only 6.3 does with HFIX-9120)
- Pega7 supports ORA 12c