Question
Unitedhealth Group
IN
Last activity: 22 Feb 2017 10:50 EST
Automated Deployment - Application rule not getting overridden
Hi ,
We are using the scripts from Pegasystems for performing automated deployments using a tool named XL Deploy. All rules / data instances are getting migated to a target environment but the Application rule is not getting overridden. If we export the archive manually using import wizard, the application rule is getting overridden.
Note that we are explicitly including the Rule-Application instance in the 'Individual instances to include' section of the Product rule.
We can see the following entries in the log:
[pega:propertyparser] import.existing.instances=override
[java] 2017-01-09 06:19:14,641 [ STANDARD] [ ] ( internal.util.MoveLog) INFO - Total instances in archive: 5
[java] 2017-01-09 06:19:14,641 [ STANDARD] [ ] ( internal.util.MoveLog) INFO - Instances imported: 5
Any clue on why the application rule is not getting overridden?
Regards,
Pardha
Pegasystems Inc.
IN
Hello,
Can you please help me understand how this tool XL deploy works ?
Is it similar to how the OOTB import works ? What is the logic here and how it determine whether a particular rule can be overwritten or not ?
Asurion
US
In our case, we had changed the ruleset associated with the application rule and what we have observed is- if we do manual deployment , we get an option to override this rule . So we used t manual deployment of this rule. I am not sure if there is any option or param to be passed to automated scripts to achieve this.
Pegasystems Inc.
US
It would help us if you could provide some specifics about how XL Deploy works and also provided log files for our review.
Pegasystems Inc.
US
Have you tested the automated process - RAP,arguments, source and target using OOTB prpcUtils and PRPCServiceUtils? Once done, then start out by mapping the corresponding segments for XL deploy tool.