Discussion
EAI Systems
US
Last activity: 6 Apr 2018 19:26 EDT
Install and Migrate Approach
Below are the three approaches while upgrading 'N' applications among a rule base of 'X' applications as part of Install and Migrate approach.
Option 1 : Install and Migrate with Data Upgrade
·Fresh installation of Pega 7.X installation.
·Take RAP of ‘N’ applications in 6.X with only rules (without any data or DADT instances). Include Pega 6.X application rule as data only upgrade requires 6.X application.
·Import the RAP from 6.X to 7.X
·Run rule update wizard and other applicable steps
·Clone the 6.X schema. Perform Data only upgrade on the cloned schema by having the same as Data schema and 7.X Rules schema as the Rules schema. (Optionally clean up instances not applicable to the ‘N’ applications)
·Configure application server by pointing above upgraded data schema as Data schema and Rules schema from fresh 7.X installation as Rules schema.
Option 2 : Hybrid approach
·Fresh installation of Pega 7.X installation.
·Perform in place upgrade on 6.X environment. Perform tolerance upgrade and configure this as a baseline environment.
·Take RAP of rules and data instances for ‘N’ applications from upgraded environment.
·Import the RAP into fresh Pega 7.X installation
·Perform data migration for ‘N’ applications
Option 3 : Install and Migrate with Data Migration
·Fresh installation of Pega 7.X installation.
·Take RAP of ‘N’ applications in 6.X with rules and data instances. Do not move any Pega shipped DADTs. Validate and remove any hard-coded schema names in DADTs.
·Import the RAP from 6.X to 7.X
·Run rule update wizard and other applicable steps
·Perform data migration for ‘N’ applications
Any corrections, suggestions , improvements or alternate approaches is appreciated.
**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.
Tata Consultancy Services
IN
I am not sure about Option 3. What I understood from this post is - we are not upgrading data in option 3. Is my understanding correct? If yes, then not doing a data upgrade can cause problems.
TCS
IN
From my view, pega recommend only the below approaches. Each approaches has some uniqueness to handle special situations. Hope you application need will fit one of these. No need to go for new approaches.
Option 1 : In-place upgrade
Option 2 : Out-Of-Place ( with One / Two Database) Upgrade
Option 3 : Lift & Shift Upgrade
Option 4 : Install & Upgrade
Tata Consultancy Services
IN
Hi Selva,
The four approaches mentioned are the approaches for Pega 7 upgrade. However, Pega does not recommend InPlace Upgrade.
Regards,
Sumeet
Updated: 12 May 2016 6:49 EDT
Cognizant
IN
Option 1 : In-place upgrade is performed only in lower environments like DEV under special circumstances when the other 3 options won't help.
Say we have a large application with huge number of rules (even after doing a major skim and purging all 'Major-1' rule set versions); the first step in the upgrade RULES MIGRATION might fail. This step would require creation of large .dmp files and then bulk loading them into the new empty-rules-schema; this could fail mid-process. Repeated attempts might not help. So there is no other option but to perform an in-place upgrade. Running a migrate.sh for performing a rules migrations is not required hence we will be skipping any *.dmp file creation/loading in the upgrade process.
## Disclaimers ##
There is no specification for calling an application as huge. Typically an application will not have more than 50K rules.
There is no specification for calling a *.dmp file as huge. Usually these files do not cross 1GB.