Comments on: MQTT (definitely) coming to MQ

By: knolleary

knolleary — Thu, 15 Mar 2012 17:57:39 +0000

Hi sandman. It was first added in MQ 7.0.1, and has since been fully integrated in last year’s MQ 7.1 release.

By: sandman

sandman — Thu, 15 Mar 2012 17:19:59 +0000

Which version or fixpack incorporated MQTT into MQ ? Is it from MQ 7.0.1.X or MQ 7.0 ?

THanks.

By: Andy Piper

Andy Piper — Wed, 06 Oct 2010 15:34:27 +0000

If you are connecting to MQ – which I thought was Tim’s original question – then there is some information in the MQ Infocenter on how e.g. SSL could be used on the telemetry channel:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.amqtat.doc/tt60318_.htm

As mentioned above though, the provision of this link is generally left to individual implementations, so not all MQTT servers will necessarily support something like this.

By: admin

admin — Tue, 21 Sep 2010 14:45:44 +0000

Hi TimB,

you’ve got the right link there. The protocol does not make any statements about encryption.

There are two areas where encryption could be applied: message-level and network-level.

One of the advantages of MQTT is its light-weight nature; the payloads are just byte arrays. Message-level security can be achieved by the application encrypting the payload before providing to the client API for publishing.

At the network layer, the protocol requires a TCP link, which could be an SSL-secured link. The provision of the link is left to individual implementations – as is done by MQ Telemetry and its clients (but not the daemon for devices).

Hope that helps.

By: TimB

TimB — Tue, 21 Sep 2010 13:44:42 +0000

Is this the documentation (MQTT v3.1 spec from the Aug 20th announcement) you’re on about? because I don’t see encryption mentioned in it.

http://public.dhe.ibm.com/software/dw/webservices/ws-mqtt/mqtt-v3r1.html

can you post a link please?

TIA

By: Andy Piper

Andy Piper — Tue, 17 Aug 2010 15:16:43 +0000

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.

By: TimB

TimB — Sat, 14 Aug 2010 18:18:24 +0000

cheers for the clarification there…

does this ‘daemon’ support encryption for the connection to MQ?

By: Andy Piper

Andy Piper — Wed, 11 Aug 2010 10:47:23 +0000

I've posted a little more about this over on my blog under MQTT The Smarter Planet protocol

By: admin

admin — Thu, 05 Aug 2010 08:51:31 +0000

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.

By: TimB

TimB — Thu, 05 Aug 2010 07:58:43 +0000

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?