| Welcome to ILOG JRules > Getting Started > ILOG JRules Architecture Guidelines > Integrating Rule Execution into an Embedded Rule Engine |
Integrating Rule Execution into an Embedded Rule Engine |
PREVIOUS NEXT |
When you execute rules in an embedded environment, you deploy and execute a ruleset archive on a single Java Virtual Machine (JVM).
You include the rule engine in the class path of the application. In the application, you use the JRules API to load a ruleset, instantiate a rule engine, and execute the rule engine against objects passed as parameters.
The rule engine is a component for executing rules. It uses a ruleset and a group of objects or ruleset parameters to evaluate what rules need to be fired. Firing a rule means executing the action part of the rule in the context of the objects that have satisfied its conditions.
Step 1 of this graphic shows that the rule engine is based on pattern matching: it matches rule conditions with a group of objects or ruleset parameters.
In step 2, the rule engine creates a rule instance for each match between a rule and an object or ruleset parameter. Depending on the algorithm used by the rule engine, or execution mode, the way the rule instances are fired varies.
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |