Skip to main content


Showing posts from September, 2014

JBoss Fuse - How to setup cluster of servers in Fabric

Staying in Beijing for a technical enablement, one question I have been ask a lot is how to setup a Fabric in a cluster of servers with JBoss Fuse? I am going to setup 2 Fuse on 2 different servers, and then join them together to form a fabric cluster. BUT!!!! In the real world please make it at least 3 servers, as zookeeper needs more then 3 to successfully setup it's ensembles!  First we need to create a fabric, so unzip the JBoss Fuse zip file in Server1, setup password by editing etc/ And please do the same thing to server2. If you are testing, and tries to setup on the same machine, please remember to go to "" under etc/ and change the RMI related port. also there are a few more port you need to adjust,, change the sshPort and last inside org.osgi.service.http.port activemq.port activemq.jmx.url Now, getting back to setting the cluster of fa

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