These pages are intended to record the work that is going on within JBoss in the area of Internet of Things (IoT). At present we have no single IoT related project because it encompasses many different technologies, such as messaging and development frameworks. As such, much work on IoT is occuring within projects where that effort is more relevant, e.g., ActiveMQ/HornetQ for MQTT. You should feel free to engage these projects and their communities directly if you have an interest, questions etc. However, we also have specific forums for IoT which are available here for discussions that are not obviously relevant in one of our other projects. If you are at all unsure, use this forum for things related to using projects within IoT environments, and this forum for discussing developing/modifying projects within IoT environments; we'll work to answer questions or re-direct where appropriate.
At some point we will add some text that describes the IoT. For now we will assume that the reader understands basic concepts of IoT and further details can be obtained from the page maintained by Scott Stark.
However, one of the biggest differences between the current definition (use cases) of IoT and ours is that we tend to be more encompassing of the historical Ubiquitous Computing roots behind IoT: for instance, we do not assume that all devices, such as sensors, are constrained devices with limited memory or processing power. With the advent of machines such as the $30 Raspberry Pi, it is obvious that relatively powerful devices can be made available to the masses. Furthermore, it is often cheaper to use mass produced CoTS hardware within devices (e.g., unused Pentium 4s, or i5/i7 processors) than setting up a bespoke fabrication facility. Therefore, as well as looking at being able to integrate constrained devices (e.g., MBed boards) with JBoss projects and products, we are also looking at how these projects and products may run on a range of devices.
In fact many of our IoT efforts have their roots in the JBossEverywhere iniative we announced several years ago. To paraphrase ...
"Just as the new wave of personal computers were thought of as constrained 30 years ago and often looked on with distain by those in the workstation and mainframe arenas, yet now they power a lot of enterprise computing, so too will go many of the devices we see around us today as being of limited utility. Your mobile phone already has capabilities that would put to shame PCs of the 1990's. They have also quickly become critical to our day to day lives, moving from supporting basic games to complex B2B applications. These applications need enterprise capabilities, such as messaging and transactions. But it's not just mobile phones. Due to the economics of scale, it's not far fetched to assume that sooner than you think your washing machine, car or even coffee pot, will have more raw processing power than workstations or laptops of years gone by. Being able to tap into these processors is something that will happen, security considerations not withstanding. So JBossEverywhere is about defining middleware components and frameworks that can be used on these various devices. We should not expect people to reinvent the wheel, e.g., transactions, when there's a perfectly good wheel already out there. It'll mean developing new projects and pushing the envelope, but that's what we're good at. New frameworks that will combine adaptability, configurability, monitoring etc. to allow them dynamically cope with changing deployment environments so that the application doesn't have to (in many cases.)"
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.
This demo will be divided into 2 parts, first part is about setting up the Messaging broker on OpenShift with MQTT Connector. Second part we are going to write a simple demo trying to connect to the broker via MQTT.
This demo will be divided into 2 parts, first is to setup the Messaging broker on OpenShift with MQTT Connector. Then we are going to write a simple demo trying to connect to the broker via MQTT. Openshift is the open and unified Platform-as-a-Service (PaaS) offering for enterprises from Red Hat. So developers like me don't have to go through all the hassle about setting up the environments or managing the networks.
"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."
How to be a JBoss A-MQ and Android Rock Star in the world of the Internet of Things! I wanted to pull together a simple example of how to leverage Red Hat JBoss A-MQ in the Internet of Things (IoT) through the use of Message Queue Telemetry Transport (MQTT) in Android.
This free guide includes: In-depth articles written by industry experts, key findings from our survey of over 2000 developers, profiles on 39 Internet of Things Vendor Solutions, "How to IoT Your Life: The Complete Shopping List", "IoT Developer Mindshare" Infographic, and Glossary of common IoT terms.
Eclipse Kura is an OSGi based framework dedicated for the M2M gateways based on the small computing platforms like Raspberry Pi or BeagleBoard Black. If you consider using Kura in your M2M gateway and and the same time you would like to take advantage of the rich set of Apache Camel components and its EIP capabilities, then Camel Kura component is something for you. Camel Kura component will be available starting from the Camel 2.15.0.
The common scenario for the mobile IoT Gateways, for example those mounted on the trucks or the other vehicles, is to cache collected data locally on the device storage and synchronizing the data with the data center only when trusted WiFi access point is available near the gateway. Such trusted WiFi network could be localized near the truck fleet parking.
Eclipse Kura is the well recognized field gateway for Internet Of Things applications. Apache Camel is the message routing engine and the library containing a gazillions of the various endpoint connectors. Are you interested in finding out how these two can be joined together to create a rocking IoT solution? Then tune in to this talk!
Engineer at Red Hat. Open source hacker (Apache Camel, JBoss Fabric8, JBoss Hawt.io). Keen on the marriage of the Internet Of Things, messaging and the cloud.
As some of you already know, I've been pretty interested in the Internet Of Things topic. The IoT is actually a natural extension of my existing interests - M2M communication relies on the messaging and integration technologies heavily, so Camel, ActiveMQ and Fabric8 excel in this area.
The incoming version of the Apache Camel (2.16) will bring Paho component which provides connector for the MQTT messaging protocol using the Eclipse Paho library. Paho is one of the most popular MQTT libraries, so if you would like to integrate it with your Java project - Camel Paho connector is a way to go.
Raspberry Pi 2 comes armed with the 900 MHz quad-core ARM Cortex-A7 and 1 GB of memory. This is a pretty powerful hardware considering the hobbyist Internet Of Things applications, but it's still relatively slow comparing to the industrial-grade microcomputers. As soon as my very own Raspberry Pi 2 has been shipped to me, I started to wonder how fast this car key size computer can be.
One of the most popular requirements for the field devices used in IoT systems is to provide the current GPS location of that device and send this information to the data center. In this article I will tell you how Apache Camel can turn a full-stack Linux microcomputer (like Raspberry Pi) into a device collecting the GPS coordinates.
The key part of the process of tailoring the perfect IoT solution is choosing the proper hardware for the gateway device.
Starting from today we will be gradually migrating our Camel Labs to new Rhiot name. That will include moving our GitHub project to the new rhiot organization and changing our Maven coordinates from com.github.camellabs to io.rhiot.
Deploying message broker for an IoT use case introduces some new challenges to the broker scalability.
The 2015 DZone Guide to the Internet of Things offers insight to executive and developer perspectives of IoT trends and concerns, as well as a listing of platform and hardware solutions to facilitate IoT development, and a comprehensive checklist to help you secure your Internet of Things applications.
Internet of Things is going to be big. Billions of connected devices and trillions of dollars of the economic value-add in the 2020. The existing enterprises are going to start collecting the enormous volume of data from the myriad of the heterogeneous devices. Data collected by the enterprises will be used to transform these organizations to be more efficient.
Recently at the Eclipse IoT Working group mailing lists one of our members raised the proposal to collaborate on the server-side platform specification.
The goal of the Rhiot project is to allow the developers to create the Internet Of Things projects as easily as possible. We want to make the complex IoT projects simpler and bring the fun to the IoT world, while preserving all the benefits the developers can gain from the rich Red Hat JBoss Middleware portfolio.
The AMQP is becoming widely adopted as the protocol of choice the communication between an IoT gateway and a data center. If you would like to rapidly create the AMQP backend service that can be immediately ready for your gateways and devices, the Rhiot AMQP quickstart from the Rhiot project will be more than interesting for you.
The BU353 Camel component for Rhiot has been well received in our community. I'm pretty happy to announce then that we plan to deprecated BU353 component in order to promote new, better and awesome GPSD Camel component. GPSD component is available (and highly recommended to use) starting from Rhiot 0.1.2.
Henryk has just released the last version of Rhiot project : 0.1.2.
Some of us (for example myself) travel pretty much around various JVM/Tech/IoT events. I personally try to keep my twitter followers in the loop in the regards of my travel plans. And keep in mind that I always answer "yes" for coffee/beer/chat proposals :).
Apache Camel is flexible enough to be used with Eclipse Kura, an M2M framework, and provide messaging for your IoT devices.
Camel and Kura integrate wonderfully, and we've already explored Camel routes into Kura with Rhiot. Here's a breakdown of managing Camel routes with the Kura web UI.
The biggest changes coming in this release is support for Rhiot shell, official support for Eclipse Kura deployments and myriad of new Camel components dedicated for IoT.
How to use Apache Camel's new Apache Spark component for different architectural styles and use cases.
While in the Java world the OSGi technology has been commonly identified with the hot redeploy features, I would like to tell you more about the possibilities that Apache Camel running outside the OSGi environment can bring into this topic.
At present this page is broken down into a series of sub-pages, each covering a different topic.
We maintain a page point to anything related to the RaspberryPi, BeagleBoard etc. so go there for references to what is going on in other projects.
iPhone and other iOS related activities are captured separately.
Of course not everything related to IoT is Raspberry Pi/Android related and we have a range of projects and products that are running in a variety of embedded/non-traditional environments.
Finally JBoss has been involved with the standardisation and implementation of a number of IoT related protocols and we've recorded that information for you to read.
Oh and you can always read what James Kirkland has to say on all things IoT related.