Handle Aged Updates, schema change in deployment using prpcServiceUtils
In Pega 7.2.2, when we use prpcServiceUtils for deployment, aged updates are going in and replacing newer rules. Is there a way to handle that from command line? And we have no chance to skip any Schema Change, then after the import we must change it manually, it hindert our release automation process.
Is there any possibilty to check the product content when we use the prpcserviceutil.sh?
Thank you very much in Advance!
Best Regards
W&W
DE
because we want to realize an one-click deployment, but this approach was criticized, because by comparison with the pega import wizard, we could not
1. check the product content
2. skip Schema change
3. skip import aged updates
so back to my question, could we set them when we use the prpcserviceutil for deployment?
JPMorgan Chase & Company
US
Hi,
prpcServiceUtils.properties properties I don't see these option, usually user's maintain schema changes in separately and move the changes.
Updated: 27 Dec 2017 8:22 EST
Pegasystems Inc.
US
If schema changes are needed then they should be done before the import if you don't want the import to do them automatically.
In 7.3.1 there is an option to bypass even looking at the schema changes that are part of the RAP. This option is not available in 7.2.2.
#Allows bypassing schema import. The schema changes (DDL) if applied manually, set this flag to true to skip schema. Default is false
import.bypassSchema=
To skip non-rule resolved rules you should be able to use the import.existingInstances option.
If schema changes are needed then they should be done before the import if you don't want the import to do them automatically.
In 7.3.1 there is an option to bypass even looking at the schema changes that are part of the RAP. This option is not available in 7.2.2.
#Allows bypassing schema import. The schema changes (DDL) if applied manually, set this flag to true to skip schema. Default is false
import.bypassSchema=
To skip non-rule resolved rules you should be able to use the import.existingInstances option.
# Handling for existing instances
# override - Replace instances that already exist in different RuleSets and/or Versions.
# skip - Skip the instances that already exist in different RuleSets and/or Versions.
# if unset, the import will fail if existing instances are encountered
import.existingInstances=skip
# if unset, the import will fail if existing instances are encountered
import.existingInstances=skip
W&W
DE
thanks for your reply.
i have still a question about the setting "import.existingInstances=skip". This property was set as "skip" by default, it means Skip instances that already exist in different rulesets or versions. But how could the aged updates be verified/handelt? Or it means the aged update would not be imported with this settings?