Chapter 81. KIE sessions In Red Hat Decision Manager, a KIE session stores and executes runtime data. The KIE session is created from a KIE base or directly from a KIE container if you have defined the KIE session in the KIE module descriptor file ( kmodule.xml ) for your project. Example KIE session configuration in a kmodule.xml file <kmodule> ... <kbase> ... <ksession name="KSession2_1" type="stateless" default="true" clockType="realtime"> ... </kbase> ... </kmodule> A KIE base is a repository that you define in the KIE module descriptor file ( kmodule.xml ) for your project and contains all rules and other business assets in Red Hat Decision Manager, but does not contain any runtime data. Example KIE base configuration in a kmodule.xml file <kmodule> ... <kbase name="KBase2" default="false" eventProcessingMode="stream" equalsBehavior="equality" declarativeAgenda="enabled" packages="org.domain.pkg2, org.domain.pkg3" includes="KBase1"> ... </kbase> ... </kmodule> A KIE session can be stateless or stateful. In a stateless KIE session, data from a invocation of the KIE session (the session state) is discarded between session invocations. In a stateful KIE session, that data is retained. The type of KIE session you use depends on your project requirements and how you want data from different asset invocations to be persisted. 81.1. Stateless KIE sessions A stateless KIE session is a session that does not use inference to make iterative changes to facts over time. In a stateless KIE session, data from a invocation of the KIE session (the session state) is discarded between session invocations, whereas in a stateful KIE session, that data is retained. A stateless KIE session behaves similarly to a function in that the results that it produces are determined by the contents of the KIE base and by the data that is passed into the KIE session for execution at a specific point in time. The KIE session has no memory of any data that was passed into the KIE session previously. Stateless KIE sessions are commonly used for the following use cases: Validation , such as validating that a person is eligible for a mortgage Calculation , such as computing a mortgage premium Routing and filtering , such as sorting incoming emails into folders or sending incoming emails to a destination For example, consider the following driver's license data model and sample DRL rule: Data model for driver's license application public class Applicant { private String name; private int age; private boolean valid; // Getter and setter methods } Sample DRL rule for driver's license application The Is of valid age rule disqualifies any applicant younger than 18 years old. When the Applicant object is inserted into the decision engine, the decision engine evaluates the constraints for each rule and searches for a match. The "objectType" constraint is always implied, after which any number of explicit field constraints are evaluated. The variable USDa is a binding variable that references the matched object in the rule consequence. Note The dollar sign ( USD ) is optional and helps to differentiate between variable names and field names. In this example, the sample rule and all other files in the ~/resources folder of the Red Hat Decision Manager project are built with the following code: Create the KIE container KieServices kieServices = KieServices.Factory.get(); KieContainer kContainer = kieServices.getKieClasspathContainer(); This code compiles all the rule files found on the class path and adds the result of this compilation, a KieModule object, in the KieContainer . Finally, the StatelessKieSession object is instantiated from the KieContainer and is executed against specified data: Instantiate the stateless KIE session and enter data StatelessKieSession kSession = kContainer.newStatelessKieSession(); Applicant applicant = new Applicant("Mr John Smith", 16); assertTrue(applicant.isValid()); ksession.execute(applicant); assertFalse(applicant.isValid()); In a stateless KIE session configuration, the execute() call acts as a combination method that instantiates the KieSession object, adds all the user data and executes user commands, calls fireAllRules() , and then calls dispose() . Therefore, with a stateless KIE session, you do not need to call fireAllRules() or call dispose() after session invocation as you do with a stateful KIE session. In this case, the specified applicant is under the age of 18, so the application is declined. For a more complex use case, see the following example. This example uses a stateless KIE session and executes rules against an iterable list of objects, such as a collection. Expanded data model for driver's license application public class Applicant { private String name; private int age; // Getter and setter methods } public class Application { private Date dateApplied; private boolean valid; // Getter and setter methods } Expanded DRL rule set for driver's license application Expanded Java source with iterable execution in a stateless KIE session StatelessKieSession ksession = kbase.newStatelessKnowledgeSession(); Applicant applicant = new Applicant("Mr John Smith", 16); Application application = new Application(); assertTrue(application.isValid()); ksession.execute(Arrays.asList(new Object[] { application, applicant })); 1 assertFalse(application.isValid()); ksession.execute (CommandFactory.newInsertIterable(new Object[] { application, applicant })); 2 List<Command> cmds = new ArrayList<Command>(); 3 cmds.add(CommandFactory.newInsert(new Person("Mr John Smith"), "mrSmith")); cmds.add(CommandFactory.newInsert(new Person("Mr John Doe"), "mrDoe")); BatchExecutionResults results = ksession.execute(CommandFactory.newBatchExecution(cmds)); assertEquals(new Person("Mr John Smith"), results.getValue("mrSmith")); 1 Method for executing rules against an iterable collection of objects produced by the Arrays.asList() method. Every collection element is inserted before any matched rules are executed. The execute(Object object) and execute(Iterable objects) methods are wrappers around the execute(Command command) method that comes from the BatchExecutor interface. 2 Execution of the iterable collection of objects using the CommandFactory interface. 3 BatchExecutor and CommandFactory configurations for working with many different commands or result output identifiers. The CommandFactory interface supports other commands that you can use in the BatchExecutor , such as StartProcess , Query , and SetGlobal . 81.1.1. Global variables in stateless KIE sessions The StatelessKieSession object supports global variables (globals) that you can configure to be resolved as session-scoped globals, delegate globals, or execution-scoped globals. Session-scoped globals: For session-scoped globals, you can use the method getGlobals() to return a Globals instance that provides access to the KIE session globals. These globals are used for all execution calls. Use caution with mutable globals because execution calls can be executing simultaneously in different threads. Session-scoped global import org.kie.api.runtime.StatelessKieSession; StatelessKieSession ksession = kbase.newStatelessKieSession(); // Set a global `myGlobal` that can be used in the rules. ksession.setGlobal("myGlobal", "I am a global"); // Execute while resolving the `myGlobal` identifier. ksession.execute(collection); Delegate globals: For delegate globals, you can assign a value to a global (with setGlobal(String, Object) ) so that the value is stored in an internal collection that maps identifiers to values. Identifiers in this internal collection have priority over any supplied delegate. If an identifier cannot be found in this internal collection, the delegate global (if any) is used. Execution-scoped globals: For execution-scoped globals, you can use the Command object to set a global that is passed to the CommandExecutor interface for execution-specific global resolution. The CommandExecutor interface also enables you to export data using out identifiers for globals, inserted facts, and query results: Out identifiers for globals, inserted facts, and query results import org.kie.api.runtime.ExecutionResults; // Set up a list of commands. List cmds = new ArrayList(); cmds.add(CommandFactory.newSetGlobal("list1", new ArrayList(), true)); cmds.add(CommandFactory.newInsert(new Person("jon", 102), "person")); cmds.add(CommandFactory.newQuery("Get People" "getPeople")); // Execute the list. ExecutionResults results = ksession.execute(CommandFactory.newBatchExecution(cmds)); // Retrieve the `ArrayList`. results.getValue("list1"); // Retrieve the inserted `Person` fact. results.getValue("person"); // Retrieve the query as a `QueryResults` instance. results.getValue("Get People"); 81.2. Stateful KIE sessions A stateful KIE session is a session that uses inference to make iterative changes to facts over time. In a stateful KIE session, data from a invocation of the KIE session (the session state) is retained between session invocations, whereas in a stateless KIE session, that data is discarded. Warning Ensure that you call the dispose() method after running a stateful KIE session so that no memory leaks occur between session invocations. Stateful KIE sessions are commonly used for the following use cases: Monitoring , such as monitoring a stock market and automating the buying process Diagnostics , such as running fault-finding processes or medical diagnostic processes Logistics , such as parcel tracking and delivery provisioning Ensuring compliance , such as verifying the legality of market trades For example, consider the following fire alarm data model and sample DRL rules: Data model for sprinklers and fire alarm public class Room { private String name; // Getter and setter methods } public class Sprinkler { private Room room; private boolean on; // Getter and setter methods } public class Fire { private Room room; // Getter and setter methods } public class Alarm { } Sample DRL rule set for activating sprinklers and alarm For the When there is a fire turn on the sprinkler rule, when a fire occurs, the instances of the Fire class are created for that room and inserted into the KIE session. The rule adds a constraint for the specific room matched in the Fire instance so that only the sprinkler for that room is checked. When this rule is executed, the sprinkler activates. The other sample rules determine when the alarm is activated or deactivated accordingly. Whereas a stateless KIE session relies on standard Java syntax to modify a field, a stateful KIE session relies on the modify statement in rules to notify the decision engine of changes. The decision engine then reasons over the changes and assesses impact on subsequent rule executions. This process is part of the decision engine ability to use inference and truth maintenance and is essential in stateful KIE sessions. In this example, the sample rules and all other files in the ~/resources folder of the Red Hat Decision Manager project are built with the following code: Create the KIE container KieServices kieServices = KieServices.Factory.get(); KieContainer kContainer = kieServices.getKieClasspathContainer(); This code compiles all the rule files found on the class path and adds the result of this compilation, a KieModule object, in the KieContainer . Finally, the KieSession object is instantiated from the KieContainer and is executed against specified data: Instantiate the stateful KIE session and enter data KieSession ksession = kContainer.newKieSession(); String[] names = new String[]{"kitchen", "bedroom", "office", "livingroom"}; Map<String,Room> name2room = new HashMap<String,Room>(); for( String name: names ){ Room room = new Room( name ); name2room.put( name, room ); ksession.insert( room ); Sprinkler sprinkler = new Sprinkler( room ); ksession.insert( sprinkler ); } ksession.fireAllRules(); Console output With the data added, the decision engine completes all pattern matching but no rules have been executed, so the configured verification message appears. As new data triggers rule conditions, the decision engine executes rules to activate the alarm and later to cancel the alarm that has been activated: Enter new data to trigger rules Fire kitchenFire = new Fire( name2room.get( "kitchen" ) ); Fire officeFire = new Fire( name2room.get( "office" ) ); FactHandle kitchenFireHandle = ksession.insert( kitchenFire ); FactHandle officeFireHandle = ksession.insert( officeFire ); ksession.fireAllRules(); Console output ksession.delete( kitchenFireHandle ); ksession.delete( officeFireHandle ); ksession.fireAllRules(); Console output In this case, a reference is kept for the returned FactHandle object. A fact handle is an internal engine reference to the inserted instance and enables instances to be retracted or modified later. As this example illustrates, the data and results from stateful KIE sessions (the activated alarm) affect the invocation of subsequent sessions (alarm cancellation). 81.3. KIE session pools In use cases with large amounts of KIE runtime data and high system activity, KIE sessions might be created and disposed very frequently. A high turnover of KIE sessions is not always time consuming, but when the turnover is repeated millions of times, the process can become a bottleneck and require substantial clean-up effort. For these high-volume cases, you can use KIE session pools instead of many individual KIE sessions. To use a KIE session pool, you obtain a KIE session pool from a KIE container, define the initial number of KIE sessions in the pool, and create the KIE sessions from that pool as usual: Example KIE session pool // Obtain a KIE session pool from the KIE container KieContainerSessionsPool pool = kContainer.newKieSessionsPool(10); // Create KIE sessions from the KIE session pool KieSession kSession = pool.newKieSession(); In this example, the KIE session pool starts with 10 KIE sessions in it, but you can specify the number of KIE sessions that you need. This integer value is the number of KIE sessions that are only initially created in the pool. If required by the running application, the number of KIE sessions in the pool can dynamically grow beyond that value. After you define a KIE session pool, the time you use the KIE session as usual and call dispose() on it, the KIE session is reset and pushed back into the pool instead of being destroyed. KIE session pools typically apply to stateful KIE sessions, but KIE session pools can also affect stateless KIE sessions that you reuse with multiple execute() calls. When you create a stateless KIE session directly from a KIE container, the KIE session continues to internally create a new KIE session for each execute() invocation. Conversely, when you create a stateless KIE session from a KIE session pool, the KIE session internally uses only the specific KIE sessions provided by the pool. When you finish using a KIE session pool, you can call the shutdown() method on it to avoid memory leaks. Alternatively, you can call dispose() on the KIE container to shut down all the pools created from the KIE container.

Commands:
<kmodule> <kbase> <ksession name="KSession2_1" type="stateless" default="true" clockType="realtime"> </kbase> </kmodule>
<kmodule> <kbase name="KBase2" default="false" eventProcessingMode="stream" equalsBehavior="equality" declarativeAgenda="enabled" packages="org.domain.pkg2, org.domain.pkg3" includes="KBase1"> </kbase> </kmodule>
public class Applicant { private String name; private int age; private boolean valid; // Getter and setter methods }
package com.company.license rule "Is of valid age" when USDa : Applicant(age < 18) then USDa.setValid(false); end
KieServices kieServices = KieServices.Factory.get(); KieContainer kContainer = kieServices.getKieClasspathContainer();
StatelessKieSession kSession = kContainer.newStatelessKieSession(); Applicant applicant = new Applicant("Mr John Smith", 16); assertTrue(applicant.isValid()); ksession.execute(applicant); assertFalse(applicant.isValid());
public class Applicant { private String name; private int age; // Getter and setter methods } public class Application { private Date dateApplied; private boolean valid; // Getter and setter methods }
package com.company.license rule "Is of valid age" when Applicant(age < 18) USDa : Application() then USDa.setValid(false); end rule "Application was made this year" when USDa : Application(dateApplied > "01-jan-2009") then USDa.setValid(false); end
StatelessKieSession ksession = kbase.newStatelessKnowledgeSession(); Applicant applicant = new Applicant("Mr John Smith", 16); Application application = new Application(); assertTrue(application.isValid()); ksession.execute(Arrays.asList(new Object[] { application, applicant })); 1 assertFalse(application.isValid()); ksession.execute (CommandFactory.newInsertIterable(new Object[] { application, applicant })); 2 List<Command> cmds = new ArrayList<Command>(); 3 cmds.add(CommandFactory.newInsert(new Person("Mr John Smith"), "mrSmith")); cmds.add(CommandFactory.newInsert(new Person("Mr John Doe"), "mrDoe")); BatchExecutionResults results = ksession.execute(CommandFactory.newBatchExecution(cmds)); assertEquals(new Person("Mr John Smith"), results.getValue("mrSmith"));
import org.kie.api.runtime.StatelessKieSession; StatelessKieSession ksession = kbase.newStatelessKieSession(); // Set a global `myGlobal` that can be used in the rules. ksession.setGlobal("myGlobal", "I am a global"); // Execute while resolving the `myGlobal` identifier. ksession.execute(collection);
import org.kie.api.runtime.ExecutionResults; // Set up a list of commands. List cmds = new ArrayList(); cmds.add(CommandFactory.newSetGlobal("list1", new ArrayList(), true)); cmds.add(CommandFactory.newInsert(new Person("jon", 102), "person")); cmds.add(CommandFactory.newQuery("Get People" "getPeople")); // Execute the list. ExecutionResults results = ksession.execute(CommandFactory.newBatchExecution(cmds)); // Retrieve the `ArrayList`. results.getValue("list1"); // Retrieve the inserted `Person` fact. results.getValue("person"); // Retrieve the query as a `QueryResults` instance. results.getValue("Get People");
public class Room { private String name; // Getter and setter methods } public class Sprinkler { private Room room; private boolean on; // Getter and setter methods } public class Fire { private Room room; // Getter and setter methods } public class Alarm { }
rule "When there is a fire turn on the sprinkler" when Fire(USDroom : room) USDsprinkler : Sprinkler(room == USDroom, on == false) then modify(USDsprinkler) { setOn(true) }; System.out.println("Turn on the sprinkler for room "+USDroom.getName()); end rule "Raise the alarm when we have one or more fires" when exists Fire() then insert( new Alarm() ); System.out.println( "Raise the alarm" ); end rule "Cancel the alarm when all the fires have gone" when not Fire() USDalarm : Alarm() then delete( USDalarm ); System.out.println( "Cancel the alarm" ); end rule "Status output when things are ok" when not Alarm() not Sprinkler( on == true ) then System.out.println( "Everything is ok" ); end
KieServices kieServices = KieServices.Factory.get(); KieContainer kContainer = kieServices.getKieClasspathContainer();
KieSession ksession = kContainer.newKieSession(); String[] names = new String[]{"kitchen", "bedroom", "office", "livingroom"}; Map<String,Room> name2room = new HashMap<String,Room>(); for( String name: names ){ Room room = new Room( name ); name2room.put( name, room ); ksession.insert( room ); Sprinkler sprinkler = new Sprinkler( room ); ksession.insert( sprinkler ); } ksession.fireAllRules();
> Everything is ok
Fire kitchenFire = new Fire( name2room.get( "kitchen" ) ); Fire officeFire = new Fire( name2room.get( "office" ) ); FactHandle kitchenFireHandle = ksession.insert( kitchenFire ); FactHandle officeFireHandle = ksession.insert( officeFire ); ksession.fireAllRules();
> Raise the alarm > Turn on the sprinkler for room kitchen > Turn on the sprinkler for room office
ksession.delete( kitchenFireHandle ); ksession.delete( officeFireHandle ); ksession.fireAllRules();
> Cancel the alarm > Turn off the sprinkler for room office > Turn off the sprinkler for room kitchen > Everything is ok
// Obtain a KIE session pool from the KIE container KieContainerSessionsPool pool = kContainer.newKieSessionsPool(10); // Create KIE sessions from the KIE session pool KieSession kSession = pool.newKieSession();