Skip to main content

JBoss Fuse integration service - Enhancing Customer Experience Through Integration and Automation of Business Events in the Cloud

This year in Red Hat summit, I have to honor to work with two intelligent colleague of mine Eric Schabell and Siamak Sadeghianfar to share an interesting workshop. The main theme on the workshop is demonstrate how rules automation can be implemented on the cloud and how to take advantage of the integration service to expose API and scalable across the network.

Red Hat OpenShift, is a Platform-as-a-Service (PaaS) that allows developers to quickly develop, host, and scale applications in a cloud environment.  The lab goes through basics concept of OpenShift, explaining the following terminology in OpenShift.

Container: Lightweight mechanisms for isolating running processes
Image: A binary that includes all of the requirements for running a single container, as well as metadata describing its needs and capabilities.
Pod: A small group of tightly coupled Containers sharing network, storage, etc
Service: A set of replicated pods that work together
Build: Process of transforming a set of parameters and source code into a runnable image
Route: A route is a way to expose a service by giving it an externally-reachable hostname like
Template: Describes a set of objects that can be parameterized and processed to produce a list of objects for creation by OpenShift

As always, I want to focus more on the software development side, lets take a look at what is going on in the lab. The background of the scenario is a weight watcher program, which allows users to register with their weight loss target. Once registered, it will base on daily input from devices sent in to the system to provide calculated statistic of how this person is doing. 

Red Hat  JBoss BRMS, using the declarative logic with business rules to build applications with independent modularized rulesets. In our lab, we will deploy the business rule to a separate decision server. Here we use it store all the calculation logic of how your weight has progressed and to diagnose how the person is doing. A decision server will be deployed on the cloud and a project of set of rules will be applied to the server. Once the rules are loaded the server become our rule engine and ready to take in user data via web service. 

Having all the rules set up and start watching the weight providing advices is good. But we are now in the era of APIs, we want to maximize the use of the rules, creating a simple RESTFul API, it offers benefits such as additional decoupling, and allows extreme scalability. Since REST forbids conversational state, we can scale very wide by utilizing load balancer later on provided automatically by OpenShift. Other advantage such as uniform interface with Basic API operations makes other parties easy to follow. Red Hat JBoss Fuse is the perfect medium to turn the Business Rules into simple services API, it’s built-in interface. As it's REST DSL allows user to expose web API in simple context as well as have 150+ variety supported component to connect other service available. 

This example expose two RESTFul Endpoints, one takes in participants data and one receives constant updates of weight and returns the analyzed result back. There are few things we need to do 
  • Create an event base system by exposing RESTFul Endpoint using REST DSL with Camel 
  • Transform the entered data into JSON format required by BRMS, and then wrap these data in XML which is needed by decision server. 
  • Connecting to BRMS decision server with API Call 
  • Filter and parse the return result 
I have created demo that will automatically setup both BRMS and Fuse on OpenShift,

The install and running instruction are as follows, 


Make sure you have installed Vagrant and Virtual box. run to setup CDK and web services (SKIP this section if you have already installed)
$ ./
Install the project on OpenShift by running
$ ./
Login to OpenShift console with USERNAME/PWD admin/admin                                    
Overview BrokerOverview TCP BrokerOverview FUSE BRMS
Also Pods, services and route
Overview BrokerOverview TCP BrokerOverview FUSE BRMS

Running the demo

Registering a new Participants: Before we start sending in weight, we need to register the participants and set their goal.
Add Participant
Events - Updating weight: In a browser or any REST client app, trigger the event by updating the weight as we measure every-time. Each event will then pass into rule engine through our API. You should be able to see the calculated response from weight watcher.
Update weightCamel status


George Varghese said…
Can BRMS rules be applied on persisted data which is received at different points of time. The rule can run over the entire set of data that has been received for a patient over a period of time and that data set will only increase during the course of patient stay.

About the the rule itself, some of the clinical decision support rule needs to run every 5 minutes, some 15 minutes etc.

Monitoring Sepsis condition is a big requirement in USA, also have other scenarios where this will be very useful.

Varsha aravind said…

What an awesome post, I just read it from start to end. Learned something new after a long time.

Car Cleaning Services in Mumbai

back to original car services
Cinderella K said…
This is a gorgeous place. The reception area and the waiting room of meeting space San Francisco will make you feel special. There is luxury vibes that will welcome you. Aside from this, the conference room contains many technology and catering options.
Shalini said…
I just see the post i am so happy to the communication science post of information's.So I have really enjoyed and reading your blogs for these posts.Any way I’ll be replay for your great thinks and I hope you post again soon.

digital marketing company in india

Popular posts from this blog

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.



JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。


Connection Pool 最少會存留的connection 數量


Connection Pool 最多可以開啓的 connection 數量


事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.

And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.

2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.

So, now we know …