Drools Gateway Jug

8/2/2019 Drools Gateway Jug

1/107

The Business Logic Integration Platform

Drools and

the BRMS

Ray PloskiDirector - Developer Experience


2/107

Agenda

The Concepts

A Simple Example and Demo

Projects OverviewBest practices integrating Drools into

your development process

Learning more, getting involved andgetting support


3/107

What is Drools?

Planner


4/107


5/107

What is JBoss BRMS?

A common and complete platform to model and govern the business logic of the

enterprise

JBoss Enterprise BRMS

Single, integrated, certified

distributions Extensive Q/A Process Industry-leading Support Documentation Secure, Production-level

Configurations Multi-year Errata Policy

BRMS


6/107

6


n Each JBoss Enterprise Middleware platform goes through a 5 phase delivery methodology that

involves many traditional elements of the software development lifecyle:

PlatformCandidateRelease(s)

QualityAssurance

Drools Projects

JBoss.orgEngineers

1

ProductRequirements

Definition

Product

Management

2Platform Testing,

Certification &Documentation

JBoss QA, DocumentationTeam, Certified Partners

4

JBossEnterprise

BRMS

Platform ComponentEngineering & Integration

JBossProductization

Engineers

3 5Platform Release

(General Availability)

JBoss ReleaseEngineering

DeliveryPhase

Produ

ctizationTeam


7/107

The

Concepts


8/107

The Typical SDLC


9/107

The Typical SDLC


10/107

The Typical SDLC


11/107

The Typical SDLC


12/107

The Typical SDLC


13/107

The Typical SDLC


14/107

The Typical SDLC


15/107

Extract the Logic


16/107

Extract the Logic

Separate integration codebasefrom business logic and into a

rules engine


17/107

Extract the Logic


rules engine Goal: Remove the requirements

churn and complexity


18/107

Extract the Logic


rules engine Goal: Remove the requirements

churn and complexity

Goal: Empower your DomainExperts to directly author rules


19/107


20/107

Business Logic

Rules


21/107

Business Logic

Rules

Process


22/107

Business Logic

Rules

Process

Response to Events


23/107

Business Logic

Rules

Process

Response to Events

Planning Problems


24/107

Why a Unified Approach?

Extend Rules Engine to handle process State

Extend the Engine to handle Events

Integration provides

Simplicity Performance

Manageability

Integration of Features


25/107

What is a Rules Engine?


26/107


Ambiguous Term


27/107


Ambiguous TermInference Engine Concepts Clarify

Scales to a large number of rules and

facts

Matches facts against rules to inferconclusions

Conclusions result in actions

Simple two-part structure:

rule XYZ

when

then


28/107

Facts POJOs (Plain Old Java Objects)

Rules engine uses to evaluate conditions

Rules engine can execute POJO methods

Can be loaded from a database viaHibernate, JPA, etc...

Rules engine can modify a facts state

Dynamic Facts

Can be modeled in the Web UI


29/107

Facts POJOs (Plain Old Java Objects)

Rules engine uses to evaluate conditions

Rules engine can execute POJO methods

Can be loaded from a database viaHibernate, JPA, etc...

Rules engine can modify a facts state

Dynamic Facts

Can be modeled in the Web UI


30/107

Fact Model Example

publicclass Room { private String name // getter and setter methods here}publicclass Sprinkler {

private Room room; privatebooleanon; // getter and setter methods here}publicclass Fire { private Room room;

// getter and setter methods here}publicclass Alarm {}

Model is multiplefacts and theirrelationships


31/107

Fact Model Example

publicclass Room { private String name // getter and setter methods here}publicclass Sprinkler {

private Room room; privatebooleanon; // getter and setter methods here}publicclass Fire { private Room room;

// getter and setter methods here}publicclass Alarm {}

Must have setters/getters

Must have a publicno-arg constructor

No mandatoryinheritance/interface

Model is multiplefacts and theirrelationships


32/107

Rules


33/107

Rules

Form the IF/Then action defined as When/Then


34/107

Rules

Form the IF/Then action defined as When/Then Must have a name that is unique for a rule

package


35/107

Rules


package

LHS (Left Hand Side)

Conditional part of the rule

Evaluate fact attributes based on criteria


36/107

Rules


package




RHS (Right Hand Side)

Consequence or action part of the rule Invoke operations

Modify Fact State


37/107

Rules


package






Modify Fact State


38/107

Rules


package






Modify Fact State


39/107

Rules


package






Modify Fact State

Rules can be authored in multiple ways!


40/107

Rules in DRLpackage com.sample

import com.sample.*;

rule"When there is a fire turn on the sprinkler"dialect"mvel"when Fire( $room: room) $sprinkler: Sprinkler( room == $room, on == false )then modify ($sprinkler) {on = true}; println("Sprinkler activated in " + $room.name);end

rule"When the fire is gone turn off the sprinkler"dialect"mvel"when

$room : Room()

$sprinkler : Sprinkler( room == $room, on == true ) not Fire( room == $room )then modify( $sprinkler ) { on = false };

println( "Turn off the sprinkler for room " + $room.name );end


41/107

Conditional Elements

and all attributes match (default of comma separated list)

or either attribute matches

eval catch all element

wraps any primative returning semantic code

not attribute does not match

exists checks for the existence of something

collect, memberOf, accumulate elements to reason over collections of data

from element to retreive data from external sources like DBs, WebServices,

etc.

matches, soundslike, regular expressions and English language phonetics


42/107

Rule Control

no-loop short circuit rule recursion

salience numeric value that represents rule importance

agenda-group fire rules in group only when in focus

auto-focus trigger focus change to the rule's agenda-group

activation-group first matching rule fires

all other rules in group are ignored lock-on-active

date-effective, date-expires define rules that are only active at certain points in time

template define templates that may be reused in multiple rules


43/107

- Dynamic Facts- Decision Tables- Guided Rules- English/Industry Specific Rules- Guided Tests- Scenario Tests- Asset Search- Browse by Category- Browse by Status

- Spreadsheet Decision Tables

- Technical Rules (.drl)- Enumerations- Domain Specific Language- Templates- Rule Flow- Step-debugging- Agenda Views and Inspection- Working Memory Inspection- Rule Engine Audit Trails- Technical Tests- Technical Test Suites

Web Broswer

Spread sheet

JBoss Developer Studio

Avenues for Authoring Rules


44/107

20

BRMS Rich UI for Business Rules


45/107

21

Fact Model Editor


46/107

22

Guided Rule Editor (Web)


47/107

23

Web Decision Table Editor


48/107

24

Decision Tables


49/107

Discussions & Inbox


50/107

DroolsDoc

Si l A t V ifi ti


51/107

Single Asset Verification


52/107

Multiple View / Edits in a Single Tab

F C ll t & A l t S t


53/107

From, Collect & Accumulate Support

From CE

From Collect CE

From Accumulate CE


54/107

Rule Template Support

W ki S t


55/107

Workin Sets


56/107

Fact Constraints within WorkingSets


57/107

Runtime


58/107

Runtime: Buildinprivatestatic KnowledgeBase readKnowledgeBase() throws Exception { KnowledgeBuilder kbuilder = KnowledgeBuilderFactory.newKnowledgeBuilder();

kbuilder.add(ResourceFactory.newClassPathResource("fire.drl"),ResourceType.DRL);

KnowledgeBuilderErrors errors = kbuilder.getErrors(); if (errors.size() > 0) { for (KnowledgeBuilderError error: errors) { System.err.println(error); } thrownew IllegalArgumentException("Could not parse knowledge."); }

KnowledgeBase kbase = KnowledgeBaseFactory.newKnowledgeBase(); kbase.addKnowledgePackages(kbuilder.getKnowledgePackages()); return kbase; }


59/107






60/107






61/107






62/107





C l S i C fi ti


63/107

Camel & Spring Configuration

THE BRE now has extensive Spring support, the XSDcan be found in the the drools-spring jar. The

namespace is "http://drools.org/schema/drools-spring"

R ti E ti
http://www.springframework.org/schema/beanshttp://www.w3.org/2001/XMLSchema-instancehttp://drools.org/schema/drools-springhttp://drools.org/schema/drools-springhttp://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-container/drools-spring/src/main/resources/org/drools/container/spring/drools-spring-1.0.0.xsdhttp://drools.org/schema/drools-springhttp://drools.org/schema/drools-springhttp://drools.org/schema/drools-springhttp://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-container/drools-spring/src/main/resources/org/drools/container/spring/drools-spring-1.0.0.xsdhttp://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-container/drools-spring/src/main/resources/org/drools/container/spring/drools-spring-1.0.0.xsdhttp://drools.org/schema/drools-springhttp://drools.org/schema/drools-springhttp://drools.org/schema/drools-springhttp://drools.org/schema/drools-springhttp://www.w3.org/2001/XMLSchema-instancehttp://www.w3.org/2001/XMLSchema-instancehttp://www.springframework.org/schema/beanshttp://www.springframework.org/schema/beans


64/107

Runtime - Execution try { // load up the knowledge base KnowledgeBase kbase = readKnowledgeBase(); StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession(); KnowledgeRuntimeLogger logger = KnowledgeRuntimeLoggerFactory

.newFileLogger(ksession, "test");

for( String name: ROOM_NAMES ){ Room room = new Room( name ); name2room.put( name, room ); ksession.insert( room ); Sprinkler sprinkler = new Sprinkler( room ); ksession.insert( sprinkler ); } // go ! ksession.fireAllRules();

R ti E ti


65/107




R ti E ti


66/107




R ti E ti


67/107




R ti E ti


68/107




R ti E ti


69/107




R ti E ti


70/107




> Everything is OK

i i


71/107

Runtime - Execution 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();

ti ti


72/107

Runtime - Execution 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

R ti E ti


73/107

Runtime - Execution ksession.retract( kitchenFireHandle ); ksession.retract( officeFireHandle ); ksession.fireAllRules();

R ti E ti


74/107

Runtime - Execution ksession.retract( kitchenFireHandle ); ksession.retract( officeFireHandle ); ksession.fireAllRules();

> Turn off the sprinkler for room office> Turn off the sprinkler for room kitchen> Cancel the alarm

> Everything is ok


75/107

Use FROM for external data

rule Find Vehicles for a given zip code"when

$zipCode : ZipCode() Vehicle() from $hibernate.getNamedQuery( FindVehicles )

.setParameters( [ zipCode : $zipCode ]) .list()then...

end

Can be a Web Service, Hibernate or any external system

R ti Vi ibilit JMX


76/107

Runtime Visibility - JMX

Drools 5.3 brings support to the JMX standard andenables knowledge base and knowledge sessionmonitoring and inspection using any JMX console.

KnowledgeBase Stats

Runtime Visibility JMX


77/107

Runtime Visibility - JMX

KnowledgeSession Stats

Deployment

- PackagingSnapshots - Asset Search


78/107

Facts

Rules

Tests

Analysis

Java Jars Dynamic Facts

- Technical Rules (.drl)- Enumerations- Domain Specific Language- Templates- Rule Flow

- Decision Tables- Guided Rules- English/Industry Specific Rules

- Decision Tables

- Technical Tests- Technical Test Suites

- Guided Tests- Scenario Tests

- Step-debugging- Agenda Views and Inspection- Working Memory Inspection- Rule Engine Audit Trails

- Rule Authoring Analysis- Guided Test Audit Trails

- Snapshots- Status Definition- User Administration- Categorization

Developer-centric Business Analyst

Asset Search- Browse by Category- Browse by Status

Web-only Feature

Modifiable via Web Browser or Developer IDE

Modifiable via Developer IDE

Modifiable via Excel/OpenOffice

Deployment

- PackagingSnapshots - Asset Search


79/107

Facts

Rules

Tests

Analysis




- Decision Tables







- Browse by Category- Browse by Status

Web-only Feature




Deployment

- Packaging- Snapshots - Asset Search


80/107

Facts

Rules

Tests

Analysis




- Decision Tables







- Browse by Category- Browse by Status

Web-only Feature




Eclipse Developer Perspective


81/107

43

Eclipse Developer Perspective

Debugging


82/107

44

Debugging

Debug Views

l

New rule perspective to configure IDE for rules as needed

Guided Rule Editor (Eclipse)


83/107

45

Guided Rule Editor (Eclipse)

Eclipse Guided Editor

Rule Flow


84/107

46

Rule Flow

N d T


85/107

Node Types


86/107

Domain Specific Process Steps

Extend Drools Flow to incorporateyour applications needs

Note: Community Only

Integrated Tooling


87/107

Integrated Tooling

CEP


88/107

CEP

Complex event processing

Real time events (concurrent events threadsafe):

sliding windows:Pattern(...) over window:time(3000)

Fusion Enables:


89/107

Fusion Enables:

Event Detection:

From an event cloud or set of streams, select all themeaningful events, and only them.

[Temporal] Event Correlation:

Ability to correlate events and facts declaring both

temporal and non-temporal constraints between them. Ability to reason over event aggregation

Event Abstraction:

Ability to compose complex events from atomic eventsAND reason over them

Events


90/107

Events

(Usually) Immutable FactsStrong Temporal

Relationship

Managed LifecylceUse of sliding windows

Can provide metadata on:

@timestamp, @duration or@expires

Streams


91/107

Streams

Temporal Reasoning


92/107

Temporal Reasoning

Event and Time semantics:

Point in Time

Over an Interval

Unified semantics for eventcorrelation over time

Temporal Constraints:

Set of 13 operators to express

temporal relationship between

events

Expressive Event Constraints


93/107

Expressive Event Constraints

Point-Point Point-Interval Interval-Interval

A beforeB

A meets B

A overlaps B

A includes B

A finishes B

A starts B

A coincides B

Behaviors & Sliding Windows


94/107

Behaviors & Sliding Windows

Behaviors: special semantics to certain patterns sliding windows, distinct, sort, etc

SlidingWindow: Allows reasoning over a movingwindow of interest

Time

Length

Memory Management


95/107

Memory Management

CEP scenarios are stateful by nature.

Events usually are only interesting

during a short period of time.Fusion manages the benefits

memory management while events

still in window of consideration

Rulebase Partitioning


96/107

Rulebase Partitioning

Achieves coarsegrainedparallelization

No fundamentalchanges in thematching algorithm

(ReteOO)

Preservesoptimizations,especially node

sharing


97/107

Planner

Wh t i Pl ?


98/107

What is Planner?

Optimizes Automated Planning

Use Cases:

Space Planning Employee Shift Rostering

Team Scheduling

Still in development! Not commercially supported.


99/107

Hospital Admissions

Patient Admission Schedule


100/107

Patient Admission Schedule

Hard constraints No 2 patients in same bed in same night

Room gender limitation

Department minimum or maximum age

Patient requires specific room equipment(s)

Soft constraints Patient prefers maximum room size

Department specialization

Room specialization Patient prefers specific room equipment(s)

Pl S t


101/107

Planner Syntax// If a hospital patient prefers specific equipment, try to assign him/her a hospital

room with such equipment.rule"preferredPatientEquipment"

when // If a patient prefers specific equipment

PreferredPatientEquipment($patient : patient, $equipment : equipment);

// and that patient is assigned a roomBedDesignation(patient == $patient, $room : room);

// and that room doesn't have that equipment

not RoomEquipment(room == $room, equipment == $equipment); then

... // lower the score with a certain weightend

Needle in a Haystack


102/107




103/107


How many possiblesolutions? 310 beds

in 105 rooms

in 4 departments 84 nights



104/107



in 105 rooms


2750 patients(admissions)



105/107



in 105 rooms


2750 patients(admissions)

Numbers from a realdataset

Commercial Support


106/107

Commercial Support

Drools ships within several supportedplatforms:


JBoss Enterprise SOA Platform *

JBoss Enterprise Application Platform **

Support Open Source!


107/107

Support Open Source!

We need You! JBoss User Groups

Contribute

Code Features

Documentation

Testing

Let us continue our work that benefits so many.

Documents

Drools Gateway Jug