Business rules and processes can help your business by providing a level of agility and flexibility. As a developer, you will be largely responsible for implementing these business rules and processes effectively, but implementing them systematically can often be difficult due to their complexity. Drools makes the process of implementing these rules and processes quicker and handles the complexity, making your life a lot easier!
This book guides you through various features of Drools, such as rules, processes, decision tables, complex event processing, Drools Rete implementation with various optimizations, and others. It will help you to set up the Drools platform and start creating your own business. It's easy to start developing with Drools if you follow our real-world examples that are intended to make your life easier.
Starting with an introduction to the basic syntax that is essential for writing rules, the book will guide you through validation and human-readable rules that define, maintain, and support your business agility. As a developer, you will be expected to represent policies, procedures, and constraints regarding how an enterprise conducts its business; this book makes it easier by showing you the ways in which it can be done.
A real-life example of a banking domain allows you to see how the internal workings of the rules engine operate. A loan approval process example shows the support of processes within Drools. Parts of a banking fraud detection system are implemented with the Drools Fusion module, which is the complex event processing part of Drools. This, in turn, will help developers to work on preventing fraudulent users from accessing systems in an illegal way.
Finally, more technical details are shown on the inner workings of Drools, the implementation of the ReteOO algorithm, indexing, and node sharing.
Chapter 1, Programming Declaratively, introduces the reader into the domain of business rules and business processes. It talks about why standard solutions fail at implementing complex business logic. We will also see a possible solution in the form of a declarative programming model. The chapter talks about its advantages and disadvantages. A brief history of Drools is also mentioned.
Chapter 2, Writing Basic Rules, shows us the basics of working with the Drools rule engine, Drools Expert. It starts with a simple example that is explained step-by-step. It begins with the development environment setup, writing a simple rule and then executing it. The chapter goes through some necessary keywords and concepts that are needed for more complex examples.
Chapter 3, Validating, introduces the reader to a banking domain that will be the basis for examples later in this book. The chapter then goes through an implementation of a decision service for validating this banking domain. A reporting model is designed that holds reports generated by this service.
Chapter 4, Transforming Data, shows how Drools can be used for doing complex data transformation tasks. It starts with writing some rules to load the data, continues with the implementation of various transformation rules, and finally, puts together the results of this transformation. The chapter shows how we can work with a generic data structure such as a map in Drools.
Chapter 5, Creating Human-readable Rules, focuses on rules that are easy to read and change. Starting with domain-specific languages, the chapter shows how to create a data transformation-specific language. Next, it focuses on decision tables as another more user friendly way of representing business rules. An interest rate calculation example is shown, and finally, the chapter introduces the reader to jBPM as a way of managing the rule execution order.
Chapter 6, Working with Stateful Session, talks about executing the validation decision service in a stateful manner. The validation results are accumulated between service calls. This shows another way of interacting with a rule engine. Logical assertions are used to keep the report up-to-date. Moreover, various ways to serialize a stateful session are discussed.
Chapter 7, Complex Event Processing, goes through various features such as events, type declarations, temporal operators, sliding windows, and others. Drools Fusion, another cornerstone of the Drools platform, is about writing rules that react to various events. The power of Drools Fusion is shown on a banking fraud detection system.
Chapter 8, Defining Processes with jBPM, goes into more detail about the workflow aspect of the Drools platform. It is shown on a loan approval service that demonstrates the use of various nodes in a flow. Among other things, the chapter talks about implementing a custom work item, human task, and a subflow.
Chapter 9, Building a Sample Application, shows you how to integrate Drools in a real web application. We'll go through the design and implementation of persistence, business logic, and presentation layers. All examples written so far will be integrated into this sample application.
Chapter 10, Testing, aims to give you an idea of various ways of how to test your business logic. Starting with unit testing, integration testing through acceptance testing will be shown on the business rules management server (Guvnor). The chapter provides useful advice on various troubleshooting techniques.
Chapter 11, Integrating, shows integration with the Spring framework. It describes how we can make changes to rules and processes while the application runs. It shows how to use an external build tool such as Ant to compile rules and processes. It talks about the rule execution server that allows us to execute rules remotely. It also briefly mentions support of various standards.
Chapter 12, Learning about Performance, takes us under the hood of the Drools rule engine. By understanding how the technology works, you'll be able to write more efficient rules and processes. It talks about the ReteOO algorithm, node sharing, node indexing, and left/right unlinking.
Appendix A, Setting Up the Development Environment, lists the various steps required to get you up and running with Drools.
Appendix B, Creating Custom Operator, shows an implementation of a custom operator that can be used to simplify our rules.
Appendix C, Dependencies of Sample Application, lists various dependencies used by the sample application.
In order to learn Drools and run the examples in this book, you'll need a computer with any operating system (Windows, Mac, or Linux), Java Development Kit (JDK) Version 1.5 or later, Drools binary distribution, some IDE—preferably Eclipse IDE for Java EE developers, Drools and jBPM plugins for Eclipse, and some third-party libraries that will be specified per chapter. All the mentioned software is freely available on the Internet under a business friendly license.
You can download some additional support material from http://code.google.com/p/droolsbook/.
The book is for Java developers who want to create rules-based business logic using the Drools platform. Basic knowledge of Java is essential.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text are shown as follows: "Let's say that we have the Account bean that has one property called balance."
A block of code will be set as follows:
if (customer.getLevel() == Level.Gold) {
// do something for Gold customer
} else if (customer.getLevel() == Level.Silver) {
if (customer.getAccounts() == null) {
// do something else for Silver customer with no accounts
} else {
for (Account account : customer.getAccounts()) {
if (account.getBalance < 0) {
// do something for Silver Customer that has // account with negative balance
}
}
}
}New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Clicking on the Next button moves you to the next screen".
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title via the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files for all Packt books you have purchased from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the erratasubmissionform link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.