Business rule management system
Drools is a business rule management system (BRMS) with a forward and backward chaining inference based rules engine, more correctly known as a production rule system, using an enhanced implementation of the Rete algorithm.
Drools supports the Java Rules Engine API (Java Specification Request 94) standard for its business rule engine and enterprise framework for the construction, maintenance, and enforcement of business policies in an organization, application, or service.
Red Hat Decision Manager
Red Hat Decision Manager (formerly Red Hat JBoss BRMS[2]) is a business rule management system and reasoning engine for business policy and rules development, access, and change management.[3] JBoss Enterprise BRMS is a productized version of Drools with enterprise-level support available. JBoss Rules is also a productized version of Drools, but JBoss Enterprise BRMS is the flagship product.[4]
Components of the enterprise version:[5]
- JBoss Enterprise Web Platform – the software infrastructure, supported to run the BRMS components only
- JBoss Enterprise Application Platform or JBoss Enterprise SOA Platform – the software infrastructure, supported to run the BRMS components only
- Business Rules Engine – Drools Expert using the Rete algorithm and the Drools Rule Language (DRL)[6]
- Business Rules Manager – Drools Guvnor - Guvnor is a centralised repository for Drools Knowledge Bases, with rich web based GUIs, editors, and tools to aid in the management of large numbers of rules.[7]
- Business Rules Repository – Drools Guvnor
Drools and Guvnor are JBoss Community open source projects. As they are mature, they are brought into the enterprise-ready product JBoss Enterprise BRMS.
Components of the JBoss Community version:[8]
- Drools Guvnor (Business Rules Manager) – a centralized repository for Drools Knowledge Bases
- Drools Expert (rule engine) – uses the rules to perform reasoning
- Drools Flow (process/workflow), or jBPM 5 – provides for workflow and business processes
- Drools Fusion (event processing/temporal reasoning) – provides for complex event processing
- Drools Planner/OptaPlanner (automated planning) – optimizes automated planning, including NP-hard planning problems
Example
This example[9] illustrates a simple rule to print out information about a holiday in July. It checks a condition on an instance of the Holiday class, and executes Java code if that condition is true.
rule "validate holiday"
when
$h1 : Holiday( month == "july" )
then
System.out.println($h1.name + ":" + $h1.month);
end
The purpose of dialect "mvel" is to point the getter and setters of the variables of your Plain Old Java Object (POJO) classes.
Consider the above example, in which a Holiday class is used and inside the circular brackets (parentheses) "month" is used. So with the help dialect "mvel" the getter and setters of the variable "month" can be accessed.
Dialect "java" is used to help us write our Java code in our rules. There is one restriction or characteristic on this. We cannot use Java code inside "when" part of the rule but we can use Java code in "then" part.
We can also declare a Reference variable $h1 without the $ symbol. There is no restriction on this. The main purpose of putting the $ symbol before the variable is to mark the difference between variables of POJO classes and Rules.
