Question
Hf Management Services LLC
US
Last activity: 4 May 2016 0:43 EDT
Automated Pega Deployment
Hi
We are planning to have automated Pega deployment in our project. We know that there is a shell script prpcutils.sh from where we can do deployment from commandline.
But will this shell script throw warnings like in the case of UI deployment?
Some of the warnings which are thrown through UI deployment are:
1. Old Rules are getting imported
2. List of applications which are getting affected
3. If schema updates are required?
Can the above warnings be shown through the command line shell script also?
Regards,
Krishna.
Updated: 3 May 2016 15:46 EDT
Pegasystems Inc.
US
Hi Krishna,
Could you please elaborate on what do you mean by UI deployment (only UI related rules?) and also the which PRPC version of prpcUtils script are you using?
If you are importing a product zip file or ruleset file using prpcutil.sh/bat, you can see the number of records skipped, records moved, errors and total records counts in the output log file and also warning in few cases.
Let us know if you are looking for anything specific, we can help!
Hf Management Services LLC
US
Hi We are using Pega 7.1.8 so I assume we have the latest script.
In ouput log we can see the details of records skipped, records moved.
But even before we deploy can we control what records we can skip etc?
Hf Management Services LLC
US
Hi Harish,
By UI deployment I mean the usual way of deploying from pega designer studio. Application -> Distribution -> Import
Pegasystems Inc.
US
Hi Krishna,
Thanks for the information.
In the 7.1.8 version, we can set the below condition for import process to skip or override the existing records/rule instances.
# 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.existing.instances=skip
I am not sure if we have any other ways to control or skip specific records before deployment through command line.
1. Can we know on what basis/criteria you want to skip the records before deployment?
2. If you have some purpose/criteria, can't we do it before exporting/creating a ruleset/product file ?
BR//
Harish