Skip to main content

Fuse Integration Service - Auto Dealership Management Demo, Part Two

This series of blog is based on building an auto dealership management system on Fuse Integration Service. We will be creating three major functions in the system.
  • Sales report tracking 
  • Vehicle inventory status
  • Customer IoT Service
We will be exporting a sales report to a web page, provide current inventory status of available cars through web service. And collect customer data from IoT devices on their car then alert close by shops. It would be better if you have some basic knowledge of Apache Camel before you begin, because I will not explain it in a great detail, I'll put my focus on how it works with the base platform, OpenShift. For Camel basic, you can check out my previous JBoss Fuse workshop. 

Alright, let's see what we are doing on part two, this is the second microservices of our case, and this service is the simplest out of all of them. It simple returns the current inventory status of the cars which is generated and stored in the application. Then it publishes this service via a web restful endpoint and return the result back in json format. 
And we are going to create 2 web services out of this, first one that returns the inventory status base on vehicle id and second one will be taking vehicle sales price range as the parameter, and return the inventory status of vehicles within price range.

So, first step is to create java bean that generate the mock result of inventory. And then map it in Camel. 

Java Bean

package com.redhat.fis.dms.mockprocessor;

import java.util.ArrayList;
import java.util.List;

import com.redhat.fis.dms.model.Vehicle;

public class VehicleGenerator {

private List<Vehicle> carpool;

public VehicleGenerator(){

public List<Vehicle> avaliablePriceRangeVehicle(Integer min, Integer max){
List<Vehicle> avaliableVehicles = new ArrayList<Vehicle>(); for( Vehicle car:carpool){
if(car.getPrice()>=min && car.getPrice()<=max)
return avaliableVehicles;

public Vehicle getVehicle(String vehicleId){
for( Vehicle car:carpool){
return car;
return null;

private void generateCarpool(){
carpool = new ArrayList<Vehicle>();


In Camel context xml, register the bean, 

<bean id="vehicleGenerator" class="com.redhat.fis.dms.mockprocessor.VehicleGenerator"/>

Complete code can be found here

Route returns the inventory status with vehicle id:

<route id="getVehicle">
 <from uri="direct:getVehicle"/>
 <bean ref="vehicleGenerator" method="getVehicle(${headers.vehicleid})"/>
  <json prettyPrint="true" library="Jackson"/>
 <log message="${body}"/>

Route returns the inventory status of price range:

<route id="availableVehicle">
 <from uri="direct:availableVehicle"/>
 <bean ref="vehicleGenerator" method="avaliablePriceRangeVehicle(${headers.minprice},${headers.maxprice})"/>
  <json prettyPrint="true" library="Jackson"/>
 <log message="${body}"/>

Web Service 
This will expose a webservice with port 9191.
<restConfiguration component="jetty" port="9191"/>
<rest path="/AutoDMS">
 <get uri="/availableVehicle/pricerange/{minprice}/{maxprice}">
  <to uri="direct:availableVehicle"/>
 <get uri="/getVehicle/{vehicleid}">
  <to uri="direct:getVehicle"/>

To expose the port on Docker, we need to set it up in the pom.xml, in the docker-maven-plugin, add 

That's all. We can then publish and deploy this service on to OpenShift platform, if you would like to know more detail about this, please check on part one of the series. In command line, under the project folder, login to OpenShift with it's client tool. Make sure you create a project called demo and deploy the mq-basic application on it, if you have not previously done so. This will save us from the need to set Kubernetes settings. Then simply type in console.
  • mvn -Pf8-local-deploy
And you will see the application deployed on OpenShift.

If you want to test it, here is where you can test the two webservices, 



In the application console, we can monitor how the routes are doing, 

To make things more interesting, say if the demand for this service has grow, we want to have more resource to support the load, all we have to do is to scale up is simply add more pod in the replication controller. 

And it will automatically add resource and balance the load to each pod. So how do we make sure every time when we redeploy it will create the number of pod we added? Simple, add the setting in the configuration in pom.xml. 

  • <fabric8.replicas>2</fabric8.replicas>

That's all for part two!


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 。

My 2cents on the future of Integration - With Service Mesh/Istio and Serverless/KNative

It's been a year and half since I blogged about "Agile Integration architecture" (Gosh, time just flies). With the "microservices" and "cloud-native" hype, I was especially curious on how all these new concept and technology affect us on how to architect the integration systems. If you ever pay close attention to all the latest and greatest news from the Kubernetes community, I am sure you will hear a lot about the new "Service Mesh". And rumor has it that this is how integration can/should be done in cloud native world, but, is that so? Anyone who has ever worked on an integration project would tell you, it's a LOT more COMPLEX and can get worst overtime. I did a talk with Christian Posta in Red Hat Tech Exchange coming from a more comprehensive view of how different Red Hat technologies are applied under different patterns when building integration solutions. In fact he also did a great blog about it.

Since then, another topics has be…

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…