Merging two separate Pega Applications into one application.
We are planning to merge two separate Pega applications which are Installed in two separate servers into a one infrastructure. Planning to merge/migrate Pega RULES and Peda DATA schemas. Planning to introduce a common application for enterprise layer and will be reused
Both the applications are in production and on same Pega version.
Have to migrate Data instances , Work Objects, Assignments , Attachments etc.. (Due to current Case volume Package Work Objects wizard may not be helpful)
Really appreciate if you could share any approaches or things to consider in merging applications.
Thanks,
Pegasystems Inc.
IN
High Level plan can be as follow:
Merge or move smaller application ( in terms of production data) into Bigger application.
For Rules:
1. Take Rules RAP from source and import into target.
For Data:
1. Identify the work and history tables. Move entire tables to target.
2.Identify the data/rows to be moved from common tables. (like attachment tables, assignment tables). In target migrate to backup table first then merge with existing table. While merging, if the there are primary key conflicts, decision to be taken which records should be discarded and which needs to be preserved.
Note: This is difficult step and requires extensive application knowledge.
3. Identify DSS and other environment configuration which requires to be moved. RAP can be used to move these configurations.
To copy/move data between source and target database, Based on the DBMS ( DB type like oracle etc), use DB tools like export/dump. Third party tools can be explored to move the data.
Approach should be implemented in lower environments and tested properly for all scenarios.