Book Image

JBoss: Developer's Guide

By : Elvadas Nono Woguia
Book Image

JBoss: Developer's Guide

By: Elvadas Nono Woguia

Overview of this book

Have you often wondered what is the best JBoss product to solve a specific problem? Do you want to get started with a specific JBoss product and know how to integrate different JBoss products in your IT Systems? Then this is the book for you. Through hands-on examples from the business world, this guide presents details on the major products and how you can build your own Enterprise services around the JBoss ecosystem. Starting with an introduction to the JBoss ecosystem, you will gradually move on to developing and deploying clustered application on JBoss Application Server, and setting up high availability using undertow or HA proxy loadbalancers. As you are moving to a micro service archicture, you will be taught how to package existing Java EE applications as micro service using Swarm or create your new micro services from scratch by coupling most popular Java EE frameworks like JPA, CDI with Undertow handlers. Next, you will install and configure JBoss Data grid in development and production environments, develop cache based applications and aggregate various data source in JBoss data virtualization. You will learn to build, deploy, and monitor integration scenarios using JBoss Fuse and run both producers/consumers applications relying on JBoss AMQ. Finally, you will learn to develop and run business workflows and make better decisions in your applications using Drools and Jboss BPM Suite Platform.
Table of Contents (10 chapters)

Authoring business rules with JBoss BRMS

In a declarative programming style, the raw material comprises mainly business rules and facts. A business rule is a statement derived from propositional and first-order logic (for example, if <conditions>, then <actions>) to express system knowledge. The inference engine applies pattern matching algorithms on rules and data facts present in the working memory to infer conclusions that lead to actions. Facts are mainly expressed as plain Java object models:

Rules reside in a space called the production memory, whereas facts are kept in the working memory. On applying pattern-matching algorithms, new facts can be generated, updated or removed from the working memory. Two rules are said to be in conflict when they both are true for the same fact assertion--an Agenda is important to manage execution orders in case of conflicts...