DOCSLIB.ORG

Drools Expert User Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Drools Expert User Guide Drools Expert User Guide ....................................................................................................................................... vii 1. The Rule Engine .......................................................................................................... 1 1.1. What is a Rule Engine? ...................................................................................... 1 1.1.1. Introduction and Background .................................................................... 1 1.2. Why use a Rule Engine? .................................................................................... 6 1.2.1. Advantages of a Rule Engine ................................................................... 6 1.2.2. When should you use a Rule Engine? ....................................................... 7 1.2.3. When not to use a Rule Engine ................................................................ 8 1.2.4. Scripting or Process Engines .................................................................... 8 1.2.5. Strong and Loose Coupling ...................................................................... 9 2. Quick Start ................................................................................................................. 11 2.1. The Basics ....................................................................................................... 11 2.1.1. Stateless Knowledge Session ................................................................. 11 2.1.2. Stateful Knowledge Session .................................................................... 14 2.2. A Little Theory .................................................................................................. 19 2.2.1. Methods versus Rules ............................................................................ 19 2.2.2. Cross Products ...................................................................................... 20 2.2.3. Activations, Agenda and Conflict Sets. .................................................... 21 2.2.4. Inference ............................................................................................... 26 2.2.5. Inference and TruthMaintenance ............................................................. 28 2.3. More on building and deploying ......................................................................... 30 2.3.1. Knowledge Base by Configuration Using Changesets ............................... 30 2.3.2. Knowledge Agent ................................................................................... 31 3. Advanced Concepts and Theory ............................................................................... 35 3.1. Truth Maintenance with Logical Objects ............................................................. 35 3.1.1. Example Scenario .................................................................................. 37 3.1.2. Lazy Truth Maintenance ......................................................................... 38 3.1.3. Important note: Equality for Java objects ................................................. 38 3.2. Rete Algorithm .................................................................................................. 38 4. User Guide ................................................................................................................. 45 4.1. Building ............................................................................................................ 45 4.1.1. Building using Code ............................................................................... 46 4.1.2. Building using Configuration and the ChangeSet XML .............................. 49 4.2. Deploying ......................................................................................................... 52 4.2.1. KnowledgePackage and Knowledge Definitions ........................................ 52 4.2.2. KnowledgeBase ..................................................................................... 53 4.2.3. In-Process Building and Deployment ....................................................... 55 4.2.4. Building and Deployment in Separate Processes ...................................... 56 4.2.5. StatefulknowledgeSessions and KnowledgeBase Modifications ................. 57 4.2.6. KnowledgeAgent .................................................................................... 57 4.3. Running ............................................................................................................ 61 4.3.1. KnowledgeBase ..................................................................................... 61 4.3.2. StatefulKnowledgeSession ...................................................................... 62 4.3.3. KnowledgeRuntime ................................................................................. 62 iii Drools Expert User Guide 4.3.4. Agenda .................................................................................................. 71 4.3.5. Event Model .......................................................................................... 76 4.3.6. KnowledgeRuntimeLogger ...................................................................... 78 4.3.7. StatelessKnowledgeSession .................................................................... 79 4.3.8. Commands and the CommandExecutor ................................................... 83 4.3.9. Marshalling ............................................................................................ 91 4.3.10. Persistence and Transactions ............................................................... 93 4.3.11. Drools Clips ......................................................................................... 95 5. The Rule Language .................................................................................................... 97 5.1. Overview .......................................................................................................... 97 5.1.1. A rule file ............................................................................................... 97 5.1.2. What makes a rule ................................................................................. 97 5.2. Keywords ......................................................................................................... 98 5.3. Comments ...................................................................................................... 100 5.3.1. Single line comment ............................................................................. 100 5.3.2. Multi-line comment ............................................................................... 101 5.4. Error Messages .............................................................................................. 101 5.4.1. Message format ................................................................................... 101 5.4.2. Error Messages Description .................................................................. 102 5.4.3. Other Messages ................................................................................... 106 5.5. Package ......................................................................................................... 106 5.5.1. import .................................................................................................. 107 5.5.2. global .................................................................................................. 108 5.6. Function ......................................................................................................... 109 5.7. Type Declaration ............................................................................................. 110 5.7.1. Declaring New Types ........................................................................... 111 5.7.2. Declaring Metadata .............................................................................. 113 5.7.3. Declaring Metadata for Existing Types ................................................... 115 5.7.4. Parameterized constructors for declared types ....................................... 115 5.7.5. Non Typesafe Classes .......................................................................... 116 5.7.6. Accessing Declared Types from the Application Code ............................. 116 5.7.7. Type Declaration 'extends' .................................................................... 117 5.8. Rule ............................................................................................................... 118 5.8.1. Rule Attributes ..................................................................................... 119 5.8.2. Timers and Calendars .......................................................................... 123 5.8.3. Left Hand Side (when) syntax ............................................................... 124 5.8.4. The Right Hand Side (then) .................................................................. 171 5.8.5. A Note on Auto-boxing and Primitive Types ........................................... 174 5.9. Query ............................................................................................................. 174 5.10. Domain Specific Languages ........................................................................... 177 5.10.1. When to Use a DSL ........................................................................... 177 5.10.2. DSL Basics ........................................................................................ 178 5.10.3.
Load more

Recommended publications
  • K-SITE RULES: Integrating Business Rules in the Mainstream Software Engineering Practice
    K-SITE RULES: Integrating Business Rules in the mainstream software engineering practice José L. Martínez-Fernández(2), José C. González(1,2), Pablo Suárez(2) (1) DAEDALUS – Data, Decisions and Language, S.A., Avda. Albufera 321, Madrid, Spain [email protected], [email protected], [email protected] (2) ETSI Telecomunicación, Universidad Politécnica de Madrid Keywords: Business rules, rule engine, rule language, software development lifecycle models. Abstract: The technology for business rule based systems faces two important challenges: standardization and integration within conventional software development lifecycle models and tools. Despite the standardization effort carried out by international organizations, commercial tools incorporate their own flavours in rule languages, making difficult the migration among tools. On the other hand, although some business rules systems vendors incorporate interfaces to encapsulate decision models as web services, it is still difficult integrating business rules in traditional object-oriented analysis and design methodologies. This is the rationale behind the development of K-Site Rules, a tool that facilitates the cooperation of business people and software designers in business applications. 1 INTRODUCTION accessible storage, and this knowledge can be modified, updated and maintained in a quick and A Business Rule (BR) can be seen as an expression simple way. Second, companies need ways to foster used to make explicit the knowledge about the their reaction to new business opportunities, and the business present in an organization. According to the ability to adapt their IT systems to take benefit of Business Rules Group1 two definitions can be given these opportunities becomes a definitive advantage. for the term business rule, depending on the point of Third, from the IT perspective, the use of business view adopted: from the business point of view, rules allows a reduction of the effort needed to adapt where a business rule is “a directive, intended to software systems to new requirements.
    [Show full text]
  • Drools Expert User Guide
    Drools Expert User Guide Version 5.5.0.CR1 by The JBoss Drools team [http://www.jboss.org/drools/team.html] ....................................................................................................................................... vii 1. Introduction ................................................................................................................. 1 1.1. Artificial Intelligence ............................................................................................ 1 1.1.1. A Little History ......................................................................................... 1 1.1.2. Knowledge Representation and Reasoning ................................................ 2 1.1.3. Rule Engines and Production Rule Systems (PRS) .................................... 3 1.1.4. Hybrid Reasoning Systems (HRS) ............................................................ 5 1.1.5. Expert Systems ........................................................................................ 8 1.1.6. Recommended Reading ........................................................................... 9 1.2. Why use a Rule Engine? .................................................................................. 12 1.2.1. Advantages of a Rule Engine ................................................................. 13 1.2.2. When should you use a Rule Engine? ..................................................... 14 1.2.3. When not to use a Rule Engine .............................................................. 15 1.2.4. Scripting
    [Show full text]
  • Business Rules White Paper Version D0.2 June 2012
    NHSIA Business Rules White Paper Version D0.2 June 2012 Prepared for the Administration for Children and Families (ACF) National Human Services Interoperability Architecture Business Rules White Paper DRAFT Version D0.2 June 2012 Prepared by: The Johns Hopkins University Applied Physics Laboratory (JHU/APL) i NHSIA Business Rules White Paper Version D0.2 June 2012 Draft Issue It is important to note that this is a draft document. The document is incomplete and may contain sections that have not been completely reviewed internally. The material presented herein will undergo several iterations of review and comment before a baseline version is published. This document is disseminated in the interest of information exchange. The Johns Hopkins University Applied Physics Laboratory (JHU/APL) assumes no liability for its contents or use thereof. This report does not constitute a standard, specification, or regulation. JHU/APL does not endorse products or manufacturers. Trade and manufacturer’s names appear in this report only because they are considered essential to the object of this document. Note: This document and other NHSIA-related documentation are available for review from the NHSIA SharePoint site. Updates and any additional documents will be published on that site. The URL for the site is https://partners.jhuapl.edu/sites/HSNIA. The version D0.1 and D0.2 documents may be viewed or downloaded from the document library named NHSIA_Drafts. Review and comments to this document are welcome. To comment, either post your feedback in the NHSIA_Drafts_Comments library or send comments to [email protected]. Christine Salamacha The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Road Laurel, MD 20723 Phone: 240-228-4976 E-Mail: [email protected] ii NHSIA Business Rules White Paper Version D0.2 June 2012 Table of Contents List of Figures ...............................................................................................................
    [Show full text]
  • Design and Implementation of a Service-Oriented Business Rules Broker
    Design and Implementation of a Service-Oriented Business Rules Broker Florian Rosenberg and Schahram Dustdar Vienna University of Technology Distributed Systems Group, Information Systems Institute 1040 Vienna, Argentinierstrasse 8/184-1, Austria {rosenberg, dustdar}@infosys.tuwien.ac.at Abstract of the business logic, because business rules tend to change quite frequently. Different research efforts exist which try Business rules define or constrain some business [24]. to extract business rules from existing applications [28]. Many different business rules engines exist to capture and The usage of a business rules engine using different manage the rules that comprise ones business. The lack of knowledge bases can greatly improve the maintainability standards in the business rule area leads to different en- in such cases. Such an engine handles the execution and gine implementations and various rule representation for- management of business rules. The administration of rules mats. Furthermore, accessing rule-based knowledge in a should ideally be performed by domain experts or business uniform way from different heterogeneous applications in analysts (depending on the rule language used for author- an enterprise computing environment poses many integra- ing). The necessity of business rules, especially in the elec- tion challenges. In this paper, we propose the design and tronic commerce domain, is stated in [1] by the following implementation of a service-oriented approach on how to two factors: Firstly, an increased competition requires fre- integrate different heterogeneous business rule engines by quent changes in cooperate policies and strategies to remain using our Business Rules Broker architecture. Furthermore, competitive. This means that changes have to be made fast we present a method to automatically expose the rule-based to react to market changes (e.g., changing insurance poli- business knowledge as Web services by generating the Web cies).
    [Show full text]
  • Business Rules Engine 1 Business Rules Engine
    Business rules engine 1 Business rules engine A business rules engine is a software system that executes one or more business rules in a runtime production environment. The rules might come from legal regulation ("An employee can be fired for any reason or no reason but not for an illegal reason"), company policy ("All customers that spend more than $100 at one time will receive a 10% discount"), or other sources. A business rule system enables these company policies and other operational decisions to be defined, tested, executed and maintained separately from application code. Rule engines typically support rules, facts, priority (score), mutual exclusion, preconditions, and other functions. Rule engine software is commonly provided as a component of a business rule management system which, among other functions, provides the ability to: register, define, classify, and manage all the rules, verify consistency of rules definitions (”Gold-level customers are eligible for free shipping when order quantity > 10” and “maximum order quantity for Silver-level customers = 15” ), define the relationships between different rules, and relate some of these rules to IT applications that are affected or need to enforce one or more of the rules. IT use In any IT application, business rules change more frequently than the rest of the application code. Rules engines or inference engines are the pluggable software components that execute business rules that have been externalized from application code as part of a business rules approach. This externalization of business rules allows the business users to modify the rules frequently without the need of IT intervention. The system as a whole becomes more adaptable with business rules that can be changed dynamically, although QA and other testing would still be required.
    [Show full text]
  • Chapter 12 –Business Rules and DROOLS
    SOFTWARE ARCHITECTURES Chapter 12 –Business Rules and DROOLS Katanosh Morovat Introduction In the recent decade, the information systems community declares a new concept which is called business rules. This new concept is a formal approach for identifying the rules that encapsulate the structure, constraint, and control the operation as a one package. Before advent of this definition, system analysts have been able to describe the structure of the data and functions that manipulate these data, and almost always the constraints would be neglected. Business rules are statements that precisely describe, constrain, and control the structure, operations and strategies of a business in an organization. Other terms which come with business rules, are business rules engine, and business rules management system. Business rules engine which is a component of business rules management system is a software system that executes a set of business rules. Business rules management system monitors and maintains the variety and complexity of decision logic that is used by operational systems within an organization or enterprise. This logic is referred to as business rules. One of more widely used business rules management system is Drools, more correctly known as a production rules system. Drools use an enhanced implementation of the Rete algorithm. Drools support the JSR-94 standard for its business rules engine and enterprise framework for the construction, maintenance, and enforcement of business policies in an organization, application, or service. This paper describes the nature of business rules, business rules engine, and business rules management system. It also prepares some information about the Drools, included several projects, which is a software system prepared by JBoss Community, and different productions made by Logitech which have used the business rules method.
    [Show full text]
  • Business Rules Management Systems
    BUSINESS RULES MANAGEMENT SYSTEMS Cliffred van Velzen Table of Contents 1. Introduction ...................................................................................................................... 3 1.1. Business rule management systems .............................................................................. 3 1.2. Research questions .............................................................................................................. 5 1.3. Methodology ........................................................................................................................... 5 2. Business Rules .................................................................................................................. 7 2.1. What are business rules? ................................................................................................... 7 2.2. Why should we care? ......................................................................................................... 10 2.3. Business Rule Approach ................................................................................................... 12 2.4. Concluding remarks ........................................................................................................... 13 3. Business rules management systems .................................................................... 14 3.1. History .................................................................................................................................... 14 3.2. Business rules management
    [Show full text]
  • Introducing a Rule-Based Architecture for Workflow Systems in Retail Supply Chain
    INTRODUCING A RULE-BASED ARCHITECTURE FOR WORKFLOW SYSTEMS IN RETAIL SUPPLY CHAIN MANAGEMENT Master’s (one year) thesis in Informatics (15 credits) Sheng Li Spring 2012 2011MAGI24 Title: Introducing a rule-based architecture for workflow systems in retail supply chain management Year: 2012 Author: Sheng Li Supervisor: Mikeal Lind Abstract Problem: While global IT competition is becoming increasingly severe, various business organizations and companies, in order to maximize the profit and gain market competitiveness, are in urgent need of high-performance workflow systems to improve efficiency. However, the workflow systems that are currently used are embedded with fixed business rules that cannot be easily adjusted by users, resulting in the inability of users to make adjustments to the business rules, so as to satisfy changed requirements and deal with high cost of business management and low efficiency. Therefore, it is highly desirable for users of workflow systems, especially retail supply chain companies, to employ a new type of systems that can be easily adjusted by end users themselves when required. Solution: The rule-based workflow system architecture for the management of retail supply chain business process is recommended. In such architecture, the business rules can be separated from the system logic and managed by users via a friendly interface. The rule-based workflow systems can greatly enhance the system efficiency and lower maintenance cost, as compared with the traditional workflow system or other similar information systems. And the efficiency of retail supply chain business process management can be greatly enhanced by employing rule-based workflow systems. Methods: Two main research problems and four sub-research problems, which serve as the guidance to conduct related research work, have been identified.
    [Show full text]