ISAlert is a flexible tool for monitoring a WebSphere® MQ environment. ISAlert uses a program, the ISAlert Server, to collect record and display data related to the operation of your WebSphere® MQ Series (WMQ) messaging operation. The ISAlert Server runs on a single system (which does not require a WMQ Server installation), using a single thread to monitor each queue manager.

ISAlert detects events, which occur within the scope of each queue manager. These events are conditions which may have an adverse impact on your messaging system, such as a broken channel connection between two queue managers or a large number of pending messages on a particular queue. When an event is detected, ISAlert generates an alarm message containing information about the event. ISAlert can also record message send and receive counts for channels, allowing you to gain an accurate picture of messaging traffic without modifying your applications.

Alarms and performance data are recorded in log files, as well as being available as input to an external application such as a mail sender.

The following tables list some of the Features of ISAlert:

ISAlert Server is designed to Monitor Threshold on:
  • Number of pending messages on any local queue.
  • Number of pending messages on any local transmit queue.
  • The number of readers and writers using any local queue.
  • WMQ queue service interval events
ISAlert Server can Monitor Performance Data from:
  • Message, send and receive counts for any local channel.
  • Message byte, send and receive counts for any local channel.
ISAlert Server has these selectable options:
  • The ISAlert Server will run regardless of the state of a queue manager being monitored. If a particular instance of WMQ is unavailable, the Server will attempt to re-establish connection on a periodic basis.
  • Alarm text is specified in the configuration file, allowing modification of alarm text without requiring modification of the ISAlert Server
  • Reporting channel status is optional.
  • Reporting performance data is optional.
  • Performance data (i.e., channel traffic volume) can be monitored and reported on an interval greater than the ISAlert Server sample cycle.
ISAlert Server supports these Rules and Definitions:
  • Exceeding a threshold is defined as an event.
  • Dropping below a threshold after exceeding that threshold is defined as an event. This event is called “clearing the threshold”.
  • Threshold data is sampled on user-defined cycle, which cannot be less than 1 second.
  • Any alarm message which reports a threshold being exceeded can be reported with one of two frequencies:
    • When it first occurs, or
    • Every scan cycle while the threshold is being exceeded
  • Every alarm message has a user-defined severity associated with it.
  • All log entries are preceded by a timestamp of the form "yyyy-mmm-dd:hh:mm:ss".
  • Server operation is configured using an ASCII-text configuration file.
  • Both cumulative and incremental performance data can be reported.

The following table list the major Requirements of ISAlert:

ISAlert Server
One ISAlert Server can monitor up to 30 queue managers simultaneously.
WMQ Software

WMQ V5.2 or later on each monitored queue manager:

  • The command server must be running
  • A permanent queue dedicated to ISAlert must be defined
  • WMQ client connections must be supported
TCP/IP Sockets
ISAlert uses 1 socket for each monitored queue manager plus 1 socket to support operations common to all monitored queue managers. It also requires a dedicated TCP/IP port assignment.
Disk requirements for ISAlert.
Alarm and performance monitoring messages (typically 80-120 characters per message) are written to disk on the Server’s system.
Supported Platforms Windows, Linux, HP_UX, HP_UX11i and OpenVMS