New: MQ Channel Throttler v1.0.0

Capitalware Inc. would like to announce the official release of MQ Channel Throttler v1.0.0.

MQ Channel Throttler (MQCT) provides the ability to control/throttle the number of messages or bytes that flow over a channel. MQCT operates with IBM MQ (aka WebSphere MQ & MQSeries) v6.0, v7.0, v7.1, v7.5 and v8.0 in Windows, Unix, IBM i (OS/400) and Linux environments. It operates with Sender, Receiver, Server, Requester, Cluster-Sender, Cluster-Receiver, Server Connection and Client Connection channels of the WMQ queue managers.

MQCT is a simple drop-in solution that provides throttling for MQ queue managers. The throttling can be configured for queue manager to queue manager channels or for client application to queue manager channels.

  • Queue manager to queue manager throttling means all messages flowing over a channel between 2 queue managers will be throttled.
  • Client application to queue manager throttling means application-level message data flowing between a WMQ client application and queue manager will be throttled.

The MQCT can be configured as a queue manager channel message exit or as a channel sender/receive exit.

On IBM i, Linux, Unix and Windows, MQCT can be configured and used with a non-default installation of WMQ in a multi-install MQ environment.

For more information about MQCT, please go to:
http://www.capitalware.com/mqct_overview.html

Regards,
Roger Lacroix
Capitalware Inc.

This entry was posted in Capitalware, IBM i (OS/400), Linux, MQ, MQ Channel Throttler, Unix, Windows.

One Response to New: MQ Channel Throttler v1.0.0

  1. All,

    To bring this topic full circle, I took T.Rob’s and zpat’s comments regarding MQ Channel Throttler (MQCT) and implemented them.

    So the new and improved MQCT v1.0.0 also includes:
    – the ability to throttle by connection calls (MQCONN & MQCONNX)
    – the ability to throttle by open calls (MQOPEN)
    – will (optional) emit an alert to an event queue if MQCT inserts a delay
    – will (optional) write a syslog message if MQCT inserts a delay
    – if the MQCT IniFile is changed, MQCT will dynamically update itself

    I changed the ClientAction keyword to APIType because MQCT is no longer about just throttling messages.
    APIType supports:
    – C means that MQCT will throttle for MQCONN and MQCONNX calls
    – O means that MQCT will throttle for MQOPEN call
    – G means that MQCT will throttle for MQGET call
    – P means that MQCT will throttle for MQPUT and MQPUT1 calls

    i.e.
    APIType=C,O,G,P

    I have updated the documentation and the web site.

    If anyone has any other comments, please share them.

    Regards,
    Roger Lacroix
    Capitalware Inc.