Business Rules Forum 2006 : Mission Critical BRMS

1,090 views

Published on

Daniel will present the technical design philosophy behind ILOG JRules as well as the general requirements for BRMS deployment within mission critical enterprise systems. In this wide-ranging presentation Daniel will outline many of the factors that ensure a successful BRMS deployment, for small projects, departmental applications and enterprise-wide solutions.

Topics covered include:
- Project Build Automation
- Best Practices for Software Change Management
- Hot, Cold and Staged Deployment
- Integration of Unit and Regression Testing
- Transaction Boundaries
- Enforcing Runtime Security
- Scaling-out to Meet Demand
- 24x7 Management, Monitoring and Service Level Agreements
- Server Replication and Disaster Recovery

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,090
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Business Rules Forum 2006 : Mission Critical BRMS

  1. 1. Mission Critical BRMS Daniel Selman dselman@ilog.fr
  2. 2. Agenda  About Me  Why “Mission Critical”?  People and Processes (Governance)  Architecture and Deployment  Service Oriented Architecture  Configuration Management  Full Lifecycle Support  Unit and Regression Testing  Security  Performance  Scalability  High Availability  Administration  Conclusions  Q&A © ILOG, All rights reserved 2
  3. 3. About Me: Daniel Selman  Product Manager, ILOG  JRules 4.6 onward, specialized in performance, enterprise integration and developer requirements  Architect, BEA Systems, WebLogic Portal  Rule engine for personalization/security  Data Synchronization for SOA  Product Catalog  Specification Lead, JSR-94  Editor http://javarules.org  Author “Java 3D Programming”  © ILOG, All rights reserved 3
  4. 4. Why “Mission Critical”?  Mission critical applications are:  On the critical path for processing everyday business transactions  Decisions (execution results) are time critical  Failures in mission critical applications incur heavy financial costs, or erode business reputation.  ILOG examples (some…)  Equifax (credit scoring/decision making)  eBay (customer satisfaction)  Travelocity (travel planning)  St. Paul Travelers Insurance (automated underwriting)  JP Morgan Chase (CRM, processing 70M accounts)  Brokerage (automated trading system)  Credit card company (fees calculation, message routing)  Car rental company (pricing) © ILOG, All rights reserved 4
  5. 5. Rules are Critical! © ILOG, All rights reserved 5
  6. 6. Rules are Critical! © ILOG, All rights reserved 6
  7. 7. Rules are Critical! © ILOG, All rights reserved 7
  8. 8. Rules are Critical! © ILOG, All rights reserved 8
  9. 9. Rules are Critical! © ILOG, All rights reserved 9
  10. 10. Rules are Critical! © ILOG, All rights reserved 10
  11. 11. Rules are Critical! © ILOG, All rights reserved 11
  12. 12. Rules are Critical! © ILOG, All rights reserved 12
  13. 13. Building Mission Critical Applications! © ILOG, All rights reserved 13
  14. 14. People and Processes Servers, routers, networks, Reporting, routing… statistics, data S Code analysis Administration coverage, Scripting, Java, C#, M Simulation / BI Regression Data Testing structures, Testing Algorithms, R Integration Development B Standards, Processes, Architecture IT portfolio Requirements Analysis elucidation, Impact assessment, Requirements Strategy, Modeling Competition, Business impact Application Lifecycle © ILOG, All rights reserved 14
  15. 15. Architecture and Deployment  The “Architect Knows Best” Principle  Don’t impose design decisions on a context you don’t fully understand. All customers are different.  Examples  Calling rule engine from: JSP, Cold Fusion, Message Oriented Middleware, Batch application, J2EE middleware, ESB, SAP, BPM, SOA, mainframe etc.  Requirements:  A range of integration options to cover many scenarios (WS, stateful, stateless, sync, async, tx…) © ILOG, All rights reserved 15
  16. 16. Integration into Enterprise Architecture Best of breed BPM/SOA solutions involves partnership  ILOG allows BRMS Decision Services to be easily integrated with the leading BPM and SOA platforms. © ILOG, All rights reserved 16
  17. 17. Configuration Management  Of software  Automate building testable software from source code  Of systems  Setup and tear-down servers as efficiently as possible  Requirements:  Integrate rules artifacts into configuration management repository  Automate extracting rules from rule repository and deploy  Easily replicate configuration data from development servers to staging or production servers © ILOG, All rights reserved 17
  18. 18. Full Lifecycle Support  Version 1.0 of app in production  Policy Managers editing rules  Version 1.5 of app in development  Developers building new integration capabilities  Analysts defining new business object models  Developers/analysts refactoring rules  Requirements  Synchronization of rule repositories  Object Model Evolution (BOM, XOM, B2X) © ILOG, All rights reserved 18
  19. 19. Unit and Regression Testing  Continuous Integration  Integrate software modules early, often and continuously  Includes business rules  Requirements:  Automate running tests on code or rules  Unit tests written by developers (code) or policy managers (rules)  Regression tests written by QA (code) or policy managers/QA (rules) © ILOG, All rights reserved 19
  20. 20. Rule Scenario Manager © ILOG, All rights reserved 20
  21. 21. Security  Authentication  Who are you?  Authorization  Are you allowed to do that?  Requirements:  BRMS integration with enterprise user registry (LDAP etc)  Fine-grained permissions to protect access to business rules resources (Access Control Language) | NOUN | VERB | PERMISSION | | DECISION TABLE | EDIT | PolicyManagers |  Follow Enterprise “best practices” (SSL, password management etc) © ILOG, All rights reserved 21
  22. 22. Team Server Security Model © ILOG, All rights reserved 22
  23. 23. Performance  Is a constraint…  Is it “good enough”?  Involves difficult trade-offs (time, money, hardware, maintainability, future-proofing, scalability, testability…)  Recasting a “slow” problem can often provide a “fast” solution  Requirements:  Understand your performance profile (bottlenecks)  A “fast” rule engine offering a variety of optimizations and algorithms (e.g RetePlus, Fastpath, Sequential)  Multi-threaded (concurrent) performance  A “productive” rule management environment for your target number of rules © ILOG, All rights reserved 23
  24. 24. Performance of Compliance Rules 250  Processing 10,000 objects 200  Single-threaded Seconds 150  Dell D600 1.7 Ghz 100  Linux  Sun JDK 5 50 0 5,000 10,000 15,000 20,000 rules rules rules rules Java code Sequential Fastpath © ILOG, All rights reserved 24
  25. 25. Scalability  Can you “throw hardware at the problem”?  Does doubling system capacity double throughput?  Usually the answer is no, because most real-world performance profiles are not that simple  Requirements:  Support for applications virtualized across multiple servers (clustering)  Clustered hot deployment  BRMS designed for multi-threaded, highly concurrent access © ILOG, All rights reserved 25
  26. 26. Monitoring Clustered Rule Engines © ILOG, All rights reserved 26
  27. 27. High Availability  Avoid a single point of failure:  Support for clustering and state replication  Deployment of BRE/BRMS to two or more geographically distributed data centers  Requirements:  Server configuration replication  Easy deployment of rules to multiple data centers  Automatic fail-over of execution components  Minimize per-server impact of hot-deployment © ILOG, All rights reserved 27
  28. 28. Administration  Applications are typically developed in months, but run for years  Administration tools are a great way to increase ROI  Requirements:  What rules are deployed?  Monitor execution performance (on each machine)  Support for rolling back deployments  Integration with management consoles (Tivol/OpenView)  Define QoS alerts © ILOG, All rights reserved 28
  29. 29. Integration with JMX Tools © ILOG, All rights reserved 29
  30. 30. Conclusions  Mission critical applications bring a tough set of challenges to the table.  Building robust systems requires thinking transversally: across the IT infrastructure, the development process, roles and responsibilities.  The BRMS (both rule authoring and rule execution) must provide the tools, processes and integration capabilities to meet these challenges.  Try not to forget the simple cases! © ILOG, All rights reserved 30
  31. 31. For additional information Daniel Selman Product Manager, ILOG e-mail: dselman@ilog.fr web: http://www.ilog.com Whitepaper: Deploying Rule Application with ILOG JRules: http://www.ilog.com/products/jrules/whitepapers/ © ILOG, All rights reserved 31
  32. 32. Questions © ILOG, All rights reserved 32

×