Query regarding software update

Pega-as-a-Service
, , , , , ,
1

Currently our Pega is using OpenShift container running Pega 8.6.1 on Oracle 19c in a on-prem setup. We are planning for upgrade to 24.1 version. We are evaluating below options. Would like to know if below methods are correct and also which would be the efficient approach.

  1. Upgrade rulebase through upgrade.bat file run and deploy the pega yaml using 24.1 image.
  2. Create the DDLs through generateddl.bat run and have DBA run it. Then deploy the pega yaml using 24.1 image.
  3. Specify “upgrade-deploy” as action in pega yaml and then do helm upgrade.
2

@SuhasKumar is this something the Modernization team could answer?

3

@MarijeSchillern and @SuhasKumar Would appreciate any insight on this? Thanks!

4

@Jey2705

Hi,

Below is the link to verify the supported infrastructure version :

Standard steps for updating Pega software in Kubernetes deployments:

To Upgrade Pega Platform with zero-downtime, refer Pega helm chart readme file l:

Thanks

Suhas

5

Hi @SuhasKumar

Sorry one last question that came up. From https://github.com/pegasystems/pega-helm-charts/blob/master/docs/upgrading-pega-deployment-zero-downtime.md, does below step means that existing data schema will be copied over to temporary data schema before migrate.sh/upgrade.sh run? Thanks!

2. Creates the target schemas and migrates the rules structure and content and data structure from the existing rules and data schemas to the new rules and temporary data schemas.

6

@Jey2705

it is temporary data schema , it will not have any data.

It will have only data structure and basic OOTB data.

The temp data schema can be used to test the upgrade before updating actual data schema.

Before testing, you need to import required data instances into temp data schema, from application. ( RAP import or deployment manager )

7

Thanks @SuhasKumar for your response. Regarding below point, can you please provide more info. My assumption was that only job that needs to be done from our end is to create the empty data schema and update the same in installer.upgrade.targetDataSchema, then running “helm upgrade release --namespace mypega” would automatically take care of all the steps. Please let me know if my understanding is correct and when below step need to be done?

Before testing, you need to import required data instances into temp data schema, from application. ( RAP import or deployment manager )

8

@Jey2705

Before testing, you need to import required data instances into temp data schema, from application. ( RAP import or deployment manager )

This is manual step. Required only if you want to sanity test the upgrade using temp schema.

Automation will not have any knowledge about client specific data instances, which client would need to sanity test the application!! (like access groups etc)

Automation will only move OOTB data instances to temp data schema.