Question
Declare Expression stopped working after R-A-P import
Hi,
Yesterday we imported a R-A-P into another environment and Declare Expression stopped working right after the import. We don't know why this happened, but we restored the database back to original state and re-imported the same R-A-P and the issue disappeared (Declare Expression started to work).
Usually, in our migration process, we import R-A-P, stop the app server, delete the Marker file, and then start the app server. After the app server gets up and running, we log in to Designer Studio to run the "Static Assembler" tool so PRPC pre-assembles all the developed new rule instances to improve the performance. However yesterday, we closed the Designer Studio window before the Rule Assembly completes by mistake. I do not believe just closing browser would stop the Rule Assembly process because this is happening at the server side. Anyways, this Declare Expression not working issue is very critical and we want to avoid it in production environment in the future, so here are my questions.
1. Could this Declare Expression stopped working issue possibly have anything to do with closing browser while Static Assembler was running? Or this assumption does not make sense and it should come from something else.
Hi,
Yesterday we imported a R-A-P into another environment and Declare Expression stopped working right after the import. We don't know why this happened, but we restored the database back to original state and re-imported the same R-A-P and the issue disappeared (Declare Expression started to work).
Usually, in our migration process, we import R-A-P, stop the app server, delete the Marker file, and then start the app server. After the app server gets up and running, we log in to Designer Studio to run the "Static Assembler" tool so PRPC pre-assembles all the developed new rule instances to improve the performance. However yesterday, we closed the Designer Studio window before the Rule Assembly completes by mistake. I do not believe just closing browser would stop the Rule Assembly process because this is happening at the server side. Anyways, this Declare Expression not working issue is very critical and we want to avoid it in production environment in the future, so here are my questions.
1. Could this Declare Expression stopped working issue possibly have anything to do with closing browser while Static Assembler was running? Or this assumption does not make sense and it should come from something else.
2. We delete Marker file every time we import a R-A-P and I believe this will clear all cache and Rule Assembly is required since then. To prevent from business users experiencing FUA, we run this Static Assembler tool but is this a standard practice in production environment? Is Static Assembler recommended after R-A-P import or not recommended for any reasons?
Thanks,
Accepted Solution
We have found out that Declare Expression not working issue was not caused by Rule Assembler, but how we imported. We have imported a R-A-P that includes Implementation layer prior to R-A-P that includes Framework layer. Some rule instances are referencing a Framework class that did not exist when imported.
For Rule Assembler, I will use this tool even for production environment as it will reduce the first log in business user's stress.
Thanks,
Hi,
Thanks for posting on PSC.
As per my understanding of Static Assembler,
- All rules are flushed from the rule caches each time it runs, thus all rules re-populated on each execution of the Static Assembler.
- It caches all eligible rules in the DB into the rule caches.
Now coming to your question,
Q1: Whether closing browser affects Static Assembler running in the background as it's on the server side.
A: I don't have much idea, but I think it needs a requestor to invoke it so probably as requestor session gets invalidated/closed it's may get affected.
Hi,
Thanks for posting on PSC.
As per my understanding of Static Assembler,
- All rules are flushed from the rule caches each time it runs, thus all rules re-populated on each execution of the Static Assembler.
- It caches all eligible rules in the DB into the rule caches.
Now coming to your question,
Q1: Whether closing browser affects Static Assembler running in the background as it's on the server side.
A: I don't have much idea, but I think it needs a requestor to invoke it so probably as requestor session gets invalidated/closed it's may get affected.
Q2:Standard practice in production environment.
A: Refer these links,
- It contains major release changes to specific rules and action required in application release.
- Performance guidance for production system:- It contains the detailed description of standard practices in prod environment.
Hope it helps you, kindly notify if it does.
Regards,
Asif
Adding to it,
https://docs-previous.pega.com/setting-and-packaging-release-your-shared-development-environment
Accepted Solution
We have found out that Declare Expression not working issue was not caused by Rule Assembler, but how we imported. We have imported a R-A-P that includes Implementation layer prior to R-A-P that includes Framework layer. Some rule instances are referencing a Framework class that did not exist when imported.
For Rule Assembler, I will use this tool even for production environment as it will reduce the first log in business user's stress.
Thanks,