Skip to main content

Fuse Integration Service - Auto Dealership Management Demo, Part Four

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. 

OK, this is our last project, from previous part we have talked about setup a restful endpoint to receive GPS signal. Here we are going to process the incoming data and alert dealer shops when a car is closing by. In this demo, we will two endpoint, messaging broker and websocket. We want to make sure this GPS detection and alert mechanism is asynchronized, minimizing stalled connection between client and server. Websocket as the protocol in between our alert web console and application, because  it allows a long single TCP socket connection establish between client console and server. Also, it has very little overhead, resulting in a very low latency connection. 

For MQ broker setup, please take a look at part three of the series. As for websocket, it is even easier, no setup needed, all we have to do is to specify which port we are going to expose in the component parameter 
  • websocket://demo?port=9292&sendToAll=true

And don't forget to expose the port in both docker and as a service. 


Java Bean:
This java bean simply determine how close the GPS location is to our shop. 

package com.redhat.fis.dms.mockprocessor;

public class GeoLocationCheck {
 public Integer isCloseToStore(String location){
  if(location!=null && !location.trim().isEmpty()){
   if(location.startsWith("3") || location.startsWith("7"))
    return 1;
   else if (location.endsWith("0") || location.endsWith("8") ||  location.endsWith("5"))
    return 2;
    return 0;
    return 0;

Receive GPS location from broker, passing it to java bean to determine if it is close to shop, 
  <from uri="amq:queue:TESTQUEUE"/>
    <json library="Jackson"/>
  <log message="Is the car closed to one of our store with geolocation: ${body.[geoloc]}"/>
  <setHeader headerName="custName">
  <bean ref="geoLocationCheck" method="isCloseToStore(${body.[geoloc]})"/>
      <simple>${body} == 2</simple>
        <simple>{"msgType":"2","custName":"${headers.custName}","warningMsg":"is nearby our store!"}</simple>
      <simple>${body} == 1</simple>
        <simple>{"msgType":"1","custName":"${headers.custName}","warningMsg":"in the neighborhood"}</simple>
        <simple>{"msgType":"0","custName":"${headers.custName}","warningMsg":"not even close"}</simple>
  <log message="${body}"/>
  <to uri="websocket://demo?port=9292&amp;sendToAll=true"/>

We are ready to 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.

I especially love this view,  because it shows the complete microservices available in my Auto Dealership Management application, also the endpoint it exposes. 

So, time to test it out! I did a small javascript application with two pages, first page mimicking cars giving out GPS signals, generate a random location every 5 seconds, and call the Restful API we did in part one. Second page is the alert console, by using websocket protocol, it connects to our alert system, and gives alert with yellow being a car is near the shop and red for even closer. 

And if you go to the application console on Openshift, here is what you will see.  
the metrics of how each route is doing, 

More consolidated view, 

Messaging Queue:

More Camel route.

That's all for part four! 


Popular posts from this blog

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 …

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 …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.

And select JBoss Fuse Development for the plugin,

Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …