Additional configuration options for IBM MQ Bridge to blockchain

IBM MQ Version 9.1.2 introduces a change to the way in which tracing and logging work on IBM MQ Bridge to blockchain.


Changes from the Version 9.1.0 IBM MQ Bridge to blockchain

By default, there are no changes to behavior from the Version 9.1.0 bridge, other than the log file now starting to rotate. See Rotating logs for more information.


Trace and debug interaction

The debug flag continues to act as before. That is, -d1 gives bridge debug information and -d2 turns on debug logging for the prerequisite components. However, if you have enabled IBM MQ trace when you start the bridge, the -d2 level reporting is automatically turned on.


Rotating logs

The default behavior for the log file changes to have three log files, each of size 2 MB. We can override these values using additional configuration properties. The existing configuration attribute, or command line parameter for the log file, is taken as the base name for the logs, with an index added.

If the configured log file has:

  • No filetype, the index is added to the end of the filename.

    Set the log file to abc, results in logs called abc.0, abc.1, and so on.

  • A filetype, the index is inserted before the filetype.

    Set the log file to abc.log, results in logs called abc.0.log, abc.1.log, and so on.

Notes:

  1. As the bridges can be running with arbitrary user permission, it is not possible to force a particular directory, for example, /var/mqm/qmgrs/<qm>/errors, for the logs.
  2. The same information continues to be written to the stdout and stderr streams.
  3. Whenever an individual log file gets reopened, basic configuration information is reprinted. The information will always be available, instead of being printed once only at the start of the program.

Parent topic: Configure IBM MQ for use with blockchain