5725-S17 IBM Watson IoT Platform - Message Gateway 5.0

IBM Asia Pacific Sales Manual
Revised: September 8, 2020


Table of contents
Product life cycle datesProduct life cycle datesDescriptionDescription
Program numberProgram numberOperating environmentOperating environment
AbstractAbstractPlanning informationPlanning information
HighlightsHighlightsPublicationsPublications


Product life cycle dates

Top rule

Program Number VRM Announced Available Marketing Withdrawn Service Discontinued
5725-S17 05.00.00 2018-12-11 2018-12-14 2022-09-16 2022-09-30
5725-S17 02.00.00 2016-05-10 2016-06-10 2021-09-17 2021-09-30
5725-S17 01.02.00 2014-10-21 2014-11-21 2019-07-12 2019-12-31


Back to topBack to top

Program number

Top rule

  • IBM Watson IoT Platform - Message Gateway 5.0 (5725-S17)


Back to topBack to top

Abstract

Top rule

IBM IoT MessageSight is renamed Watson IoT Platform. Message Gateway to be consistent with the rest of the Watson IoT Platform portfolio.

IBM IoT MessageSight offers the ability for businesses to simply, efficiently, and reliably connect their enterprise systems to devices and sensors. It enables fast and responsive, bidirectional mobile applications.

Both IoT and mobile environments present challenges to businesses for security, scalability, and manageability, particularly when working with large numbers of sensors and devices. IoT MessageSight acts as a gateway to provide these capabilities while processing large numbers of events in near real-time.

IoT MessageSight allows an enterprise to unlock information that is contained within systems of record and to take advantage of new opportunities, particularly in the fields of connected car, smart meters, online gaming, assisted living, connected home, banking notifications, track and trace, and chat.

IoT MessageSight works around a standard, lightweight, bidirectional protocol, known as MQTT.

Version 5.0 provides enhancements for the IoT. They include:

  • MQTT v5
  • Bridge capability
  • Session expiry
  • Message rate performance tuning
  • Improved monitoring
  • Administrative subscriptions
  • Performance enhancements

IBM IoT MessageSight 5.0 offers the ability to connect enterprise systems to the devices and sensors of the Internet of Things (IoT):

  • Simply, by using policy-based administration to manage large numbers of clients
  • Efficiently, by using lightweight standard MQTT, which is designed to connect to sensors
  • Securely, by using advanced security protocols (SSL/TLS, OAuth, and LDAP)
  • Reliably, with assured delivery, persistent messaging, and high availability

It enables you to take advantage of big data that comes from sensors and devices and couple this data with analytics to take informed, timely action.

Version 2.0 provides enhancements to support connectivity for the IoT. They include:

  • Scalability: cluster multiple instances
  • RESTful administration API
  • Deployment: Linux, Docker
  • Security: black list rogue client certificates
  • Performance enhancements
  • High availability enhancements
  • New licensing option for high-availability configurations
  • Plug in point to support additional protocols

MessageSight is renamed in Version 2.0 to IoT MessageSight.



Back to topBack to top

Highlights

Top rule

IBM IoT MessageSight 5.0 offers the ability to connect enterprise systems to the devices and sensors of the Internet of Things (IoT):

  • Simply, by using policy-based administration to manage large numbers of clients
  • Efficiently, by using lightweight standard MQTT, which is designed to connect to sensors
  • Securely, by using advanced security protocols (SSL/TLS, OAuth, and LDAP)
  • Reliably, with assured delivery, persistent messaging, and high availability

It enables you to take advantage of big data that comes from sensors and devices and couple this data with analytics to take informed, timely action.

IBM IoT MessageSight 2.0 offers the ability to connect enterprise systems to the devices and sensors of the Internet of Things (IoT).

  • Simply, by using policy-based administration to manage large numbers of clients
  • Efficiently, by using lightweight standard MQTT, which is designed to connect to sensors
  • Securely, by using advanced security protocols (SSL/TLS, OAuth 2.0, and LDAP)
  • Reliably, with assured delivery, persistent messaging, and high availability

It enables you to take advantage of big data that comes from sensors and devices in new scenarios and couple this data with analytics to take informed, timely action.



Back to topBack to top

Description

Top rule

IoT MessageSight 5.0 key product capabilities and highlights:

Asynchronous messaging that supports:

  • Both publish and subscribe (topic-based) and point-to-point (queue-based) messaging domains
  • Both persistent and nonpersistent qualities of service
  • MQTT versions 3.0, 3.1, and 5.0
  • MQTT over HTML5 WebSockets
  • Java Messaging Service (JMS) 1.1
  • Message expiry
  • Message discard
  • MQTT shared subscriptions
  • Clusters for scalability
  • A separately installable web UI
  • Restful administration API

Performance

  • Delivers high throughput for persistent and nonpersistent messages
  • Supports vast numbers of connected devices

Developer-friendly APIs and libraries

  • MQTT clients and libraries for a variety of platforms, which include C and Java-based APIs
  • Libraries for Google Android and Apple iOS
  • JMS client libraries
  • JavaScript API for HTML5-based applications

Reliability

  • Assured delivery of messages
  • Support for MQTT qualities of service (QoS) 0, 1, and 2 (best effort, at least once, and exactly once)
  • Local transaction support
  • Support for high-availablity configurations
  • SNMP monitoring
  • Support for log file rotation, purging, and offloading

Security

  • Authentication through local user store or external Lightweight Directory Access Protocol (LDAP) servers.
  • Secure Sockets Layer (SSL) and Transport Level Security (TLS) support (SSL v3 and TLS 1.0, 1.1, and 1.2).
  • Fine-grained messaging authorization policies, which restrict access that is based on combinations:
    • User of group
    • Client identifier
    • Protocol
    • Network interface
    • Listening address or port
    • Client IP address or range
    • Destination (topic and queue) name
    • Black list with client revocation lists
  • OAuth 2.0 support designed to securely delegate authorization to a remote server. OAuth authorization servers that can be used with MessageSight include the DataPower appliances that contain an OAuth authorization server feature.
  • Single sign-on support by using LTPA tokens within cookies in the HTTP header when connecting with WebSockets.

Integration

  • Extends and connects to IBM MQ infrastructures
  • Supports mapping MessageSight destinations to and from IBM MQ destinations
  • Supports connectivity to WebSphere Message Broker via JMS or MQTT nodes or both
  • Integrates with Java environments
  • Integrates with rich HTML5-based web applications
  • Allows development of interactive mobile messaging applications
  • Is extendable with a protocol plug-in feature

Simplified deployment

  • Allows complete configuration and operation within 30 minutes
  • Delivers easy-to-use, web-based command-line interfaces
  • Requires minimal configuration options
  • Is available to support nonproduction, idle standby, and production environments

Supported environments:

  • Supports Linux RPMs and can be installed on both Red Hat and CentOS Linux
  • Can be deployed as a Docker image, which improves portability and enables automation across your software delivery pipeline
  • Can be deployed within VMware ESXi on either a Red Hat or a CentOS base image
  • Can be deployed on public cloud infrastructure in IBM Cloud, Amazon, and Azure cloud environments

In addition, the product is provided free of charge for development use and is available for download at IBM MessageSight

MQTT v5

In a world of many protocols and standards, there is one protocol that has become the de-facto standard in Internet of Things: MQTT.

MQTT was originally developed as a collaboration between IBM and Eurotech. MQTT features of being lightweight on the wire, being bidirectional yet avoiding polling, and having a publishing and subscribing model have made it appealing for IoT use cases. The publish and subscribe model avoids hardcoding links between sensors and consuming applications, and makes for easy prototyping and adaption.

MQTT is now part of the Oasis standards body. Version 3.1.1 has been available since 2014. Since then the Oasis working group has been working on improving it and developing a new version of MQTT, version 5.

As new sensors, devices, and gateways are produced, more and more of them will start supporting MQTT 5. If you're looking at an IoT use case, then you'll want to ensure that the MQTT server you choose supports MQTT 5.

MQTT v5 improvements:

  • Error reporting - Better error reporting makes it easier for the client to understand why something didn't work, such as a refused connection or failed publish, saving time in development.
  • Topic alias - Topic alias saves bytes on the wire. It works by decreasing the size of MQTT data by encoding long topic names into a short integer encoding. In most clients this is seamless and fully hidden from the client application.
  • Message expiry - This allows a message to expire without being delivered based on an expiration time set in the message. It is particularly useful if a message you are sending is important to the device only if it's online. For example, when unlocking car doors, you could send a message and ensure that it takes effect only if it's delivered within 30 seconds.
  • Message properties including user properties - Users can add message properties to the message header, such as whether the content is text or binary, the content type, and application-defined user properties. This metadata can be changed without modifying the message content. This enables rapid routing in the back-end application without needing to parse the payload of the message. Another use for this is when the payload is encrypted and some information is included in the header outside the encrypted envelope to help with processing.
  • New session start and expiry support - This allows the client to control how long a session lasts by indicating whether to start a new session on connect, and how long after a disconnect to keep a session.
  • Subscription identifiers - A subscription can be tagged with an identifier that is returned along with the messages received by the subscription. This allows for routing of messages internally in the client application.
  • Capability discovery - This allows the client to discover the capabilities of the MQTT server. Many of these capabilities are handled by the client library but are made available to the client application. For instance, the server will send to the client the maximum packet size it will accept.
  • Request/response - Users can send a request and allow the far end to send a response back that is tied to the original request.

IoT MessageSight Bridge (MQTT Bridge)

  • The new bridge feature allows you to connect your MessageSight to another MQTT server.
  • The bridge allows you to take messages from a large number of topics and map them across your network, either to individual topics or consolidated with a smaller number of topics.
  • Messages can be filtered in the bridge based on topic or message properties.
  • This allows you to build a hierarchy of MessageSight instances. For example, you could have a MessageSight instance in each factory with details from all the plant machinery, then use the bridge to filter the data and send a subset to a MessageSight instance in the regional office. A filtered set could then be sent to another instance at headquarters.
  • Hybrid scenarios are supported using the bridge to send data to a public cloud IoT platform, such as the IBM Watson IoT Platform in IBM Cloud.
  • For scalability for high message rates, the bridge can be configured to use shared subscriptions to share the load across multiple connections.
  • The bridge feature is symmetric. Messages can be sent in both directions.
  • The bridge is deployed as a stand-alone component. This allows you to run multiple copies for scalability and reliability.

Apache Kafka bridge

  • In addition to MQTT, the bridge can also forward messages to Apache Kafka (version 0.11 and above), using SASL plain authentication (or no authentication), and using TLS 1.2 (or no TLS).
  • The bridge is compatible with IBM Event Streams (formally IBM Message Hub) which is based upon Apache Kafka.
  • The consolidation of messages from a large topic space or devices to a smaller number of topics is particularly important when mapping to Kafka.

Other enhancements:

Session expiry - This allows you to administratively set an expiry time for the session state for clients that have connected and have state information stored in the server. This prevents the system from filling up with clients that will never reconnect.

Message rate performance tuning - This allows you to administratively inform the system of the characteristics of a particular client. The system will then optimize resource usage to match the expected use. You can specify whether the expected message rate is low, medium, or high. Individual devices are likely to be low. Back-end applications are likely to be high.

Improved monitoring - This allows administrators to obtain a full detailed view of the system across all connecting clients.

Administrative subscriptions - In the case where a network outage occurs between a stateless client (cleansession=true for 3.x clients or sessionexpiry=0 for v5 clients), then typically any messages buffered on a subscription will be discarded by the server. Administrative subscriptions can be used to prevent the buffered messages from being discarded.

Performance enhancements - Significant performance enhancements are included for persistent messaging (QoS 1 and 2).

IoT MessageSight 2.0 key product capabilities and highlights:

  • Asynchronous messaging, that supports:
    • Both publish and subscribe (topic-based) and point-to-point (queue-based) messaging domains.
    • Both persistent and non persistent qualities of service.
    • MQTT 3.1 and industry standard 3.11 specification.
    • MQTT over HTML5 WebSockets.
    • Java Messaging Service (JMS) 1.1.
    • Message Expiry, which allows the administrator to set an upper time limit to prevent old messages from queuing in the MessageSight system, eventually causing newer messages to be rejected.
    • The message discard feature that gives you greater control for handling new messages when a subscription hits the maximum number of messages configured for that subscription. When the subscription is full, you can choose either to reject new messages or discard old messages.
    • MQTT Shared subscriptions
  • Performance
    • Delivers high throughput for persistent and non persistent messages.
    • Supports vast number of connected devices.
  • Developer-friendly APIs and libraries
    • MQTT clients and libraries for a variety of platforms, which include C and Java-based APIs
    • Libraries for Google Android and Apple iOS
    • JMS client libraries
    • JavaScript API for HTML5-based applications
  • Reliability
    • Assured delivery of messages
    • Support for MQTT qualities of service (QoS) 0,1, and 2 (best effort, at least once, and exactly once)
    • Local transaction support
    • Support for high availability configurations
    • SNMP monitoring
    • Support for log file rotation, purging, and offloading
  • Security
    • Authentication through local user store or external Lightweight Directory Access Protocol (LDAP) servers
    • Secure Sockets Layer (SSL) and Transport Level Security (TLS) support (SSL v3 and TLS 1.0, 1.1, and 1.2)
    • Fine-grained messaging authorization policies, which restrict access that is based on combinations:
      • User or group
      • Client identifier
      • Protocol
      • Network interface
      • Listening address or port
      • Client IP address or range
      • Destination (topic and queue) name
    • OAuth 2.0 support to securely delegate authorization to a remote server. OAuth Authorization Servers that can be used with MessageSight include the DataPower appliances that contain an OAuth authorization server feature.
  • Single signon support by using LTPA tokens within cookies in the HTTP header when connecting with WebSockets.
  • Integration
    • Extends and connects to IBM MQ infrastructures.
    • Supports mapping MessageSight destinations to and from IBM MQ destinations.
    • Supports connectivity to WebSphere Message Broker via JMS and or MQTT nodes.
    • Integrates with Java environments.
    • Integrates with rich HTML5-based web applications.
    • Allows development of interactive mobile messaging applications with IBM MobileFirst
  • Simplified deployment
    • Allows complete configuration and operation within 30 minutes.
    • Delivers easy-to-use, web-based, and command-line interfaces.
    • Requires minimal configuration options.
    • MessageSight is available to support non-production and production environments.

In addition, the product is provided free of charge for development use and is available for download at the IBM MessageSight website.

New in IoT MessageSight 2.0

  • Scale beyond an instance.
    • You can now cluster multiple MessageSight instances to scale to enormous numbers of device connections. The cluster creates a shared topic tree across the server instances. This enables publication and subscription of messages across the cluster that is independent of the server devices to which they are connected.
    • The web UI is now separately installable and can address multiple instances. This makes it easy to administer your estate.

For example, MessageSight instances A and B are clustered. If a client 1 connects to MessageSight A and client 2 connects to MessageSight B, then when client 2 sends a message bound for client 1, the message will be automatically routed between MessageSight B and A to reach client 1.

  • RESTful administration API.
    • Administration is simpler with the new REST administrative API. You can issue commands simply from the command line by using a REST client, such as Curl. Easily create scripts to run from a remote client automatically. This makes scripting common actions easy allowing you to move configurations from development to test or quality assurance and on to production systems. This makes it easier to ensure your system test environment simulates your production environment and to avoid mismatches.
  • Expanded environments.
    • MessageSight is now available as Linux RPMs and can be installed on both RedHat and CentOS Linux.
    • MessageSight can now be deployed as a Docker image, which improves portability and enables automation across your software delivery pipeline.
    • MessageSight can be deployed within VMware ESXi on either a Red Hat or CentOS base image.
    • MessageSight can be deployed on public cloud infrastructure in IBM SoftLayer, Amazon, and Azure cloud environments.
  • Security. When using client certificates to control access for client devices, if you have a device which has gone rogue or has been compromised in some way, you can blacklist the device. You can use the certificate revocation list to safeguard your systems and prevent access.
  • Performance enhancements. Significant performance enhancements are included for persistent messaging (QoS 1 and 2).
  • High availability. The high availability channel can now be encrypted and thread health monitoring is improved. The achievable distance between a high availability pair is significantly increased and it is now possible to split the pair between different data centers.
  • Additional protocols. MessageSight now has a fully supported protocol plug--in feature. This allows you to add support for an additional protocol, by coding a plugin and loading it into the system. You might use this to connect legacy sensors that cannot be changed to use MQTT. You may find that there is a regulatory protocol for a particular industry, such as smart meters. You can expand the system and use a common infrastructure for all your sensors and devices, both new and old.
  • New licensing option for high-availability configurations
  • An Idle Standby licensing option is now available for MessageSight that:
    • Offers reduced price licenses for high-availability scenarios that use the high availability feature by using multiple MessageSight instances.
    • Makes high-availability scenarios by using this software failover capability more affordable.

Accessibility by people with disabilities

A US Section 508 Accessibility Compliance Report containing details on accessibility compliance can be found on the Product accessibility information website.

Section 508 of the US Rehabilitation Act

IoT MessageSight is capable, as of June 10, 2016, when used in accordance with associated IBM documentation, of satisfying the applicable requirements of Section 508 of the Rehabilitation Act, provided that any assistive technology used with the product properly interoperates with it. A US Section 508 Voluntary Product Accessibility Template (VPAT) can be found on the IBM Accessibility website.



Back to topBack to top

Operating environment

Top rule

Hardware requirements

IoT MessageSight 5.0

Disk space: 25 GB for first disk; 16 GB for second disk

Memory: 4 GB for developer system; 16 GB for nonproduction and production systems

Processor: Two virtual CPUs for developer system; four virtual CPUs for nonproduction and production systems

Other: One network interface for developer system; two 1GBE network interfaces for nonproduction and production systems

IoT MessageSight 2.0

For the server

  • Two 1GbE network interfaces
  • 16 GB of memory
  • Intel or AMD x86-64 processor with at least four cores
  • 25 GB, for first disk
  • 64 GB, for second disk

For the web UI

  • One network interface
  • 4 GB of memory
  • Intel or AMD x86-64 processor
  • 16 GB disk space

Software requirements

IoT MessageSight 5.0

One of the following operating systems:

  • CentOS 7.4 or later x86-64
  • RHEL Server 7.4 or later x86-64

One of the following hypervisors:

  • VMware Workstation 12.5.9+
  • VMware Workstation Player 12.5+
  • Oracle VM Server for x86 (all supported versions)
  • VMware ESXi 5.5+

One of the following browsers:

  • Mozilla Firefox 52+
  • Google Chrome 69+
  • Microsoft Internet Explorer 11
  • Microsoft Edge 17+
  • Apple Safari 12+

IoT MessageSight 2.0

One of the following operating systems:

  • RHEL Linux 7 in x86_64
  • CentOS 7 on x86_64

IoT MessageSight 2.0 can be installed on bare metal servers to meet the minimum requirements, or a virtual server in the following cloud providers and hypervisor:

  • Hypervisors: VMware ESXi 5.5 or higher
  • Cloud Providers
    • SoftLayer
    • Amazon AWS
    • Microsoft Azure

IoT MessageSight 2.0 requires one of the following browsers that runs in a remote machine, if using the Web UI for configuration:

  • RHEL Linux 6 or SLES 11
    • Firefox 38 ESR
    • Chrome (latest version)
  • Windows 7 or 8
    • Firefox 38 ESR
    • Chrome (latest version)
    • Internet Explorer 11
  • Mac OS X
    • Firefox 38 ESR
    • Chrome (latest version)
    • Safari 9


Back to topBack to top

Planning information

Top rule

Customer responsibilities

Not applicable



Back to topBack to top

Publications

Top rule

IoT MessageSight 5.0

Effective December 14, 2018, product information will be available in IBM Knowledge Center.

IoT MessageSight 2.0

Effective June 10, 2016, product information will be available in IBM KnowledgeCenter.



Back to topBack to top

Trademarks

Top rule

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.

Windows is a trademark of Microsoft Corporation.

Terms of use

IBM products and services which are announced and available in your country can be ordered under the applicable standard agreements, terms, conditions, and prices in effect at the time. IBM reserves the right to modify or withdraw this Sales Manual at any time without notice. This Sales Manual is provided for your information only. Additional terms of use are located at

Terms of use


© IBM Corporation 2020.