MQTT (definitely) coming to MQ
July 8th, 2010 - adminIBM has formally announced its plans for bringing MQTT support to MQ. Unlike the preview announcement made previously, this includes the concrete details on what is being done, including the planned availability date – August 27th, 2010.
Known as MQ Telemetry, this will allow applications to use the MQTT v3 protocol to communicate with their MQ queue manager. A pair of client libraries are provided for applications to use, in both c and java.
An advanced client is also provided – the MQ Telemetry daemon for devices. This is based on RSMB that was previously only available via IBM alphaWorks on an evaluation license.
A key part of this will be a much clearer statement on the use of the MQTT protocol itself – something the community has needed for some time.
The formal announcement is here and the MQ product pages have been updated here.
how is the “the MQ Telemetry daemon for devices” an advanced ‘client’, shirley it’s a message broker connecting to MQ as a bridge? you’d still need a client of some sorts to connect to it?
Tim, it is called a ‘client’ because it will be run on the client devices connecting back to the central MQ. Often these devices will be constrained in terms of memory or processor and be running on the end of a costly/thin/fragile network. These characteristics make it impractical to run a full MQ queue manager.
A possible scenario is where you have an device, such as a smart meter, running a number of different services on board. Each service needs to communicate with each other and with the enterprise. Rather than have each one establish a network connection back to MQ which would be costly, you would run the daemon devices locally acting as a concentrator. Each of the services would then use the C or Java client libraries (or any other client library that implements the MQTTv3 protocol) to communicate with the daemon.
Hope that answers your question.
I’ve posted a little more about this over on my blog under MQTT The Smarter Planet protocol
cheers for the clarification there…
does this ‘daemon’ support encryption for the connection to MQ?
Tim, there are several security options, one of which is SSL for the connection, and another of which is a JAAS authentication module (the latter of which would not give “encryption”, of course). You can also combine the two. This is all described in the documentation which will go live around release time.