IBM WebSphere MQ Telemetry
MQTT support was previously available with either WebSphere Message Broker or WebSphere MQ Version 7.0.1, where WebSphere MQ Telemetry was a separate feature. Because WebSphere MQ Telemetry is a component of WebSphere MQ Version 7.1 and later, upgrading is essentially uninstalling WebSphere MQ Telemetry version 7.0.1 and installing WebSphere MQ Version 7.1. WebSphere MQ Telemetry can either be installed with the main product, or installed after version 7.1 or later is already installed. For migration information, see Migrating IBM WebSphere MQ Telemetry from Version 7.0.1 to Version 7.5 or Migration of telemetry applications from using WebSphere Message Broker version 6 to use IBM WebSphere MQ Telemetry and WebSphere Message Broker version 7.0.
- Telemetry channels
- Use telemetry channels to manage the connection of MQTT clients
to IBM WebSphere MQ. Telemetry channels use
new IBM WebSphere MQ objects, such as the
SYSTEM.MQTT.TRANSMIT.QUEUE, to interact with IBM WebSphere MQ. - Telemetry (MQXR) service
- MQTT clients use the
SYSTEM.MQXR.SERVICEtelemetry service to connect to telemetry channels. - IBM WebSphere MQ Explorer support for IBM WebSphere MQ Telemetry
- IBM WebSphere MQ Telemetry can be administered using IBM WebSphere MQ Explorer.
- Client Software Development Kit (SDK)
- The client SDK has four parts:
- MQTT v3 client libraries for Java SE and Java ME. Use the Java libraries to write Java clients for devices that support Java SE or Java ME.
- MQTT v3 libraries for C. Use the C libraries to write C clients for a number of platforms.
- IBM WebSphere MQ Telemetry daemon for devices, which is an advanced client written in C that runs on a number of platforms.
- MQTT v3 protocol. The MQTT v3 protocol is published and licensed for reuse. Use the protocol, and reference MQTT client implementations, to write MQTT clients for different platforms and languages.
- Documentation
- IBM WebSphere MQ Telemetry documentation is included in the standard IBM WebSphere MQ product documentation from Version 7.1. SDK documentation for Java and C clients is provided in the product documentation, and as Javadoc and HTML.
Telemetry concepts
You collect information from the environment all around you to decide what to do. As a consumer, you check what you have in store, before deciding about what food to buy. You want to know how long a journey is going to take if you leave now, before booking a connection. You check your symptoms, before deciding whether to visit the doctor. You check when a bus is going to arrive, before deciding whether to wait. The information for those decisions comes directly from meters and devices, from the written word on paper or from a screen, and from you. Where ever you are, and when ever you need to, you collect information, bring it together, analyze it, and act upon it.
If the sources of information are widely dispersed or inaccessible, it becomes difficult and costly to collect the most accurate information. If there are many changes you want to make, or it is difficult to make the changes, then the changes do not get made, or are made when they are less effective.
What if the costs of collecting information from, and controlling, widely dispersed devices is greatly reduced by connecting the devices with digital technology to the internet? The information can be analyzed using the resources of the internet and the enterprise. You have more opportunities to make informed decisions and act upon them.
- The cost of connecting and controlling sensors and actuators is reducing, due to standardization and connection to low cost digital processors.
- The internet, and internet technologies, are increasingly used to connect devices. In some countries, mobile phones exceed personal computers in the number of connections to internet applications. Other devices are surely following.
- The internet, and internet technologies, make it much easier for an application to get data. Easy access to data is driving the use of data analytics to turn data from sensors into information that is useful in many more solutions.
- Intelligent use of resources is often a quicker and cheaper way of reducing carbon emissions and costs. The alternatives: finding new resources, or developing new technologies to use existing resources, might be the long-term solution. In the short term developing new technologies, or finding new resources, is often riskier, slower, and more costly, than improving existing solutions.
Example
An example shows how these trends create new opportunities to interact with the environment intelligently.
The International Convention for the Safety of Life at Sea (SOLAS) requires Automatic Identification System (AIS) to be deployed on many ships. It is required on merchant ships over 300 tons and passenger ships. AIS is primarily a collision avoidance system for coastal shipping. It is used by marine authorities to monitor and control coastal waters.
Enthusiasts around the world are deploying low-cost AIS tracking stations and placing coastal shipping information onto the internet. Other enthusiasts are writing applications that combine information from AIS with other information from the internet. The results are put on Web sites, and published using Twitter and SMS.
In one application, information from AIS stations near Southampton is combined with ship ownership and geographical information. The application feeds live information about ferry arrivals and departures to Twitter. Regular commuters using the ferries between Southampton and the Isle of Wight subscribe to the news feed using Twitter or SMS. If the feed shows their ferry is running late, commuters can delay their departure and catch the ferry when it docks later than its scheduled arrival time.
For more examples, see Telemetry concepts and scenarios for monitoring and control.