IBM MQ 7.5 was EOS 30th April 2018.Click EOS notice for more details
Configuring a queue manager for telemetry on Windows
Follow these manual steps to configure a queue
manager to run IBM®WebSphere® MQ Telemetry.
You can run an automated procedure to set up a simpler configuration
using the IBMWebSphere MQ Telemetry support for IBMWebSphere MQ Explorer.
Create and start a queue manager. The queue manager is referred
to as qMgr in this task.
As part of this task you configure the telemetry (MQXR) service. The MQXR property settings are
stored in a platform-specific properties file: mqxr_win.properties. You do not
normally need to edit the MQXR properties file directly, because almost all settings can be
configured through MQSC admin commands or MQ Explorer. If you do decide to edit the file directly,
stop the queue manager before you make your changes. See MQXR properties.
When the telemetry (MQXR) service is first started,
it creates SYSTEM.MQTT.TRANSMIT.QUEUE.
It
is created manually in this task, because SYSTEM.MQTT.TRANSMIT.QUEUE must
exist before the telemetry (MQXR) service is started, to authorize
access to it.
Set the default transmission queue
When the telemetry (MQXR) service is first started, it does not alter the queue manager to make
SYSTEM.MQTT.TRANSMIT.QUEUE the default transmission queue.
To make SYSTEM.MQTT.TRANSMIT.QUEUE the default transmission queue alter the
default transmission queue property. Alter the property using the IBMWebSphere MQ Explorer or with the command in Figure 1.
Altering the default transmission queue might interfere with your existing configuration. The
reason for altering the default transmission queue to SYSTEM.MQTT.TRANSMIT.QUEUE is
to make sending messages directly to MQTT clients easier. Without altering the default transmission
queue you must add a remote queue definition for every client that receives IBMWebSphere MQ messages; see Sending a message to a client directly.
Verify the configuration by running the sample
client.
For the sample client to work with your telemetry channel, the channel must authorize the client
to publish, subscribe, and receive publications. The sample client connects to the telemetry channel
on port 1883 by default. See also IBMWebSphere MQ Telemetry sample programs.
Creating SYSTEM.MQXR.SERVICE manually
Figure 2 shows the runmqsc command to create the
SYSTEM.MQXR.SERVICE manually on Windows.