ManageEngine® Applications Manager IBM WebSphere MQ | ||
IBM WebSphere MQ servers are monitored based on the attributes such as listener stats, channel monitoring, etc. and the different web applications and EJB deployed in the server. You can also monitor the operation of the queue managers through event logs. The monitoring details of IBM WebSphere MQ server are represented graphically that helps to understand the parameters with ease. You can also configure thresholds to the attributes monitored by the server based on these details.
Availability tab, gives the Availability history for the past 24 hours or 30 days. Performance tab gives the Health Status and events for the past 24 hours or 30 days. List view enables you to perform bulk admin configurations. Click on the individual monitors listed, to view the following information.
The WebSphere MQ server attributes monitored are classified under the following tabs in Applications Manager:
Parameter |
Description |
---|---|
Name |
The Display name of the Monitor |
Health |
Represents the health status |
Last Polled at |
Time at which the previous poll had started |
Next Poll at |
Time at which the next poll has been scheduled |
Availability |
Shows the current status of the server - available or not available. |
Parameter | Description |
---|---|
Name |
The Display name of the monitor |
Health |
Represents the health status |
Command Server Status | Specifies the status the command server. It used to check whether the command server on the target queue manager is running or not |
Channel Initiator Status | Specifies the status the channel initiator. It used to check whether the channel initiator on the target queue manager is running or not |
Active Connections | The current number of connections to the queue manager. |
Graphical View of Events Count | Count of events occurred in the below category in last data collection.
|
Parameter | Description |
---|---|
Queue Name |
Name of the Queue |
Current Depth |
Current queue depth. |
% of Queue Occupied |
Percentage of Queue Depth occupied against the max Queue Depth. |
Open Input Count |
Open input count (parameter identifier: MQIA_OPEN_INPUT_COUNT). |
Open Output Count |
Open output count (parameter identifier: MQIA_OPEN_OUTPUT_COUNT) |
Health |
Health of the Queue based on all the above attributes |
Queue Usage Graph | Graphical view queue depth percentage against the max Queue Depth |
% of Queue Free | Percentage of Queue Depth free against the max Queue Depth |
Uncommitted Messages | It indicates whether there are any uncommitted changes (puts and gets) pending for the queue.
|
Oldest Message Age | The age, in seconds, of the oldest message on the queue. |
Latency | The interval, in seconds, between messages being put on the queue and then being destructively read. |
Trigger Control | It indicates whether the triggering on the queue enabled or not.
|
Parameter | Description |
---|---|
Channel Name |
Name of the Channel |
Status |
Status of the channel - running |
Bytes Sent |
Number of bytes sent |
Bytes Received |
Number of bytes Received |
Buffers Sent | Number of buffers sent |
Buffers Received | Number of buffers Received |
Availability | Availability of Channel,based on the status attribute.If the status of the channle is RUNNING then it is considered to be available .If the channel is in other states then it is considered to be down. |
Health |
Health of the Channel based on all the above attributes |
Compression Time | The amount of time per message, displayed in milliseconds, spent during compression or decompression. |
Compression Rate | Rate of compression achieved in percentage. |
Parameter | Description |
---|---|
Listener Name |
Specifies the name of the listener |
Status |
The current status of the listener. The value can be:
|
Session Count | The number of sessions that the listener can use. This is valid only on Windows. |
Backlog | The number of concurrent connection requests that the listener supports. |
Health |
Health of the Listener based on all the above attributes |
Parameter | Description |
---|---|
Name | Name of the service |
Mode | Specifies on which mode the service was started
|
Type | Type of the service
|
Start Time | Specifies at which time the service was started.It is applicable only for Server type of service |
Alteration Time | Specified at which time the service configuration was last altered. |
Status | Status of the service:
It is applicable only for the server type of service |
WebSphere MQ events provide information about errors, warnings, and other significant occurrences in a queue manager. You can monitor the operation of the queue managers by analyzing these events. When an event occurs, the queue manager puts an event message on the appropriate event queue. The event message contains information about the event.
Search Options :
We have provided the On-demand event search with multiple search options in 'Event Log' tab. You can also export the event search result to PDF.
Event Category
From Date
To Date
Event Type
Any keyword in the event message
Note:
|
Events & Corresponding Queues
Events | Queues |
---|---|
SYSTEM.ADMIN.QMGR.EVENT | Local, Remote, Inhibit, Authority, Start & Stop |
SYSTEM.ADMIN.CHANNEL.EVENT | IMS Bridge, Channel, SSL |
SYSTEM.ADMIN.PERFM.EVENT | Performance |
SYSTEM.ADMIN.CONFIG.EVENT | Configuration |
SYSTEM.ADMIN.COMMAND.EVENT | Command |
SYSTEM.ADMIN.LOGGER.EVENT | Logger |
Event Categories:
Events | Queues |
|||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Start and Stop Events |
|
|||||||||||||||||||||||||||||||||
Performance Events |
|
|||||||||||||||||||||||||||||||||
Configuration Events |
|
|||||||||||||||||||||||||||||||||
Channel Auto Definition Events | DISABLED | |||||||||||||||||||||||||||||||||
Channel Events |
|
|||||||||||||||||||||||||||||||||
Command Events |
|
|||||||||||||||||||||||||||||||||
SSL Events |
|
|||||||||||||||||||||||||||||||||
Remote Events |
|
|||||||||||||||||||||||||||||||||
Authority Events |
|
|||||||||||||||||||||||||||||||||
Inhibit Events |
|
|||||||||||||||||||||||||||||||||
Logger Events |
|
|||||||||||||||||||||||||||||||||
Local Events |
|
|||||||||||||||||||||||||||||||||
Bridge Events |
|
Parameter | Description |
---|---|
Name |
The Display name of the Monitor |
Queue Manager | Name of the Queue Manager |
Command Queue | Name of the Command Input Queue |
Dead Letter Queue | Name of the Dead Letter Queue |
Transmission Queue | Name of the Transmission Queue |
Max length of Message | Specifies length of the longest message that the queue manager can handle |
Max Number of Handles | Specifies the maximum number of open handles that any one task can use concurrently |
Max Uncommitted Messages | Specifies the maximum number of uncommitted messages that can exist within a unit of work. |
Max Trigger Interval | Specifies the time interval (in milliseconds) used to restrict the number of trigger messages |
Platform | The operating system on which the queue manager is running |
Version | Version number of the queue manager |
You can also compare the values between the various attributes.
See Also
Creating New Monitor - IBM WebSphere MQ
IBM WebSphere Message Broker Monitoring
WebLogic Integration Servers |
IBM WebSphere Message Broker |