Migration of telemetry applications from using WebSphere Message Broker version 6 to use IBM WebSphere MQ Telemetry and WebSphere Message Broker version 7.0

Migrating telemetry applications from using WebSphere® Message Broker v6 to use IBM® WebSphere MQ Telemetry and WebSphere Message Broker v7 requires a number of steps. Only the last step involves modifying the telemetry application. The first steps are migrating IBM WebSphere MQ and WebSphere Message Broker to v7.

You can run WebSphere Message Broker v6 with IBM WebSphere MQ Telemetry, if you convert all your SCADA flows to use IBM WebSphere MQ Telemetry. You must migrate IBM WebSphere MQ to Version 7.1 to use IBM WebSphere MQ Telemetry.

Before you begin

Your target environment is going to run the IBM WebSphere MQ Telemetry feature on IBM WebSphere MQ Version 7.1, with WebSphere Message Broker v7. IBM WebSphere MQ Telemetry runs on Windows, AIX®, and Linux®, see https://www.ibm.com/software/products/en/wmq-telemetry for detailed information.

Consider setting up parallel development and test environments before starting the task of upgrading and migrating all the components. In a large production environment, migrating the telemetry applications is the last step after upgrading IBM WebSphere MQ and WebSphere Message Broker to v7.

An alternative migration path is to migrate telemetry applications before migrating WebSphere Message Broker to v7. It is likely to be more effort to follow this path. New functionality in WebSphere Message Broker v7, namely republishing to the same topic, makes it easier to migrate some flows from SCADA to IBM WebSphere MQ Telemetry. By migrating the telemetry applications last you also avoid testing telemetry twice. First, you would test telemetry with WebSphere Message Broker v6, using the publish/subscribe engine in the broker. Second, you would test telemetry with WebSphere Message Broker v7, using IBM WebSphere MQ as the publish/subscribe engine.

About this task

You have created telemetry applications that use the MQTT protocol and the Supervisory Control And Data Acquisition (SCADA) nodes in WebSphere Message Broker v6. You want to upgrade your WebSphere Message Broker deployment from v6 to v7, but SCADA nodes are not supported in v7 of WebSphere Message Broker. Connectivity support for the MQTT protocol has been moved from WebSphere Message Broker to IBM WebSphere MQ. You want to leave as much of the telemetry application unchanged as you can. You must migrate the telemetry connectivity between the MQTT client and WebSphere Message Broker. Migrate it from the SCADA nodes in WebSphere Message Broker to the telemetry channels in IBM WebSphere MQ Version 7.1.

Procedure

  1. Upgrade IBM WebSphere MQ
  2. Install the IBM WebSphere MQ Telemetry feature.
  3. Upgrade WebSphere Message Broker to v7.
  4. Modify existing MQTT client applications to use v3 of the MQTT protocol.

    If your client applications are already using v3 of the MQTT protocol, no modifications to the applications are required.

    If you are using an MQTT client library with your applications, the library might not support MQTT v3. Migrate the library to use one of the C or Java MQTT v3 libraries provided with IBM WebSphere MQ Telemetry .

  5. Modify your message flows from using SCADA nodes to using MQInput or JMSInput nodes.