Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Preassembling rules in an application

Updated on May 11, 2022

The Static Assembler utility enables the preassembly and caching of rules that belong to an application. These actions improve the response time for interactive users after a system startup or when new ruleset versions are imported into the system.

You can run the utility at any time, for example, after you import an application that contains a large number of new rules, after an application upgrade, or after any significant change was made in the application development cycle.

You can run the Static Assembler utility in one of the following modes, depending on your work context.

  • Running Static Assembler in utility mode

    Run the Static Assembler from the /scripts/utils directory within the extracted application installation directory. This is the best practice because the Static Assembler uses information that is in the application installation directory.

  • Running the Static Assembler in stand-alone mode

    Use the stand-alone mode when using the utility at a command prompt and when passing connection details through the setupDatabase.properties file.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us