Skip to main content

JBoss Fuse - Parsing CSV file playing with Websocket in Camel Part two

Continue on from the last post, as in a vegetable wholesalers warehouse, when ever a truck comes in with loads of goods, when the driver signs the goods over, a cvs file contains the product information will be feed into our system via wireless transmission. And then the content of the file needs to go to 2 places simultaneously, first display the content on the monitor for the bider to see instantly, also it needs to store the content inside the system. 

We used the Bindy data format converter component in camel to convert CSV into POJO from the previous post.So now to display the content, we are going to continuously print out the arrived goods data to all the connected devices, such as the big monitor in the warehouse or distributor's hand-held device. For this we are going to publish the content to all client(html5 web page) that are connect to our websocket, and store the content into a constant POJO at the same time. 




The WebSocket endpoint is pretty simple and straight forward, I bit you will never go back to EE once you see how much easier with Camel. 
     

Here you see I have setup a websocket ws://localhost:9292/echo and try to send to all clients.  Did you see how simple that was? You have a option of sending the message to a single client or all, these 2 parameters can be set either in the header or in the parameter.
Key
Description
WebsocketConstants.SEND_TO_ALL
Sends the message to all clients which are currently connected. You can use the sendToAll option on the endpoint instead of using this header.
WebsocketConstants.CONNECTION_KEY
Sends the message to the client with the given connection key.


So make sure you set the right one, and I am not going into the details of a HTML client, I simply grab the available example online, all you need to do is change where your WebSocket destination. The script simply just connects to the WebSocket and start listening to the port and display the content when ever it receives messages from server. 
      var wsUri = "ws://localhost:9292/demo"; 

function onOpen(evt) { 
writeToScreen("CONNECTED");
 } 

function onMessage(evt) { 
  writeToScreen('' + evt.data+'');
} 

window.addEventListener("load", init, false);

By using the Wire Tap enterprise integration pattern in Camel, it "allows you to route messages to a separate location while they are being forwarded to the ultimate destination". We can then send the data both to the websocket endpoint and the data store simultaneously. 


On the other side of the wire tap, we redirect it to another route, which then starts up a  Java bean, sums up the quantity of goods and log for demo purpose. 

The Java process bean is very simple. 

package org.blogdemo.websocketbindydemo;

import java.util.HashMap;

public class ProductProcessBean {
 
 private HashMap productSum = new HashMap();
 
 public String addProduct(Product product){
  Integer sum=0;
  if(productSum.get(product.getProductId()) != null){
   sum = productSum.get(product.getProductId())+product.getQuantity();
  }else{
   sum = product.getQuantity();
  }
  
  productSum.put(product.getProductId(), sum);
  
  return "Added Product "+product.getProductName()+", now the total shipped quantities are :"+sum;
 }

}


Deploy the application using fabric8's maven plugin.


fabric8:deploy


Now, we are ready to deploy content into the application. 

1. Start up and setup Fuse, create Fuse Fabric



2. Create a container and add the profile



3. Go to the container view, sending CSV file to the endpoint.


You can find the result published to the web page.


And log




Here is the step by step video. 



You can find the code inside JBoss Demo Central.
https://github.com/jbossdemocentral/jboss-fuse-component-websocket


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 …