Question

4
Replies
895
Views
 Neha Ketkar (NehaK595)
HSBC

HSBC
IN
NehaK595 Member since 2017 1 post
HSBC
Posted: May 12, 2018
Last activity: May 30, 2018
Posted: 12 May 2018 6:05 EDT
Last activity: 30 May 2018 5:13 EDT
Closed

Pega 6.2 ( Single Schema) to Pega 7(Split Schema) Upgrade

The application is being migrated from Pega 6.2 to Pega 7, i.e from single schema to Split Schema.
1. What approach must be taken to conduct testing the same ?

2. What are the challneges for data Migration

3. what are other issues / challnges observed for these upgrades .

Any help around the same would be beneficial

System Administration Upgrades
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 3 years ago
Posted: 15 May 2018 7:58 EDT
Gowrishankar Ramasamy (GOWRISHANKAR)
PEGA
Sr. Service Assurance Advisor Specialist
Pegasystems Inc.
IN

Hello, 


Please follow the below steps,


1. Install the upgrade estimator tool in Pega 6.2 to estimate the efforts to convert the legacy user interface to pega 7 supported user interface components. https://pdn.pega.com/exchange/components/upgrade-estimator-tool from this location you can down the estimator tool.


2. What approach must be taken to conduct testing the same?


                Split schema upgrade is already tested by Pega. You can take Out of Place split schema approach. Please follow the Pega7  upgrade guide to achieve this.


3. What are the challenges for Data Migration?


                 Data Migration challenges will arise if we are setting up fresh Pega7 split schema environment and move the data from 62.  We recommend to do the split schema upgrade.


4.   what are other issues / challenges observed for these upgrades?


                   Issues will vary across DB and application server vendors. Please let us know the what is the Database type and AppServer used in the deployed. We can update issues/ challenges based on that. 


Please let us know if this helps.


Thanks,


Gowrishankar.
Posted: 3 years ago
Posted: 30 May 2018 0:46 EDT
sheetal gangawane (sheetalg4338)
Capgemini India Pvt Ltd

Capgemini India Pvt Ltd
IN

Hi,


  Issues will vary across DB and application server vendors. Please let us know the what is the Database type and AppServer used in the deployed. We can update issues/ challenges based on that.


Reply: The Database type is Oracle and AppServer is WebShere. Kindly update the issues/challenges that might arise.


 
Posted: 3 years ago
Posted: 30 May 2018 1:11 EDT
Neha Ketkar (NehaK595)
HSBC

HSBC
IN

Thanks a lot Gowrishankar .


In reply to your question around database and application server vendors here are the details



The Database type is Oracle and AppServer is WebShere. any insight based on the details availble woyuld be helpful


 


Thanks,


Neha Ketkar
Posted: 3 years ago
Posted: 30 May 2018 5:13 EDT
Laurence Brannigan (LaurenceB_GCS)
PEGA
Senior Software Solutions Engineer
PEG
GB

I'm not sure I can offer specific problems that you may encounter.


I wasn't sure what version of 7 you were upgrading to. But it's worth noting that improvements have been made in the 7.4 Upgrade Guide.


Even if you are upgrading to a lower version, it would be worth cross referencing the Upgrade Guide from the version that you're going to with the 7.4 guide.


Also, there is a resume feature which will place a "resume.properties" file in you /scripts directory as it completes the various sections of the upgrade.


If you do decide to start again (i.e. you restore a database pre-upgrade) don't forget to remove the resume.properties file (otherwise the upgrade will not start from the beginning)