Question

2
Replies
143
Views
neeraj.roy Member since 2014 1 post
Capgemini
Posted: 5 years ago
Last activity: 5 years 2 months ago
Closed
Solved

Upgrade 62 SP1 to Pega 7.1.8

One of the Pega customers has requested us to perform this upgrade. The customer has below circumstances -

1. We cannot perform an upgrade on existing machine which has thier application ( Pega 62 + KYC ).

2. We have been provided with a new machine having IBM WAS 8.5 which will become their instance post upgrade.

With these limitations in mind we have agreed to below approach.

Step 1. Move a clone of the Application Database Schema from machine A to machine B.

Stepl 2. Next we follow the command line upgrade methods as mentioned in the upgrade guide. Create an empty schema called UPGRADE on machine B.

Step 3. Run migrate.sh and then upgrade.sh on the UPGRADE schema to get upgraded rules schema.

Step 4. Run upgrade,sh on the cloned Application Database Schema to selectively upgrade the Data part.

Step 5. Deploy Pega 7.1.8 archive to WAS 8.5 and configure it to point approrpriate PEGARULES ( schema from step 3 ) AND PEGADATA ( schema from step 4 ).

Step 6. Upgrade KYC 7.13.1 following the upgrade guide for this Pega 7.1.8 instance

Machine B now becomes the new upgraded instance for the customer.

Can someone please validate the above approach. I'm more interested to know below -

1. Whether upgrade scripts interact with the filesystem ? In above approach we are dealing with database initially and then in Step 5 WAS comes into the picture.

2. Do we see any issues here in the approach ?

***Updated by moderator: Lochan to close 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.

Low-Code App Development Upgrades
Moderation Team has archived post
Share this page LinkedIn