ILOG JRules Overview
Roles-based Tour
and Intro to Business Rule Management Systems (BRMS)
(from ILOG 2010 STEW & PoT)
© 2010 IBM Corporation
ILOG BRMS Roles-based Tour
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Debug
Deploy
6
Rule Execution Server
12
Audit
Java™ SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
2
Tip: click on any task number or name to move to this task.
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
2
Agenda
 Introduction to Business rule management systems (BRMS)
 Roles-based Tour of ILOG JRules BRMS
 Methodology and Next steps
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Business Decisions are everywhere
Va r i a t i o n – N e e d f o r F l e x i b i l i t y
• Jurisdictional
• Micro-Market Segmentation
• Multichannel
Up-sell or Cross-sell
Compensation
Smart CRM
Underwriting
Tax calculation
Benefit calculation
…
Fraud
Risk
Pricing
Claims processing
Eligibility
Compliance • Market Driven
…
• Regulatory
• Mergers and Acquisitions
Change – Need for Agility
4
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Business Needs are Dynamic
Are we compliant with the
new regulation
requirements?
Let’s create a special
promotion for our best
customers.
Can we automate approvals
for this type of order?
5
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
When business logic is hard-coded
• Long change cycle
• Opaque for business users
• Often hidden, scattered and duplicated
LOB
IT
Application code
6
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Business Change Drives IT agility
Decisions used in operations = “business rules”
Where Business Rules Exist
Issues
• Rules are hidden in code or isolated
within the organization
• Changes are hard to track and
maintain over time
Applications
Documents
• Rules used by systems have to be
programmed and require IT resources
• Duplication and multiple versions of
the same rules
• Lack of auditability, traceability
People
7
Processes
IBM WebSphere ILOG JRules 7.1.1.0
• Decision changes cannot be easily
tested or simulated
© 2010 IBM Corporation
The Smarter Approach: Facilitating Change with BRMS
Where Business Rules Exist
Business Rule Management System
User Tools
Rules are
Defined,
Analyzed
and
Maintained
Documents
Applications
Rules are
Managed
and Stored
Rule Repository
People
Processes
Rule Execution
Server
8
IBM WebSphere ILOG JRules 7.1.1.0
Rules are
Deployed,
Executed
and
Monitored
© 2010 IBM Corporation
Rule and Software Development Life cycles
Functional enhancements
Platform upgrade
Software Development Life cycle
Design
Construct
Test
> 4-6 months
Design
Construct
Test
Deploy
Manage and Monitor
Deploy
Validate
Author
Analyze
< 1 month
Deploy
Deploy
Validate
Author
Analyze
Deploy
Validate
Author
Analyze
Deploy
Validate
Author
Analyze
Rule Management Life cycle
Change
Request
9
IBM WebSphere ILOG JRules 7.1.1.0
Change
Request
Change
Request
© 2010 IBM Corporation
Agenda
 Introduction to Business rule management systems (BRMS)
 Roles-based Tour of ILOG JRules BRMS
 Methodology and Next steps
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Roles-based Tour of ILOG JRules BRMS
© 2010 IBM Corporation
Roles: Sequence of 13 tasks
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Debug
Deploy
6
Rule Execution Server
12
Audit
Java™ SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
12
Tip: click on any task number or name to move to this task.
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation12
Agenda
 Introduction to Business rule management systems (BRMS)
 Roles-based Tour of ILOG JRules BRMS
– Business user focused activities
– IT user focused activities
 Methodology and Next steps
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Task 9: Manage
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
14
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation14
Task 9: Manage – web application for rule management
 Access rule artifacts concurrently without
conflict or delay
 Take control of very large rule projects
with Smart Views, easy search
and reporting
 Get automatic notification of potential
rule conflicts, redundancies
 See where rules are used across
projects using queries
 Hot-deploy rule changes in minutes
 Secure, integrated with enterprise
security facility including single sign-on
15
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation15
Task 9: Manage – Rule Repository capabilities
What is the impact of
changing this rule?`
When will this rule take
effect?
Rule repository
PM
New
PM
PM
Defined
PM
Analyst
Who can change what?
• Rule Governance
• Meta-data
• Lifecycle management
• Versioning
• Role-based permissions
• Consistency checking
What has
changed?
16
Rejected
Validated
How do I undo a change?
Admin
Retired
Admin
Admin
Admin
Deployable
Admin
Inactive
What rules do I need
to deploy?
What rules do I need
to validate?
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Task 9: Manage – Rule Versioning
 Versions
– Rules, Decision Tables, Decision Trees, Ruleflows, etc… are
versioned
– Versions created upon modification of element
– You cannot delete previous versions
 History
– consult the history of version modifications made over time
 Baselines
– freeze the state of a project
– for instance keeps an image of rules currently deployed
17
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation17
Task 9: Manage – Comparing versions of a Decision Table
18
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation18
Task 9: Manage – Rule Queries
 Queries enable to search the content of the repository, including any
type of artifact (rule, folder, ruleflow and others)
 Evaluate impact of changes to the object model or changes to the rules
• Before adding a new rule that modifies a certain data value to a rule
project, query for all rules that use that parameter to assess impact of new
rule
 Find rule artifacts based on their properties
• Find only rules you wrote
• Find all rules added within certain time period
• Find a specific rule, based on documentation
 Perform actions based on the results of a search
 Find all business rules such that the status of each business rule is new
Do set the status of each business rule to validated
19
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation19
Task 10: Validate
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
20
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation20
Task 10: Validate - Motivations
 Support the various testing aspects of a decision service
– Correctness
– Non Regression
– Performance
– Coverage
 Support the business impact of a set of changes
– KPI-driven simulation
 Support the ability for qualitative and quantitative comparisons of the
execution of different versions of a given decision service
– Real-time: champion-challenger
– Off-line: data mining and analytics
21
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation21
Task 10: Validate – Decision Validation Services (DVS)
 Functionality Overview
22
–
Ready for immediate use ruleset
testing in Rule Team Server
–
Business impact simulation in
Rule Team Server
–
Scenario configuration and
customization in Rule Studio
–
Audit - Decision Warehouse in
Rule Execution Server
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation22
Task 10: Validate – Fundamental Concepts
 Scenarios
– A scenario defines a real or fictitious use case that contains the necessary
input to execute a decision service properly
– Support for Microsoft® Excel® for defining scenarios
– Specific “scenario providers” can be implemented to use alternate format
such as databases
 Test Suites
– Test suites enable to compare the outcome of a set of scenarios against
expected results
– Expected results and expected execution details can be defined
Example: the list of rules expected to execute
 Simulation Suites
– enables the evaluation of one or more KPIs against a set of scenarios
– KPIs must be defined in Rule Studio
23
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation23
Task 10: Test Suite in Rule Team Server (RTS)
RTS Test Suite Results
Detailed Scenario
Reports
Consolidated
Results
Individual Scenario
Result
24
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation24
Task 11: Deploy
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
25
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation25
Task 11: Deploying from Rule Team Server
 Rules can get deployed either from Rule Team Server to the Rule
Execution Server.
 Hot-deploy rule changes in minutes
Rule Studio
deployment
deployment
Rule Team
Server
Rule Execution
Server
26
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation26
Agenda
 Introduction to Business rule management systems (BRMS)
 Roles-based Tour of ILOG JRules BRMS
– Business user focused activities
– IT user focused activities
 Methodology and Next steps
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Task 1: Design
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
28
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation28
Task 1: Rule Studio
Rule Studio is the development environment for business rule applications.
Developers can take advantage of this integration with Eclipse to develop their
Java projects along with rule projects.
Rule Perspective
Rule Project
Rule Project Map
29
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation29
Task 1: Rule Studio Low cost of ownership for developers
 Easy to learn
– Familiar environment
– Project map for new users
– Follows Eclipse style and design guidelines
– Complete Comprehensive Documentation
– Tutorials and Samples
 Easy to use
– Auto-completion in rule text editor
– Wizard-Driven
 Productivity
– Wizard-driven Java, XML, WSDL data
integration
– Automatic Vocabulary Generation
– Re-factoring
– Queries
– Integrated Rules and Java debugging
30
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation30
Task 1: Rule Project
 The business logic of your application is stored in a rule project. A
rule project enables you to manage, build, and debug the artifacts
that comprise the business logic of your application.
 A rule project is a container for rules and for the artifacts needed
to create them and manage them:
– Business Object Model (BOM)
– Rule templates
Repository
– Queries
 A project can refer to another rule project.
It will have access to all artifacts.
Templates
31
IBM WebSphere ILOG JRules 7.1.1.0
*
Project
Rules BOM
Queries
© 2010 IBM Corporation31
Task 1: Business Object Model (BOM)
 Before writing any rules a vocabulary must be prepared
 The vocabulary is defined by a Business Object Model (BOM)
– BOM classes are “Terms”
– Class members are “Phrases” to be used as conditions or
actions
 A BOM is based on an eXecutable Object Model (XOM)
– XOM can be Java classes, XML Schemas
– Not necessarily one to one mapping. A BOM can have virtual
artifacts with explicit BOM to XOM mapping defined
32
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation32
Task 1: BOM (2/5)
33
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation33
Task 1: BOM (3/5)
Rule Studio provides a dedicated editor to prepare the BOM
BOM class
editor
Discrete domain
definition
Term
verbalization
BOM navigation
Custom BOM to
XOM mapping
Rule category
applicability
34
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation34
Task 1: BOM (4/5)
Class member editor
Phrase
verbalization
Discrete domain
definition
Rule category
applicability
Custom BOM to
XOM mapping
35
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation35
Task 1: BOM (5/5)
BOM folder
BOM Entry
BOM class created from
the Java classes
« miniloan-xom »
Java classes
36
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation36
Task 1: Ruleset parameters
 A rule service is defined by a ruleset containing:
– a set of input/output parameters
– a ruleflow orchestrating the execution of the rules
– a set of rules artifacts grouped into several packages
Business application
Rule-based
Decision Service
IN
OUT
boolean Eligibility (Customer cust)
Risk Scoring (CreditRequest request)
37
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation37
Task 2: Orchestrate
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
38
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation38
Task 2: Rule packages
Project
A rule package is a container for rule artifacts:
 Free text rules written in a pseudo natural
language, Business Action Language
Top-level container
 Decision tables
 Decision trees
*
 Functions written in interpreted Java enabling
to perform technical tasks
Package*
 Ruleflows
*
*
Rule
Rule project structure and rule packaging should be carefully designed to
enable easy maintenance and efficient execution.
39
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation39
Task 2: What is a ruleflow?
 A ruleflow is an executable procedural
diagram composed of tasks and transitions
between tasks
 A rule task maps to a rule package : When the
task is traversed, the rules in the package are
evaluated.
 A function task contains interpreted Java code
performing technical computation (external
data access, etc)
 A flow task maps to another ruleflow module
that can be reused across many higher level
ruleflows
 Any task can be enriched with initial and/or
final actions in interpreted Java
40
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation40
Task 3: Author
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
41
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation41
Task 3: Author – A hierarchy of artifacts
Repository
*
Project
Top-level container
42
• A project is a container for business rules
along with the elements needed to define them
(rule artifacts, BOM, rule templates, queries)
• A container for rule artifacts and packages
(rules, rule flows, functions, variables, rule
packages)
*
• A container for rule artifacts and packages
(rules, rule flows, functions, variables, rule
packages)
*
• A rule (action rule, decision table, decision
tree, technical rule)
Package*
*
• A repository includes a set of projects that
may reference each other
Rule
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation42
Task 3: Write rules
 Using ILOG JRules, business logic is expressed using rule artifacts
based on the vocabulary of all the “visible” BOMs
Rule Artifacts
business rules
decision tables
decision trees
ruleflows
Vocabulary
BOM
43
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation43
Task 3: Business Action Language (BAL) rule
 Anatomy of a rule
rule name
rule documentation
rule category
definitions
conditions
actions
Local
variable
44
Ruleset
parameter
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation44
Task 3: Decision Table
 Concise way of representing sets of business rules that have a
uniform structure in the form of a spreadsheet
row
header
condition column
action column
column
header
rows
45
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation45
Task 4: Test
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
46
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation46
Task 4: Test – Testing & Simulation
 Decision Validation Services allow for testing and simulation of rulesets
in RTS and Studio
– Non regression testing for QA
– Functional tests and simulations for developers and business analysts
 Based on concepts of usage scenarios:
– A usage scenario represent a use case
– A usage scenario is composed of:
• a ruleset,
• An input data set (Excel by default)
 Testing
– A set of expected values for the output parameters is associated with the
usage scenario
 Simulation
– A simulation will be based on a (often large) set of usage scenario without
expected results but with a KPI (Key Performance Indicator)
 Reports
– Test and Simulation runs generate reports
47
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation47
Task 4: Test – Scenario Definition
Input Data
Expected
Results
Ruleset
Tests
48
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation48
Task 4: Test – Test suite in Rule Studio
Generated
Scenario Document
Configuration
editing
Detailed Scenario
Reports
49
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation49
Task 5: Debug
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
50
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation50
Task 5: Debug rules
 With the Debugger, the process of business
rule execution can be controlled by:
– Step into, step over, and step return in any
given block of business rule.
– Resume, suspend, and terminate.
– Setting breakpoints on rules, classes, and
objects.
51
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation51
Task 6: Deploy
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
52
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation52
Task 6: Deployment and Execution
 Rulesets are packaged as RuleApp for deployment and execution
 A RuleApp is a deployable management unit that contains one or more RuleSets
 Each RuleSet is the invocation unit when executing the rules
 Several RuleSets can be packaged in the same RuleApp for management purpose
 Each RuleSet has its own:
– Signature: Input/Output parameters
RuleApp: name, version, creation date, etc.
– Content:
• Rules
RuleSet: name, version, parameters,
rules, ruleflow, etc.
• Ruleflows
• Variables
• Functions
RuleSet: name, version, parameters,
rules, ruleflow, etc.
 A ruleset is the minimal executable resource, identified as:
– /<ruleapp>/<ruleapp-version>/<ruleset>/<ruleset-version>
53
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation53
Task 6: Deploying from Rule Studio
 RuleApps can get deployed either from Rule Studio or/and Rule Team
Server to the Rule Execution Server.
 RES (Rule Execution Server)
– managed business rule execution platform that embeds JRules engine
– Persists rulesets in database in the file system
– Communicates with Rule Studio (RS) and Rule Team Server (RTS)
Rule Studio
deployment
deployment
Rule Team
Server
Rule Execution
Server
54
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation54
Task 7: Integrate
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
55
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation55
Task 7: What is the Rule Execution Server (RES)?
 Managed environment for executing rules
 Set of independent, but cooperating, software modules that interact with
the rule engine
– Provide management, performance, security, and logging capabilities
 Flexible modular architecture can service different server clients and
integration with enterprise infrastructure
– Enables you to dynamically change business logic in Java SE, Java EE and
SOA environments
– Can handle rule execution for multiple applications
56
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation56
Task 7: Rule Execution Server components
Ruleset change notification
Monitoring data gathering
Execution stack
Management stack
Console
JMX
Execution Components
Rule Studio
Management Model
Execution Unit (XU)
Persistence Layer
Persistence Layer
Database /
File System
Rule Team Server
57
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation57
Task 7: Execution stack
 Execution components: stub components (rule sessions, rule Message
Driven Beans MDB and so on) used in the business logic layer to invoke
rule service execution
 Execution Units: J2EE Connector Architecture-compliant components
that manage rule execution.
– Rule engine pooling (connection management)
– Secure access to rule engines (through rule sessions)
– Ruleset hot update
– Ruleset tracing and monitoring
 Persistence layer: retrieves rulesets from the database for execution.
58
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation58
Task 7: Management and monitoring stack
 Management Console
– The Rule Execution Server is accessed through the Rule Execution Server
Console, a web-based administration interface
– The console acts as an application-specific interface to manage business
rules, including remote browsing, updating and deployment of RuleApps
– Central point of the Rule Execution Server architecture
 JMX Management Model components
– Based on JMX (Java Management eXtension), a part of Java SE
– Responsible for:
• Hot update / deployment: when a new version of a ruleset is deployed, the console
notifies through the JMX control all XUs in the cluster that a new version of the
ruleset is available in database
• Exposing execution statistics as MBeans which can be then monitored using JMX
tools such as IBM Tivoli® software
59
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation59
Task 7: Persistence layer
 File persistence
– Targets the Java SE platform
– Is useful for testing on a single local instance of the application server
 Database persistence
– Recommended option when deploying to a Java EE cluster
60
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation60
Task 7: Ant tasks
 Rule Execution Server provides a series of Management Ant Tasks and
Persistence Ant Tasks for automation purpose
 Use Management Ant tasks to automate RuleApp deployment and undeployment in Rule Execution Server.
 With Persistence Ant tasks, you directly access the persistence layer,
storing or removing rulesets and RuleApps directly in the database,
without passing through the Management stack (JMX)
– If you use Persistence Ant tasks to deploy rulesets or RuleApps, there will be
no notification, no hot deployment, and the Rule Execution Server console
will not be aware of this deployment
61
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation61
Task 7: Integration options
 Application Integration
–
–
–
–
–
J2SE with direct API control
J2SE managed service
J2EE managed service
SCA components
Web Service
External
Client
Service Interface
Session Bean
MDB
Servlet
…
JMS
RMI
IIOP
SOAP
HTTP
Service Implementation
 Data Integration
Local
client
– Java
– XML
 Operating Systems
– Microsoft Windows®
– UNIX® or Linux®
– Mainframe (IBM z/OS®)
 J2EE architecture
–
–
–
–
–
62
Rule Execution Server
Rulesets
+
Metadata
J2EE RES
Standard J2EE service interface for remote clients
In-memory/local invocation for co-hosted clients
POJO application controller
App Server handles security, transactions, session
replication
IBM WebSphere ILOG JRules 7.1.1.0
POJO controller
Management
Stack
.ear
Execution Unit
(XU)
.rar
J2EE
Local
Ruleset
Repository
Runtime
Audit
Trail
© 2010 IBM Corporation
WebSphere ILOG JRules in the SOA Reference
Architecture
Rule integration
Rule authoring, governance,
testing and simulation
Business Innovation & Optimization Services
Rule Solutions for Office
Development
Services
Interaction Services
Process Services
Personalization
Process routing
ESBFacilitates communication
Partner Services
Information Services
Data processing
between services
Business App Services
Rule Execution Server
IT Service
Management
Rule Team Server
Rule Studio
(Eclipse)
Access Services
Complex decision
automation
QoS
Infrastructure Services
63
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
BPM & BRMS interoperability overview
WebSphere ILOG JRules
BPM
Order
Validation
Order parameter
Fraud
Report parameter
Detection
Transparent
Decision
Service
Rule Designer
(for example, exception)
Exception?
Exception
Yes
handling
No
No
Deploy rules
Yes
Order
accepted?
Order validation rules
Fraud detection rules
Review
Process
Computation rules
Rule
Repository
Order
The business logic within business processes changes
more frequently than the business processes themselves
64
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Integration with the IBM WebSphere Process Server
Decision Service Wizard (Service Component Architecture - SCA)
65
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Task 8: Publish
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
66
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation66
Task 8: Publishing to Rule Team Server (1/3)
 Rule Synchronization
– In Rule Studio users edit rule projects stored in an Eclipse
workspace; In Rule Team Server users edit rule projects stored
in the reference rule repository stored in a relational database
– Synchronization goes in both directions
– Differences are managed in the Synchronization perspective of
Eclipse
Project Synchronization
Rule Studio
67
IBM WebSphere ILOG JRules 7.1.1.0
Rule Team
Server
© 2010 IBM Corporation67
Task 8: Publish – Rule projects
 A project is the unit of synchronization between Rule Studio (RS)
and Rule Team Server (RTS)
 The default ruleset extraction maps a rule project to a ruleset
 RTS views one project at a time
 Security settings within RTS are project-specific
68
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation68
Task 12: Audit
Business Rule Application Development
Business Rule Management and Authoring
Architect / Developer / Business Analyst
1
Design
2
Orchestrate
3
Author
4
Test
Business Analyst / Policy Manager / Administrator
8
Rule Studio
5
Publish
9
Manage
Rule Team Server
Rule Solutions for Office
10
11
Deploy
7
Integrate
Validate
Author
Decision Validation Services
Debug
Deploy
6
Rule Execution Server
12
Audit
Java SE / Java EE / SOA
Enterprise Application
Architect / Developer / Administrator
69
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation69
Task 12: Audit – Decision Warehouse
 Traces decisions in production
applications
– Logs execution trace
– Input / Output data
– Execution results
– Executed Tasks
– Rules Fired
– Queries
– Open API to connect third-party
business intelligence (BI) tools
70
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
70
Task 12: Audit – Decision Warehouse
71
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
71
Agenda
 Introduction to Business rule management systems (BRMS)
 Roles-based Tour of ILOG JRules BRMS
– Business user focused activities
– IT user focused activities
 Methodology and Next steps
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
What are the challenges using rules?
 Business involvement and new business processes
– How do I know when rules change?
– Where can I find the rules?
 Data modeling
– What is the business vocabulary?
– Where do my business objects come from?
 Rule acquisition, modeling, and execution
– What is the complexity of rules? How do I write new rules?
– How do I validate the rules?
 Integration, performance, and scalability
– Will I have good performance at full production scale?
– How do I integrate business rules into my IT architecture?
73
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Agile Business Rule Development
 Capture the raw business rules for one
decision service
 Harvest rule using short workshop
sessions
Rule
Discovery
Complement
Rule
Analysis
 Form a set of coherent business rules
applying industry standard benchmarks,
including redundancy and overlap
checks
 Isolate and factor out common rules
Improve
New Rule Set
Rule
Authoring
• Develop domain object model
Enhance
Maintenance
Rule
Validation
• Design a scalable rule repository
structure
• Develop ruleflow, rules, decision tables…
 Test in Sandbox deployment environment
Rule
Deployment
 Involve subject matter expert (SME) for
feedback
 Use rule execution server staging
platform
74
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Discovery Workshop
Business Session
-
Wrap-up Session
Business objectives
Walk thru use cases
ILOG capabilities
Business Goals
Preparation
Meeting
Architecture Session
ILOG Offering
Project
Goals
-
IT issues / goals
IT infrastructure
ILOG technology
ILOG
Offering
Implementation Approach
Implementation Session
-
75
Methodology aspects
High level project plan
Important Milestones
IBM WebSphere ILOG JRules 7.1.1.0
Suggested next steps
© 2010 IBM Corporation
Application Assessment
RIGHT START
Set yourself up for success by planning and designing your BRMS
applications with IBM experts
76
Scope
Experts will interview key SMEs to refine the requirements and use cases, and develop a
proposed architecture, design, and plan. A report with these findings will be presented to
executives.
Context
This is intended for clients who have already identified a target project and use cases and
would like help outlining a plan for building the BRMS application to support this project.
Benefits
●
●
●
Duration
10 days
(23 man-days workload)
Identify the most feasible plan for best meeting the requirements
Set expectations from the beginning
Identify risks and mitigation techniques early on
IBM WebSphere ILOG JRules 7.1.1.0
Resources
1 BRMS Project Manager (PM)
1 BRMS Architect
1 Business Policy Consultant
© 2010 IBM Corporation
Value of BRMS
Improved agility
– Business Decisions and Rules can be more easily accessed and changed
– Business Decisions and Rules can be reused across applications
Improved time to market
– Line of Business Managers can manage and change rules
– Quick response to market and regulatory changes
Management of rule based decisions
– Improved regulatory compliance
– Consistency in applying business decisions across applications
Incremental application modernization
– Incrementally modernize business applications by managing business logic
independently of technical services
77
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
IBM developerWorks - BMRS Resources
Central resource for developers, architects and IT managers to share industry
knowledge, experience and best practices surrounding BRMS.
http://www.ibm.com/developerworks/websphere/zones/brms
78
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
79
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
ITALIAN
TRADITIONAL CHINESE
HINDI
SPANISH
FRENCH
RUSSIAN
JAPANESE
TAMIL
BRAZILIAN PORTUGUESE
THAI
SIMPLIFIED CHINESE
GERMAN
ARABIC
We appreciate your feedback.
Please fill out the survey form in order to improve this educational event.
80
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
Backup Slides
81
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation
“Miniloan” Scenario Background Information
© 2010 IBM Corporation
Objectives
 Learn by example about “Business Rule Management with ILOG
JRules”
 Walk through all the tasks of BR management life cycle
 Exercises divided in three separate laboratories:
– Business Rule Management and Authoring : Focused on the
Business Rule Management activities by business users
– Business Rule Application Development : Focused on the
BRMS development activities by developers
– Enterprise Application : Focused on the BRMS deployment
activities by developers
83
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation83
Scenario: Business Case
 Company profile
– Mid-size mortgage bank
– Sells loans to individuals
 Company objectives
– Build a re-usable risk qualification function for loan applications based
on their corporate business policies and compliant with regulations
– Build a flexible implementation in order to minimize the effort needed
to update these policies
– Involve different roles (analyst, developer, administrator) in policy
maintenance.
84
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation84
Scenario: Functional Architecture
IT users
Business users
Rule based
Integrated
Development
Environment
Rule
Management
Web Application
Web Application
Rule-based
Decision Service
Input/Output
BORROWER
Rule Repository
• Validation rules
• Eligibility rules
LOAN
85
IBM WebSphere ILOG JRules 7.1.1.0
© 2010 IBM Corporation