The log messages are as important as the transactions - as they provide problem resolution, transaction replay and audit functions - to some extent the logging is more important than the transaction - ...
We do have local QMgrs on our IIB servers, however we only use them to enable the broker functions that require the SYSTEM.BROKER.* queues. In future we may not need this local MQ QMgr as we may depr ...
As per the last post - the connections are all MQ client connections from IIB to the remote MQ QMgr via an IIB MQ Endpoint Policy. The tests have been repeated and the results are consistent - the pe ...
It looks like the resolution to this performance issue was to create separate queues for each of our brokers for the logging subflow - initially our logging subflows for all brokers put to the same qu ...
Adding additional Linux IIB brokers only leads to a slight increase in performance - which may indicate that the bottleneck is a combination of the TransactionMode='No' setting in our logging subflow ...
New Architecture:
IIB v.10.0.0.9 brokers hosted on Linux RHEL 7.2 servers connect via MQ Endpoint policies to remote MQ 7.5.0.6 QMgrs hosted on AIX 7.1 (which we will be u ...
I have an issue with a subflow used for logging in the MQ Output node where the Transaction Mode is set to 'No'. The reason it is set to 'no' is so that on failure the log message is always ge ...