Last activity: 18 Sep 2015 9:09 EDT
Does anyone know if Pega 7 can merge multiple RAPs and create a single RAP?
I have a requirement to merge Rule Admin Products (RAPs) for all sprint releases. I have a list of JAR files (around 20) and need to merge them to have a single JAR file. Doing this manually by copying entries is a tedious process. Checking if anyone knows a way to do this in Pega 7 by combining all RAP Jars and create a single one. Appreciate if any feedback.
What is the purpose of merging JAR files?
Are you trying to merge rules scatered in multiple rule-sets into one unified rule-set? If so, try "Skim a RuleSet" or "Copy/Merge RuleSet" under the Designer Stuido > System > Refactor > RuleSets
Thanks for the reply Chunzhi.
Not really. These are related to data only RAPs.
For e.g., assume we have sprint releases and project has 16 sprints. Each sprint, we deploy Rules JAR and Data JAR to System Testing.
At the end of the release, we have 16 Rules JARs and 16 data JARs.
I want to combine all 16 data JARs for example, and create a single JAR. Above refactoring doesn't help for this matter.
So you are trying to import all data JARs in one shot, and 16 Rule JARs one by one?
Exactly. For Rules, I am planning to migrate the whole rules schema.
>I am planning to migrate the whole rules schema.
If it is ture, isn't it safe to migrate the whole data schema also?
You can't migrate whole data schema in a real world system, specially to a production system.
>You can't migrate whole data schema in a real world system, specially to a production system.
I agree. However I couldn't understand what is the value of merging data JARs that are apparently associated with diferrent set of rules.
how do you make it safe to migrate the whole rules schema from a non-production environment to production?
how do you make it safe to migrate any rules or data having dependencies that are not included in a single package or properly managed a set of packages?
What if combined data JAR import fails in the middle of import process, isn't it going to be more difficult to troubleshoot?
This is a latest technology Pega has introduced, still early days. It is related to high availability.
I don't think High Availability Admin Guide sugests in any manner the approach you are trying to take.
Could you refer any support articles that backs up your migration procedure is a good practice to achieve high availability?
Create a new R-A-P include all things you need to export to a JAR, and use import/export tool to create new JAR, if you really want to have a single data JAR archive.
It's a bit ironic, your title says
>>> merge multiple RAPs and create a single RAP?
but your details say you want to merge the jars that those RAPS (rule-admin-products) produce rather than actually merge the RAPs, but as just suggested by Chunzhi, merging the RAPs may be an easier way.
More specifically, if you have n RAPs that respectively specify rule-application sets An, ruleset lists Rn, and specific key lists Kn, it wouldn't be too hard to write an activity (extra credit: do it with data-transforms instead of an activity !!) that uses obj-browse to collect all n RAPs and produce a new total-RAP that specifies the union of An, Rn, and Kn. Then you click the "create product" button on the total-RAP to get your single merged JAR.
do the OOTB wizard Designer Studio Application --> Distribution --> Package helps? please share your comments, Thank you!
p.s: fyi: also please refer OOTB RULE-OBJ-ACTIVITY RULE-ADMIN-PRODUCT EXPORTRAP
Thanks all for your feedback.