We have done ruleset skimming for few of the rulesets and deployed to QA. There were few parse XML rules and XML sreams rules were not getting invoked during a soap call. Once we revalidate those rules, it started working. Then we have deployed the same build to PROD but now different set of rules were failing and we had to revalidate them. Basically I need to understand why do we need to do this revalidation? why cant pega handle this smoothly? Should we do any post deployment steps like running static assembler etc. Its not consistent across environments as I had to revalidate different rules in different environment which proves the problem is not in the build but the deployment or environment issue. Can some one throw more light on this? As we see this more after the skimming, it was happening even before as well. So skimming cannot be a root cause.
What version are you using? When you see rules not being picked up properly, does the issue happen on all nodes or does the import node work fine? Do you use the Application Import wizard or prpcUtils for your deployments?
Hi - Thanks for the response. Version used is 7.1.9 and prpcutils is used for deployment. I am not very sure whether the issue is with specific node or not. As the issue was there in PROD for almost a day long, i think it should have happened in all the nodes.
You shouldn't need to revalidate and save rules when deploying to a higher environment. When new rules are imported, the appropriate caches should be invalidated and the pulse mechanism, which is Hazelcast in Pega 7.1.9, should propagate the changes to all of the nodes.