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 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

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 - 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 …