Pega Data Upgrade - UPDATE APPLICATIONS SCHEMA Config

General
, , , ,
1

During the Data only upgrade, if we don’t want to run Application schema updates using update.applications.schema=false in the setupDatabase.properties and take it later with prpcUtil, what is the right configuraton & input to pass to run prpcUtils.sh or prpcUtils.bat.

There are two conflicting information.

  1. Below documentation says
  • data.schema.name=<the existing data schema>
  • import.nonpegarules.only=true

Pegasystems Documentation

  1. prpcUtil properties has a block or input upgradeApplicationsSchema and it says we can apply the changes.

############################### SETTINGS FOR UPGRADE APPLICATIONS SCHEMA #############
######################################################################################

DOWNLOAD OR APPLY DDL

Allowed values are ‘download’ and ‘apply’.

If operation is set to ‘download’ then the DDL is downloaded to upgrade.applications.schema.generated.output

If operation is set to ‘apply’ then the DDL is applied automatically

upgrade.applications.schema.operation=

PATH TO GENERATED SCHEMA

Full path to the directory where the generated schema is placed

After running upgradeApplicationsSchema the output file outputschema.zip is generated

If upgrade.applications.schema.operation is set to apply, this property is ignored

upgrade.applications.schema.generated.output=

What is the right way to do it? if we need to adopt tables changes which are cloned from OOTB tables like pc_work etc.

2

@SuhasKumar is this a question which the Modernization team might be able to answer?

3

@MadhavaRaoJ

Hi,

Both are not conflicting. The second block mentioned above, provides additional control over how the scripts are executed.

  1. For simple and straight forward approach. use below configuration.
  • data.schema.name=<the existing data schema>
  • import.nonpegarules.only=true
  • upgrade.applications.schema.operation= apply

With these settings , pega upgrade engine will generate application specific DDL and proceed with next steps.

  1. If additional control is required over the DDL changes, only DDL can be generated first using generateDDL option with below setting
  • upgrade.applications.schema.operation= generate

Manually verify the generated DDLs for changes and manually apply the DDL to target and then proceed with steps mentioned in “https://docs.pega.com/bundle/platform/page/platform/deployment/patch-update-process-data-schema-changes.html”

  • data.schema.name=<the existing data schema>
  • import.nonpegarules.only=true

Thanks

Suhas