1. © 2011 IBM Corporation ® Managing Decision services in WebSphere Message Broker using WebSphere ILOG JRules. Amar Shah Mallanagouda Patil December 2011

2. IBM Software Group | WebSphere software Agenda  Need for Business Decision/Rules  Adopting Agile Approach using ILOG-JRules  Benefits of WMB-ILOG integration  Demo

3. © 2011 IBM Corporation Business Decisions are Everywhere… We need to add an eligibility check to meet the requirements of the new regulation. Let’s create a special promotion for our best customers. Can we automate approvals for this type of order? And Changing Frequently Benefit calculationBenefit calculation Fraud assessmentFraud assessment Eligibility Pricing Underwriting Configuration Tax calculationTax calculation Billing Product SelectionProduct Selection Accounting DispositionAccounting Disposition Compliance ScreeningCompliance Screening Documentation RequirementsDocumentation Requirements Commissions / RoyaltiesCommissions / Royalties Up-sell/Cross-sell offerUp-sell/Cross-sell offer Improve agility and time to market

4. © 2011 IBM Corporation Issues Rules are hidden in code or isolated within the organization Changes are hard to track and maintain over time Rules used by systems have to be programmed and require IT resources Duplication and multiple versions of the same rules Lack of auditability, traceability Decision changes cannot be easily tested or simulated The traditional (ad hoc) approach of dealing with rule changes leads to… Traditional Approach for Managing Decision Change  Reduced organizational agility  Reduced employee productivity  Increased load on IT Where Business Rules Typically Exist Applications Processes People Documents Improve agility and time to market

5. © 2011 IBM Corporation A More Agile Approach with BRMS Business Rules may already exist in Message Flows ? Smart Routing Validation Transformation B usiness R ule M anagement S ystem Rule Execution Rule Repository User Tools  Adapt faster to ongoing change requirements –Respond to customer and industry demands by deploying rule changes independently from message flow update cycles  Reduce load on IT development –Express decision logic in business language terms to enable your business team to participate in policy changes –Validate rules execution without the need to retest the whole message flow Extract decision logic from custom ESQL, Java code and databases

6. © 2011 IBM Corporation More customized, consistent decisions Reduced lead time for changes Better business and IT alignment Greater compliance through transparency and auditability Extreme Reliability Fast and Flexible Application Integration Ability to integrate disparate systems and technologies Reduced Integration Costs WMBILOG BRMS Combine the Benefits of WebSphere Message Broker and WebSphere ILOG BRMS for Maximum Business Flexibility Integration & data enrichmentManage Business Decisions

7. © 2011 IBM Corporation Separate Message Broker Flow and Rule Lifecycles Functional Requirements Functional Enhancements / Platform Upgrades Functional Enhancements / Platform Upgrades Business policies Business policies Business policy and rule changes Business policy and rule changes Business policy and rule changes Business policy and rule changes Business policy and rule changes Business policy and rule changes In-Production Message Flow Application Synchronization Business Rule Management Message Flow Development Business policy and rule changes Business policy and rule changes Message Flow Developer Business & IT Functions / Tasks / Flow changes in Weeks / Months Decisions / Policies Changes in Days / Weeks

8. © 2011 IBM Corporation WebSphere ILOG JRules enables Message Broker customers to: WebSphere ILOG JRules augments WMB functionality  Specify dynamic routing in intuitive business terms Portal Rule-based Business Decisions BPM System Enterprise Application Destination Business Application Destination Business Application  Augment and transform messages based on business decisions  Provide business level validation rules for messages

9. © 2011 IBM Corporation Adding Rule Team Server gives WMB customers choice to: Align Business and IT on Decisions and Rules Rule-based Business Decisions View rules Change rules IT Users Business Users Author rules Design Message Flows Rule Team Server Repository Rule Solutions for Office  Provide visibility of business rules to Business Users via Web interface  Provide selective rule authoring ability to Business Users via Web interface –E.g. IT can enable rule parameters to be changed by business Rule Solutions for Office extends Rule Team Server capabilities – Provides capabilities to author and change rules using familiar desktop tools

10. © 2011 IBM Corporation Rule-based Business Decisions WebSphere Message Broker extends BRMS connectivity WebSphere Message Broker enables BRMS customers to:  Transform Decision requests from multiple sources to a common format to invoke common decision services Portal BPM System Enterprise Application Rule-based Business Decisions  Enrich decision requests with additional data prior to invoking decision  Enable virtualization of decision services

11. © 2011 IBM Corporation JRules via Web service Use Message Broker support for Web services to make an external call out to a Rule Execution Server JRules via JMS call Use Message Broker support for JMS to make an external call out to a Rule Execution Server JRules Java SE engine Deploy a core JRules rule engine in a Message Broker JVM and access the rule engine directly with the JRules API JRules Java SE Rule Execution Server Deploy a JRules Rule Execution Server in a Message Broker JVM and access the rules via the Rule Session API Runtime Options for Integrating Message Broker & JRules

12. © 2011 IBM Corporation  Scenario Use SOAP node in Message Broker to call a Rule App in WAS as a Web Service either via a:  Hosted Transparent Decision Service in JRules, or  Native Web Service in WAS – Full capability JRules Execution Server – Allows Broker to integrate with deployed rules – Loosely coupled decisions/rules can be easily shared & re-used across other applications  Benefits of this Approach Required support is available today Standards-based integration Decisions can be re-used/shared with other systems Message Flow SOAP Request RuleApp SOAP / HTTP Message Broker calling JRules via Web Service WebSphere Application Server (WAS) Message Broker V7.0 Rule Execution Server V7 Web Service

13. © 2011 IBM Corporation Demo

14. © 2011 IBM Corporation Questions? And Thank you!

15. © 2011 IBM Corporation

19. To earn Loyalty points, credit should be > 200

20. © 2011 IBM Corporation

21. The Min Balance Req is > 500