Download mq channel monitor

IBM MQ (formerly known as IBM WebSphere MQ), IBM's Message Oriented Middleware (MOM) offering, has a primarily queue based infrastructure. Applications Manager's middleware monitoring capabilities allows you to monitor the performance attributes of MQ Objects like channels and queues while also enabling easy alerting, health check and management of your IBM Integration Bus. Resolve incidents before they become an issue, enjoy improved service levels and reduced risk of downtime within your IBM MQ infrastructure.Monitor Queue Manager Discovery entire Queue Manager clusters, monitor every individual queue as well as multiple queue mangers on multiple hosts. Determine queue usage stats, the percentage of the queue free and track the messages causing problems. Find the oldest message age, track excessive queue depths and manage queue traffic. Monitor Channel Stats Get detailed information about channels associated with a specific queue manager. Channel-level monitoring provides a graphical representation of various attributes, like the channel traffic (bytes and buffers sent and received). Calculate the message count for the selected queue over time, data flow to and from the transmission channel, transmission speeds and compression rates for various time intervals. Track Performance of more MQ components Monitor the health of your messaging system by tracking MQ objects like listener processes of four types of listeners: TCP, NetBIOS, SPX, and LU6.2 and session count. Manage and monitor the health of MQ services and create reports on service stats. Manage Your MQ Configuration - Configure, change and compare queues, messages, and more Event Log Get detailed information about each type of event: queue manager, channel, and performance. Generate event messages when certain events occur. Monitor command and configuration events, which are very useful for generating audit trails. Perform simple event filtering and event search using event name, type and more. Generate PDF reports of events stats over various time

Content Home Products for IBM MQ z/OS Products for IBM MQProducts for MQTT -->Products for MQTT Licensed As Free Open Source » Universal File Mover » MQ Channel Monitor » MQ File Mover » Message Multiplexer » Message Router » MQ Port Scan » MQRC2 » MQWhat » Round Robin Messaging » PSCI » ServerStatus Partners / Resellers About UsSupport Support InfoInformation Roger's Blog Follow Us on Twitter YouTube Channel IBM MQ Library Links MQTT News White Papers Java Linux Windows z/OS (OS/390) Recent News November 05, 2021 Capitalware releases MQ Visual Edit v3.2.0. Read More November 05, 2021 Capitalware releases MQ Visual Browse v3.2.0. Read More November 04, 2021 Capitalware releases MQ Batch Toolkit v3.2.2. Read More July 23, 2020 Capitalware releases MQ Auditor v3.2.0. Read More July 23, 2020 Capitalware releases MQ Authenticate User Security Exit v3.5.0. Read More July 23, 2020 Capitalware releases MQ Authenticate User Security Exit for z/OS v3.5.0. Read More July 23, 2020 Capitalware releases MQ Channel Connection Inspector v1.2.0. Read More July 23, 2020 Capitalware releases MQ Channel Connection Inspector for z/OS v1.2.0. Read More July 23, 2020 Capitalware releases MQ Channel Encryption v3.4.0. Read More July 23, 2020 Capitalware releases MQ Channel Encryption for z/OS v3.4.0. Read More July 23, 2020 Capitalware releases MQ Channel Throttler v1.3.0. Read More July 23, 2020 Capitalware releases MQ Message Encryption v4.2.0 Read More July 23, 2020 Capitalware releases MQ Message Replication v2.2.0. Read More

Introduction Copied The MQ Channel plugin is part of a suite of plugins designed to monitor an IBM WebSphere MQ server. MQ is a middleware product which allows independent client programs to communicate by passing messages to each other via a message queue. These queues provided added benefits by adding reliability of communications, and storing and persisting messages allowing client programs to operate asynchronously.The MQ Channel plugin monitors all configured channels for a particular Queue Manager (an MQ system service which holds a set of queues). Using the Geneos framework administrators can set alerts for events such as a channel going down, or if an unknown process connects on a channel. MQ Architecture Copied Websphere MQ servers are based around queues of messages, each Message containing some arbitrary application data. Messages are contained within Queues, which are in turn managed by a Queue Manager. An MQ server may contain several queue managers.Client applications communicate with each other by sending messages via a queue. To do so they connect to a queue manager - typically using TCP/IP - and send or receive messages accordingly.Communication between components are handled using pre-configured links called Channels. Channels are mono-directional, so a full-duplex link between two components requires two channels.A queue manager also has an associated Command Server, which allows a remote client to execute commands. The MQ Channel plugin connects as a client to the configured queue manager, and obtains monitoring data by issuing status query commands using the command server. View Copied MQ Channel produces a single dataview displaying the configured channels for the queue manager it is connected to, and the selected attributes for each view. By default, these attributes include those produced by a DISPLAY CHSTATUS command. An example of this is shown below.The legends below list all columns which can

Copied This setting specifies the name of the queue manager the plugin is to connect to. If a channel table is used, then this name should match the one specified for the connection.Mandatory: Yes channels Copied The channels section specifies the channels that will be monitored by the plugin. By default, if no channels are specified then all channels on the queue manager will be monitored.Mandatory: No channels > channel channel" href="#channels--channel" title="Link to this section"> Copied Specifies a channel (or channels for a generic name) for the MQ Channel plugin to monitor. If no channels are specified all channels on the queue manager will be monitored.Mandatory: No channels > channel > matches channel > matches" href="#channels--channel--matches" title="Link to this section"> Copied This setting specifies the exact name of a channel to monitor.Mandatory: No channels > channel > startsWith channel > startsWith" href="#channels--channel--startswith" title="Link to this section"> Copied This setting specifies a prefix of a channel name. All channels on the queue manager starting with the prefix will be monitored.The startsWith setting uses the generic queue names feature of the command server. For example, if you entered the value SYSTEM then the monitored channels would be the same as the channels returned when you issue the command DISPLAY CHSTATUS(SYSTEM\*) using the runmqsc MQ utility. You may also add the trailing \* in the setting value if you wish to match the standard MQ syntax.Mandatory: No Columns Copied By default, MQ Channel will display columns including the data you would see when executing the DISPLAYCHSTATUS command in the runmqsc MQ utility, along with some additional metrics (see below for more details). The columns section allows users to configure a set of columns that they wish to see, and ignore data which is not relevant for their particular monitoring configuration. columns Copied

Added to the mqm group, authorised to connect to the Queue manager, channel, and queue. As the netprobe user would be the one used for MQ authorisation checks. But if ADOPTCTX attribute is set to YES then the Connection Authentication username provided would be used instead throughout the connection. See the IBM documentation on MQCSP password protection and on Connection Authentication: Configuration for more information. Note The Security Connection Authentication is applicable only to IBM MQ Version 8.0. If the version is lower than 8.0 then this configuration will have no bearing.This setting only works if the mqServer setting is configured.Mandatory: No connection > securityConnectionAuthenticationConfig > password securityConnectionAuthenticationConfig > password" href="#connection--securityconnectionauthenticationconfig--password" title="Link to this section"> Copied This setting allows the user to specify the password for the given username that will connect to the MQ server which supports Security Connection Authentication. See the IBM documentation on MQCSP password protection and on Connection Authentication: Configuration for more information.Choose the appropriate field when specifying the password:stdAES — use this to input your plaintext password. If you select stdAES, you can define your password directly in the sampler and store it in standard AES encryption hash in the Gateway.var — use this to pass the password as a variable. The variable is defined in Managed entity > Advanced > Var. This is useful for situations where you have multiple samplers that use the same credentials.extPwd — use this for passwords provided by an external provider. For more information, see Securing your Gateway with an external password provider in Secure Passwords. This setting only works if the mqServer setting is configured.Mandatory: No Channels Copied By default, MQ Channel will monitor all channels on the configured queue manager. The channels section allows users to configure only the channels they are interested in for monitoring. queueManager