Both source and target points to new rule schema
User planning to upgrade from PRPC v7.1.7 Split schema to PRPC v7.1.9 Split schema using Out Of Place upgrade using the new RULES schema.
User was confused with the implementation of the upgrade process and trying to follow the below steps:
1. Copy old rule schema to new rule schema
2. Upgrade the new rule schema
3. Generate and apply rule schema objects
4. Bring PRPC application down
5. Upgrade the data schema
6. Migrate to new rule schema [where migrateSystem.properties modified source points to new rule schema and target points to original rule schema]
1. As per Pega719_UpgradeGuide.pdf page 72 both pega.source.rules.schema, pega.target.rules.schema points to new rule schema, is it correct?
2. If the answer is yes, how to migrate new rule schema to old rule schema?
The user is upgrading from PEGA 7.1.7 Split schema to PEGA 7.1.9 Split schema with one database.
The process will create a new rules schema to perform the upgrade to decrease the System down time and finally we will use the new rules schema and discard the old rules schema from database.
- Data Schema – your current schema
- Rules Schema – your current rules schema
- New Rules Schema – your newly created rules schema
- Create one blank schema, for example new rules schema.
- Use the migrate script to migrate the current rules schema to the new rules schema as explained in “Migrating the existing rules schema in a split-schema upgrade with one database” in page 69.
- Upgrade the new rules schema, either use the Installation and Upgrade Assistant or the upgrade.bat/sh script as explained in “Upgrading the migrated rules schema” in page 71.
- Now you need to follow “Migrating to the new rules schema with one database” step with same properties as explained in document by pointing both source and target rules schema to new rules schema with different properties in migrateSystem.properties as explained in document.
- Bring PRPC application down
- Upgrade the Data Schema and apply any DDL changes as explained in “Upgrading the data schema from the command line” in page 83.
- Reconfigure the application server to use Data schema and New Rules schema.
- Finally discard the Rules Schema as it is useless.
- In the first rules migrate step, copy the rules from original schema to new rules schema.
- In the rules upgrade step, we will create the required rules of the newer version.
- In the second rules migrate step, we will generate the required trigger links for the upgraded rules schema and then apply this trigger links with the original schema with the help of “pega.rules.objects.generate=true” and “pega.rules.objects.apply=true” properties. In this step both the source and target rules schema should point to new rules schema.
- This is the reason behind the second migrate step on the new rules schema and it is not the defect in the documentation.
0% found this useful