MQXR properties

MQXR property settings are stored in a platform-specific properties file: mqxr_win.properties or mqxr_unix.properties. You normally configure these properties by using MQSC admin commands or MQ Explorer.

When you start a queue manager for the first time, the template version of the MQXR properties file for your platform is copied from the mqinstall/mqxr/config directory to the mqinstall/qmgrs/qmgr_name/mqxr/config directory.

You do not normally need to edit the MQXR properties file directly, because all properties except one 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.

The property that you can only set by editing the file directly is webcontentpath. If your telemetry client app is a web app, you also need to serve the web app executable JavaScript to the browser. This requirement is explained in The MQTT messaging client for JavaScript(tm) and web apps. You use the webcontentpath property to specify the directory from which the web app executable files are served:
  • By default, webcontentpath is not present in the MQXR properties file. If webcontentpath is not present, the MQ telemetry server serves the web app executable files from the following default location: mqinstall/qmgrs/qmgr_name/mqxr/WebContent/your_client_app
  • if webcontentpath specifies a path, the MQ telemetry server serves the web app executable files from that location.
  • if webcontentpath is present and blank, the MQ telemetry server does not serve the web app executable files.