Question

9
Replies
2142
Views
PATTNAIKS Member since 2006 1 post
Cognizant Technology Solutions
Posted: 3 years ago
Last activity: 3 years 4 months ago
Closed
Solved

Pega Static Assembler Utility - Implementation plan

We are planning to implement static assembly process across all the application. There are applications which are in Pega 6.x and in 7.x as well.

We ran the utility in the development environment, which took approximately 2 hrs to complete the process. Below is the snapshot of the log entries which summarizing the completion status.

jvm1 STATIC ASSEMBLY SUMMARY

2017-03-15 10:52:29,777 [ ftwldscimw118] [ STANDARD] [ ] (ly.metrics.PrimerStatCollector) INFO - ===========================================================================

2017-03-15 10:52:29,777 [ ftwldscimw118] [ STANDARD] [ ] (ly.metrics.PrimerStatCollector) INFO - No of Rules Processed : 116156

2017-03-15 10:52:29,777 [ ftwldscimw118] [ STANDARD] [ ] (ly.metrics.PrimerStatCollector) INFO - No of Rules Assembled : 114352

2017-03-15 10:52:29,777 [ ftwldscimw118] [ STANDARD] [ ] (ly.metrics.PrimerStatCollector) INFO - No of Rules Not Assembled : 400

2017-03-15 10:52:29,777 [ ftwldscimw118] [ STANDARD] [ ] (ly.metrics.PrimerStatCollector) INFO - No of Rules Not Eligible : 1404

2017-03-15 10:52:29,777 [ ftwldscimw118] [ STANDARD] [ ] (ly.metrics.PrimerStatCollector) INFO - Total Duration taken (in Sec) : 2421

I have below questions which needs to be clarified in order to better plan the production implementation.

  1. In case of multi node clustered environment, is it required to run for each node or cluster? I see there is a property that we set in the prstaticassembly.properties file to specify the no. of JVMs. What is there relevance of that? If the assembled rules gets stored into DB then running it only once should serve the purpose , please confirm if my understanding is correct.

  2. Does static assembly process only update DB or it also update the disk?

  3. PRPC 7.1.X the “Static Assembler” is available for the user to kick off himself at (Pega button) > System > Tools > Static Assembler. Does that mean after new code deployment running this from one of the node is what required to pre-assemble all the rules?

  4. How to verify that all the required assemble is done and the end user is benefited from this.

  5. Is there a way to not to include based on application each time when we do static assembly ?

  6. In the log snapshot there are entries as below, what is the reason of this and do we care about this?

    1. No of Rules Not Assembled : 400

    2. No of Rules Not Eligible : 1404

Thanks

Sarada

System Administration
Moderation Team has archived post
Share this page LinkedIn