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. 

<fabric8.service.name>dealeralert</fabric8.service.name>
<fabric8.service.port>80</fabric8.service.port>
<fabric8.service.containerPort>${http.port}</fabric8.service.containerPort>
    
<env>
 <JAVA_LIB_DIR>/deployments/lib</JAVA_LIB_DIR>
 <JAVA_MAIN_CLASS>org.apache.camel.spring.Main</JAVA_MAIN_CLASS>
 <HTTP_PORT>${http.port}</HTTP_PORT>
 <A_MQ_SERVICE_NAME>${fabric8.env.A_MQ_SERVICE_NAME}</A_MQ_SERVICE_NAME>
</env>
<ports>
 <port>${http.port}</port>
</ports>

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;
   else
    return 0;
  }else{
    return 0;
  }
 }
}

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

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! 



Comments

Popular posts from this blog

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…

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.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

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

prefill

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

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

Fuse - Contract First API Design with Apicurio and Fuse/Camel - Part One

This is part one of my two-article series that demonstrates the approach of implementing contract-first API design using Apicurioand Red Hat Fuse.

It covers how to create an OpenAPI standard document as the contract between API providers and consumers using Apicurio. It also shows how to quickly create mock tests using Red Hat Fuse.

There are two common approaches of creating these APIs.
Code FirstContract First Coming from a old time ESB developer, these are not new. We have been doing this forever. Before, it was the WSDL that define the contract of the service. we were doing a lot more code first, for me it's simply because it's much easier for me to write couple of Java classes and generate the WSDL for my consumer. 

It's often pretty straightforward if the consumer of your application has finalized how they want the service to be like. But you and I all know this is not often the case. So I had to go back to my code, and make the changes accordingly and pray I did not …