Location of telemetry logs, error logs, and configuration files
Find the logs, error logs, and configuration files used by MQ Telemetry.
Note: The examples are coded for Windows systems. Change
the syntax to run the examples on AIX® or Linux® systems.
Server-side logs
The telemetry (MQXR) service writes FDC files to the IBM® MQ error directory:
WMQ data directory\errors\AMQ nnn.n.FDC
The format of the FDC files is MQXRn.FDC
.
It also writes a log for the telemetry (MQXR) service. The log path is:
WMQ data directory\Qmgrs\qMgrName\errors\mqxr.log
The format of the log file is mqxr_n.log
.
The IBM MQ telemetry sample configuration created by
IBM MQ Explorer starts the telemetry (MQXR) service using the
command runMQXRService, which is in WMQ Telemetry installation directory\bin. This command writes to:
WMQ data directory\Qmgrs\qMgrName\mqxr.stdout
WMQ data directory\Qmgrs\qMgrName\mqxr.stderr
Server-side configuration files
- Telemetry channels and telemetry (MQXR) service
-
Restriction: The format, location, content, and interpretation of the telemetry channel configuration file might change in future releases. You must use IBM MQ Explorer, or MQSC commands, to configure telemetry channels.
IBM MQ Explorer saves telemetry configurations in the mqxr_win.properties file on Windows systems, and the mqxr_unix.properties file on AIX or Linux systems. The properties files are saved in the telemetry configuration directory:
- JVM
- Set Java properties that are passed as arguments to the telemetry (MQXR) service in the file, java.properties. The properties in the file are passed directly to the JVM running the telemetry (MQXR) service. They are passed as additional JVM properties on the Java command line. Properties set on the command line take precedence over properties added to the command line from the java.properties file.
- JAAS
- The JAAS configuration file is described in Telemetry channel JAAS configuration, which includes the sample JAAS configuration file, JAAS.config, shipped with MQ Telemetry.
- Trace
- See Tracing the telemetry (MQXR) service. The parameters to configure trace are stored in two files:
and there is a corresponding file:WMQ data directory\Qmgrs\qMgrName\mqxr\trace.config WMQ data directory\Qmgrs\qMgrName\mqxr\mqxrtraceOn.properties
WMQ data directory\Qmgrs\qMgrName\mqxr\mqxrtraceOff.properties
Client-side log files and client-side configuration files
For the latest information and downloads, see the following resources:
- The Eclipse Paho project, and MQTT.org, have free downloads of the latest telemetry clients and samples for a range of programming languages. Use these sites to help you develop sample programs for publishing and subscribing IBM MQ Telemetry Transport, and for adding security features.
-
The IBM Messaging Telemetry Clients SupportPac is no longer available for download. If you have a previously downloaded copy, it has the following contents:
- The MA9B version of the IBM Messaging Telemetry Clients SupportPac included a
compiled sample application (mqttv3app.jar) and associated client library
(mqttv3.jar). They were provided in the following directories:
- ma9c/SDK/clients/java/org.eclipse.paho.sample.mqttv3app.jar
- ma9c/SDK/clients/java/org.eclipse.paho.client.mqttv3.jar
- In the MA9C version of this SupportPac, the /SDK/ directory and contents
was removed:
- Only the source for the sample application (mqttv3app.jar) was provided. It
was in this directory:
ma9c/clients/java/samples/org/eclipse/paho/sample/mqttv3app/*.java
- The compiled client library was still provided. It was in this directory:
ma9c/clients/java/org.eclipse.paho.client.mqttv3-1.0.2.jar
- Only the source for the sample application (mqttv3app.jar) was provided. It
was in this directory:
- The MA9B version of the IBM Messaging Telemetry Clients SupportPac included a
compiled sample application (mqttv3app.jar) and associated client library
(mqttv3.jar). They were provided in the following directories: