Changing the default behavior of the execution stack

You can modify the values of various execution unit properties or parameters that affect the execution stack.

Configuring Rule Execution Server in scoped mode
When the default configuration in shared mode is not appropriate for your use case, you can configure Rule Execution Server so that it is scoped to a single Jakarta EE application.
Configuring Rule Execution Server in shared mode
You can configure Rule Execution Server so that client applications can share the same deployed execution unit (XU) resources.
XU configuration properties for Jakarta EE
You can set configuration properties for the execution unit (XU). In Jakarta EE environments, you use the administration console of your application server.
Turning on the trace autoflush
You can set the execution unit (XU) to flush the XU log automatically.
Enabling ruleset monitoring
A property of the execution unit (XU) is set to monitor some usage data on rulesets.
Managing the maximum idle time of rulesets
You can define the minimum time a ruleset stays in memory by setting the value of the ruleset.maxIdleTime ruleset property in the Rule Execution Server console.
Customizing the ruleset cache
You can customize the ruleset cache by writing your own implementation class and then modifying the deployment descriptor of the execution unit (XU) accordingly.
Setting the compiled archives cache
When working with ruleset archives for the decision engine (.dsar files), you can use the compiled archives cache to limit the bytecode generation to the first execution of a ruleset only. The execution unit (XU) generates the bytecode when a ruleset is executed, and stores it into a file-based cache for reuse.
Setting up ruleset parsing
You can set a configuration property to block the execution of a ruleset while waiting for a new version of the ruleset.
Changing persistence parameters
You can change the persistence type for the ruleset repository. If you have set up Java™ XOM management, you can also change the persistence properties for the XOM repository. You must set the persistence t to the same type in both the console and the execution unit (XU) archive.
Configuring the execution stack on Java SE
When you use Rule Execution Server in a Java SE environment, you can configure the execution stack in several ways.
Determining the optimal XU pool size
The optimal execution union (XU) pool size setting in Rule Execution Server depends on many parameters. The best way to determine the optimal XU spool size setting is to run benchmark tests and incrementally adjust the setting until performance is optimal for your environment.

Parent topic: Configuring a Rule Execution Server instance