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(){
generateCarpool();
}

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)
avaliableVehicles.add(car);
}
return avaliableVehicles;
}

public Vehicle getVehicle(String vehicleId){
for( Vehicle car:carpool){
if(car.getVehicleId().equalsIgnoreCase(vehicleId))
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})"/>
 <marshal>
  <json prettyPrint="true" library="Jackson"/>
 </marshal>
 <log message="${body}"/>
</route>

Route returns the inventory status of price range:




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

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>
 <get uri="/getVehicle/{vehicleid}">
  <to uri="direct:getVehicle"/>
 </get>
</rest>

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, 

  • http://inventoryservice-demo.cdk.10.1.2.2.xip.io/AutoDMS/availableVehicle/pricerange/20000/40000

  • http://inventoryservice-demo.cdk.10.1.2.2.xip.io/AutoDMS/getVehicle/vno03

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!




Comments

Popular posts from this blog

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

jboss-devstudio-9.0.0.GA-installer-eap.jar
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 …

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 …

RHTE - Supercharge your integration services

Red Hat Tech Exchange has taken place in Vietnam, Ho Chi Minh city two weeks ago, it is a great event held by Red Hat in Asia Pacific Region. It is open to all Red Hat partners who are interested in learning what Red Hat is doing recently, see what the trend of the open source world, basically it is a great event to share your knowledge and experience, to meet other enthusiastic people.

I am very fortunate to talk in this great event, to talk about the things I have been working on and even discuss it with many. Also got lots of great ideas too. So here are the slide.

My first talk was with Thomas Qvarnström about how to handle large size data in JBoss Fuse and how JBoss Data Grid can help in the situation.

Here is the agenda of the talk, we will be talk about this in the up coming webinar on 24th Sept.

Integration often involves storing, retrieving, and transforming data. Using a traditional database in your integration is likely to becomes a bottleneck that is expensive and hard to …