IBM ODM (Operational Decision Management) / ILog JRules common Terms

IBM ODM (Operational Decision Management) / ILog JRules common Terms This document tries to provide a complete list of all the important keywords/terms in IBM ODM along with their meaning. Here we are trying to understand it in one or two lines max. More details are provided on all of these in upcoming chapters -

  1. BOM – Business Object Model. The rules are written and saved on top of business object model.
  2. XOM – Execution Object Model. The rules are executed on xom. BOM is mapped to XOM so that rules at run time can execute on XOM.
  3. Verbalization – The vocabulary for the rules. verbalization is defined on top of BOM. Verbalization makes the rules easily readable for non IT staff.
  4. Domain – you can define domain on BOM elements. This restricts the value of a bom element.
  5. Category – you can define a category and link multiple categories to a BOM element. This helps in mapping the bom elements with the rule. It makes the rule writing easier by reducing the number of possible bom elements in a rules placeholder.
  6. BAL – Business Action Language. used to define rule in easy to read language as if-else statements.
  7. IRL – Ilog Rule Language. A java like language but can be executed directly by rule engine. Can be used to write complex logic in rule application.
  8. BQL – Business Query Language. Used to write queries on business rules.
  9. Rule Orchestration – The process of defining the rule flow or the sequence in which the rules are executed.
  10. Ruleflow – Create a flow diagram linking nodes with various decisions and rule packages. Ruleflow defines the execution sequence of rules and rule packages.
  11. Rule Task – A node in the rule flow diagram.
  12. Execution mode – The execution mode of a rule task. This is defined in ruleflow at rule task level. possible values are “RetePlus”, “sequential”, “fastpath”.
  13. Rule Package – Structuring of rules in different folders.
  14. RuleSet – Rule set are equivalent to a decision of rule application. An external application invokes a ruleset to trigger the rule engine execution. Ruleset is the execution access point of business rule for an external system at runtime
  15. RuleSet parameters – The parameters passed or returned or both to/from the Ruleset.
  16. RuleSet variables – The scope is only internally in a ruleset. They are global within ruleset but not accessible outside ruleset.
  17. Variable Set – A collection where all the ruleset variables are defined.
  18. RuleSet Archive – A technical language version of all the rules and other rule artifacts like ruleflow, variables etc.
  19. Rule Query – finds all the rules which satisfy the criteria specified in the query.
  20. Ruleset Extractor – filter out all the rules in ruleset archive as per the criteria specified in Rule Query.
  21. Rule Override – If overriding rule is available in the execution scope, then it will override the rule as specified in the properties “overriddenRules”.
  22. Rule priority – A higher priority rule will be executed before a lower priority rule.
  23. Decision Center / RTS ( Rule Team Server) – A web application for writing rules. It is an online shared environment for all the business users. Can also be used to release rules on the execution server.
  24. Rule Solution For Office – A MS Office environment for writing rules offline. The rules can be synched with Decision Center only.
  25. Rule Designer – Eclipse based rule application development environment. Used by developers and experienced IT staff only.
  26. Decision Tables – A table like structure for writing rules with similar condition and action blocks. Each row in decision table is translated to one action rule after compilation.
  27. Decision Tree – A tree like structure for writing rules. Each end node (action node) is equivalent to one action rule.
  28. Templates – Templates are half completed rules which can be used to define a new rule. Templates are used by developers to define the complex parts of a rule. It can also be used by business users to lock / freeze certain parts of a rule.
  29. Rule Variable – variables defined at rule level and having scope limited to a rule.
  30. Automatic Variables – defined in BOM, can be used as a rule variable without explicitly defining them at rule level.
The following two tabs change content below.
Saurabh has more than 15 years of experience of developing IT applications and leading IT teams. He has strong expertise in web applications development using Java/PHP frameworks and mobile applications (ios/android) using native frameworks. At present he works as a technical consultant and mentor with various companies in capacity such as CTO, architect, team leader etc.