Skip to main content

JBoss Fuse on xPaaS - IoT Mash-up Demo

There are 3 common protocols when it comes to messaging on Internet of Things,

MQTT - is OASIS standard, adopted by various vendor and companies, it is an extremely light weight transport, and is excellent for low computing power device, and platforms. And it only supports publish and subscribe mechanism. 

STOMP - is simple and lightweight (not as light as MQTT), it supports transport over websockets, and it is basically sending text through wires, very much like telnet.

AMQP - is a vendor neutral protocol over the wire, it supports rich sets of communication patterns, and it is accessible through a wide variety of APIs, such as JMS, JCA, WCF, Qpid, etc

All these are very easy to implement using Apache Camel. So I came up with a demo, showcasing these 3 common protocols. 

The basic architecture of demo is basically like this: 


Where I have created different connectors, like MQTT, AMQP, STOMP, WebSocket and Openwire for a broker on top of OpenShift, or it's similar if you want to create this on a Local JBoss Fuse. 
To do that, go to the boker.xml setting (depending on your environment, if you create a new broker profile on Fuse, make sure you make a copy of broker.xml from mq.base profile to your broker profile.), add transportConnector with different protocol name and port. 

<transportConnector name="amqp" publishedAddressPolicy="#addressPolicy" uri="amqp://${OPENSHIFT_FUSE_IP}:5672"/>       

<transportConnector name="mqtt" publishedAddressPolicy="#addressPolicy" uri="mqtt://${OPENSHIFT_FUSE_IP}:1883"/>      

<transportConnector name="stomp" publishedAddressPolicy="#addressPolicy" uri="stomp://${OPENSHIFT_FUSE_IP}:31613"/>      

<transportConnector name="websocket" publishedAddressPolicy="#addressPolicy" uri="ws://${OPENSHIFT_FUSE_IP}:31614"/>

Then install 3 Camel Routes, all of them are using built-in Components in JBoss Fuse to poll in the message from broker. With the built-in component, it will save lots of code implementation time.

AMQP Component: 
       amqp:queue:myAMQPDemo

MQTT Component: 
       mqtt:bar?subscribeTopicName

STOMP Component: 

        stomp:topic:chat.general

As you can see from the camel route, after we retrieve messages, we will process it and put them all into a big queue, which will be picked up later by web application and displayed. 

Because we are using openshift as our broker, we need to export the internal port by using the port-forward command provided by the openshift client tool.

rhc port-forward containerName

And lastly, we are going to startup a local web application, so we can have a nice web interface let you play with different protocol and display the result in a web console. And within the web application, we also use Qpid API and MQTT API to send messages into the queue or topics. 

You can find the demo code here:
https://github.com/weimeilin79/iot-mashup

Here is the video demo: 



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 …