IBM MQ
  • 25 Nov 2021
  • 3 Minutes to read
  • Dark
    Light
  • PDF

IBM MQ

  • Dark
    Light
  • PDF

In this section, we will take a detailed look at how to monitor IBM MQ. Monitoring a queue involves creating the rules for settings the alert thresholds. With BizTalk360, you can monitor the health of the queue as well as other parameters associated with the queue. The other parameters include Current Queue Depth, Backout queue Depth, Current Queue usage, Backout Queue Usage, and Message Age.

  1. Log in to the BizTalk360 application
  2. Select the 'Environment'
  3. Click 'Monitoring' in the navigation panel
  4. Click the expand button against the 'Manage Mapping' and select 'Queues'
  5. Select the Alarm name (see Manage Alarms) from the drop-down, which you would like to associate the queue for monitoring
  6. Click the 'IBM MQ' tab to automatically list out all the Send Ports/Receive Locations which are using the MQSC adapter or the MQSeries adapter

  • To configure monitoring for a particular queue, in the grid, click the row of that queue

  • If you are using MQSC Adapter, BizTalk360 will automatically fetch all the details from the BizTalk admin console
  • If you are using MQSeries adapter, then you will need to manually enter the Channel Name, the Connection Name, the User Id, and the Password
  • Create the rules for threshold alerts under the queue configuration


While creating a rule in Queue monitoring, You can add up to 5 conditions for alert thresholds based on your needs. For each condition you add, you can create 2 sub-conditions (AND/OR).
  • Click 'Save' to save the monitoring for the queue

In-depth look at Queue Monitoring Rules screen in BizTalk360

In this section, we will take a deep dive into the Queue Monitoring Rules screen to understand the functionality of every option and control present on the screen.

  • Queue Manager Name - This option specifies the Queue Manager name that is responsible for transferring data to another queue manager via message channels. It’s a logical container for the message queue.
  • Queue Name - This option specifies the message queue name
  • Channel Name - This option specifies the channel name which is responsible for communicating between two queue managers. IBM MQ uses message channels to transfer messages between queue managers.
  • Connection Name - This attribute is the communication connection identifier
  • Transport Type - Currently BizTalk360 supports TCP type only
  • User ID - The name of the user who has the authority to perform any operation on the queue. While creating a user in Computer Management, use a name with less than 8 characters
  • Password - User password
  • SSL Cipher Specification - Every MQ Channel definition includes the SSLCIPH attribute. The value is a string with a maximum length of 32 characters. SSL Cipher specification is optionally
  • SSL Peer Name - Peer name specifies the SSL Peer Name used on the channel. The SSL Peer attribute is used to check the Distinguished Name (DN) of the certificate from the peer queue manager or client at the other end of an IBM® WebSphere® MQ channel
  • Message Age Units - This metric configuration allows you to choose the time parameter (Day/Hour/Minutes/Seconds) for finding the duration of existing messages in the queue

Editing the Monitoring Rules

BizTalk360 allows users to modify the configured rules from the monitor results blade. The system does not allow you to edit the Queue Manager name and Queue name but allows you to edit other properties and the rule conditions associated with the queue. For instance, the user wants to add a sub-condition to the existing rule condition.

Follow the steps as shown below to edit the rule information.

  • In the grid, click the row against the queue you wish to edit
  • The configuration blade will be opened
  • Edit the rules as per your requirements. In this case, you can click the icon at the end of the condition to add an operator
  • Select the operator and enter the values
  • Click 'Save' to update the monitoring for the queue


Was this article helpful?

What's Next