Summary

In this chapter, we covered the main classes that we will be using to bootstrap, configure, and manage our Rule Engine instances. The first half of the chapter covered how different approaches can be used to define the rules that will be available to each rule engine instance. We also took a look at how Drools can load everything from the classpath and how the KIE-CI module can be used to delegate the KieModules resolution into Maven. We also covered how important the hierarchical structures of KieModules are and how they can be used to group different set of rules so that they can be loaded in the same container, to be used together. The second half of the chapter covered how to update our business knowledge (rules, processes, and so on) using the KieScanner to update the modified assets. This is a quite common requirement due the fact that we need to be able to update the business knowledge quickly so that we can adapt and deal with real-life business changes.

In the next chapter, we will cover more advanced rule structures in order to be able to provide more complex solutions to more complex business needs. We will continue developing our eShop scenario into a more complex application.