firing and firinglimit in Rule task – IBM ODM
SeriesIBM ODM in practicepart 7 of 11
- Rule Engine Execution Modes
- IBM WebSphere Application Server Garbage Collection Policies
- IBM Operational Decision Management(ODM) Performance Tuning – JVM
- Initializing IBM RAD/RSA – eclipse.ini
- Rule Engine Execution Mode – Choosing and Setting in ODM
- Optimizing Ruleset Performance in IBM ODM
- firing and firinglimit in Rule task – IBM ODM
- Development Standards for Execution Object Model (XOM)
- Organizing your application into rule projects – IBM ODM
- Rule Solutions for Office Installation – IBM ODM
- Synchronizing Rules and RuleDocs – Rule Solutions for Office, ODM
On this page
Configuring the Rule task execution plays the key role in executing the rules in a rule flow. firing and firinglimit are the two rule task properties that help rule execution in a rule flow.
firing keyword
The firing keyword determines whether all the rules are executed. This keyword is used to determine whether all the rules of a rule task are executed or only one of them.
Syntax
ruletask ruleTaskName
{
[firing = allrules|rule;]
};All instances of one rule are executed. If only one rule is executed, use the keyword firinglimit.
firinglimit
The firinglimit keyword specifies the number of rules to be executed. The purpose of a rule task is to execute rules. You can modify the execution order and the number of rules that are executed. The keyword firinglimit specifies how many rules are executed.
Syntax
ruletask ruleTaskName
{
[firinglimit = integer value;]
};It is good to have knowledge about these two properties to orchestrate the rules properly in the Operation Decision Management. It all depends on the orchestrator who designs the ruleflow. Happy Learning! Happy Exploring!!