Question
Bank Of America
IN
Last activity: 7 Aug 2023 10:32 EDT
When Skimming is performed do application still need to hold the old ruleBase during upgrade ?
hi Team,
we are starting an upgrade journey for our CLM Application.
As part of process we are doing the ruleset skimming of all rulesets part of the application.
Do upgrade process clean up the old code base specific to the Application, if so when it will do.
what do cleaup.sh utility do ? does it just works for the pega rule base deletion.
what should app team need to do to remove old code base part of the implementation layer.
what will be risk involved if we do a clean up or if we don't do a clean up.
Rule Resolution definitely play role during run time based on Application rule configuration and we can control the rule stack, but still do we need to maintain old base.
Note :I am complete new to upgrade hence posting this question.
Thanks
Dileep.N
***Edited by Moderator Marissa to change Product tag Pega Onboarding for Financial Services to Pega Client Lifecycle Management for Financial Services***
Updated: 7 Dec 2020 16:14 EST
Pegasystems Inc.
IN
By default Pega build comes with the cleanup.bat / cleanup.sh scripts to remove the ruleset versions older than the current version you were upgrading from.
Please refer the upgrade guide for pega 7.3 for more information.
https://community.pega.com/knowledgebase/documents/pega-73-platform-upgrade-guide.
Depending on the pega version you are planning to upgrade to you can download and refer the corresponding pega platform versions upgrade guide from below link https://community.pega.com/knowledgebase/products/platform/deploy
Here is the snippet from the upgrade guide:
In most cases, removing older rules decreases the overall upgrade time. Running the cleanup script permanently removes rules older than the current version from which you are upgrading. For example, if you are upgrading from PRPC 6.2 SP2 (06-02-20) to 7.3, cleanup removes rules of version 06-01-99 and older. Run the cleanup.bat or cleanup.sh script to generate an SQL script to clean up the rulebase. You can either have the cleanup.bat or cleanup.sh script automatically apply the SQL script, or have your database administrator make the changes.
Once the scripts get generated, pass in the appropriate version number to delete those corresponding ruleset. I hope you would not want to delete all the versions prior to 7.2.
By default Pega build comes with the cleanup.bat / cleanup.sh scripts to remove the ruleset versions older than the current version you were upgrading from.
Please refer the upgrade guide for pega 7.3 for more information.
https://community.pega.com/knowledgebase/documents/pega-73-platform-upgrade-guide.
Depending on the pega version you are planning to upgrade to you can download and refer the corresponding pega platform versions upgrade guide from below link https://community.pega.com/knowledgebase/products/platform/deploy
Here is the snippet from the upgrade guide:
In most cases, removing older rules decreases the overall upgrade time. Running the cleanup script permanently removes rules older than the current version from which you are upgrading. For example, if you are upgrading from PRPC 6.2 SP2 (06-02-20) to 7.3, cleanup removes rules of version 06-01-99 and older. Run the cleanup.bat or cleanup.sh script to generate an SQL script to clean up the rulebase. You can either have the cleanup.bat or cleanup.sh script automatically apply the SQL script, or have your database administrator make the changes.
Once the scripts get generated, pass in the appropriate version number to delete those corresponding ruleset. I hope you would not want to delete all the versions prior to 7.2.
For your application implementation layer specific ruleset skimming is recommended.
Refer the below link for more details https://community.pega.com/knowledgebase/articles/how-skim-compress-merge-copy-and-delete-rulesets-ruleset-maintenance-wizard
Bank Of America
IN
hi Sushanth,
Thank for responding ,we have already completed skimming ,so my intention is can we clean up our Application layer rules as well like
AppA:01-01-01-this is old
AppA:03-01-01-this is major skimmed
now how to delete theAppA01-01-01 ruleset contents.