WebSphere MQ

The WebSphere MQ Device Driver allows Iotellect Server to perform monitoring of IBM WebSphere MQ server operability. The monitoring is performed via the native MQ communication protocol over an IP network.

Driver Information

Driver Plugin ID:

com.tibbo.linkserver.plugin.device.mq

Global Settings

None defined.

User Level Settings

None defined.

Device Account Properties

Connection Properties

Connection settings define how Iotellect Server communicates with an MQ server. These settings may be accessed using the Edit Device Properties action of Device Context. The following connection properties are available:

Property

Description

IP address or host name

Address of the MQ server.

Port

Port to connect on the MQ server (default is 1414).

Channel

Name of MQ channel to connect (default is ADMIN.CONN).

Timeout

Operation timeout (default is 30 seconds).

Device Assets

Assets are not supported by the driver.

Device Settings

The MQ device driver provides three tabular read-only settings:

  • Channels. This table contains information about every channel provided by MQ server, including channel name, type, status, start time and incoming/outgoing traffic volume.
  • Queues. This table contains information about every queue provided by MQ server, including queue name, depth, last get/put time, maximum and average message ages, counts of open inputs/outputs, and number of uncommitted messages.
  • Listeners. This table contains information about every listener provided by MQ server, including listener name, description, status, start time, backlog, and command/session counters.

Device Operations

No operations provided by the driver.

Device Events

No events provided by the driver.

Connection Handling

This driver makes the device Online if connection with MQ server was successfully established.

Synchronization Details

Synchronization between Iotellect Server and MQ server includes the following steps:

  • Reading the list of channels available on the MQ server and fetching information about each individual channel.
  • Reading the list of queues available on the MQ server and fetching information about each individual queue.
  • Reading the list of listeners available on the MQ server and fetching information about each individual listener.

Was this page helpful?