Skip to main content

Red Hat JBoss A-MQ - A-MQ in Internet of Things, Sensor transmitting vital signal to Biomedical dashboard via AMQP



I was amazed by the increasing number of people mentioning "Internet of Things" in the recent conversations, if you already know what IoT is, please skip this part and go straight to my demo. :)

From Wiki,

"The term Internet of Things was proposed by Kevin Ashton in 1999,... it originally refers to uniquely identifiable objects and their virtual representations in an Internet-like structure. ...... Today however, the term Internet of Things is used to denote advanced connectivity of devices, systems and services that goes beyond the traditional machine-to-machine (M2M) and covers a variety of protocols, domains and applications."

From my understanding, is that more and more light weight, hand carry device or smart appliance are produce and manufactured. All these device works great on it's own, such as mobile phone,  TVs, GPS or even sphygmomanometers. But they work even better with the internet, by transmitting their live data, we were able to get better and quicker response and reaction. But the number of device out there is much greater then the current machines we are used to today. How do we cope with the vast amount of data floating in and make sure the data was delivered reliably?

The nature of messaging technology that allows information to deliver safely and reliably to the endpoint, has made it become the perfect medium to be the front line of IoT.

Under different circumstance, different ways and format to transmit information are used. So we can achieve better and more efficient performances.

STOMP (Streaming Text Oriented Messaging Protocol)
=========================================
Purely text base protocol. And since it's in text format, almost every broker supports it. But being the whole text format,I wouldn't count on it's performance.


MQTT (MQ Telemetry Transport)
=========================================
The most "light weight " Protoco out of all there. It is design for remote client with limited bandwidth to  deliver messages. MQTT has small code footprint. It's goal is simply deliver messages to the broker, the broker is then responsible to pass on the messages to other endpoints.

AMQP (Advanced Message Queuing Protocol)
=========================================
Open standard application layer protocol, It mandates the behavior of the messaging provider and client to the extent that implementations from different vendors are truly interoperable. WIth A-MQ, you can always use this protocol by using JMS API with Apache QPid Project.

This demo showcase how the sensor transmit Body vital sign by sending signals via AMQP to A-MQ queue. And the information is catch by the consumer in the Dashboard (again with AMQP) then display the data on the web dashboard.


https://github.com/weimeilin79/amqp-demo-web-biomedical

This video shows you how to install and run the demo:


Biomedical Dashboard demo from christina on Vimeo.

Comments

Irl Balcueva said…
This comment has been removed by the author.
Irl Balcueva said…
oday is the year of internet of things, this is the most commonly used today, everything from smartphone, cars, home. 2015 is a year of connected devices, home automation, connected cars. the big question for this right now is the security issues. Since cyber crime is always around the corner. Thank you for this very interesting info of yours. Hope you have time reading our blog.

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 …