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)

 Real-time decisions with BRMS

The standard deployment scenario for a BRMS application includes the following steps:

  1. Create POJO fact classes.
  2. Creating business rules.
  3. Use the KIE API to create a KieContainer or the production memory, which is a repository holding the whole knowledge of the application.
  4. Create a KieSession object to maintain a conversation state with the Business Engine.
  5. Insert POJO Facts in the session.
  6. Fire rules.
  7. Handle Facts.

For an external application, there are various mechanisms to interact with a business rule:

  • The fat jar approach: This is the possibility given to developers to incorporate rules in their applications, code and provide a single deployment unit. Once a rule or code changes, the whole package needs to be redelivered. This option relies on the KieService API provided to load business rules from the application classpath.
  • The second...