Discovered CITs

The WebSphere MQ discovery discovers the following CI Types.

Note To view the topology, see Topology.

CI Type

Key Attributes

Description

Composition    
Containment    
Dependency    

IBM MQ Channel (mqchannel)

Parent: Message Queue Resource

  • Name

  • Container: IBM MQ Queue Manager

This abstract CI Type represents MQ Channels. MQ Channels are required by Queue Managers to communicate with other Queue Managers. Channels have uni-directional and bi-directional communication (such as a request-response system) and require a second channel to return data. A channel sends or receives data on a specific port on a TCP/IP network.

IBM MQ Cluster (mqcluster)

Parent: Failover Cluster

Name Represents an MQ Queue Manager Cluster An MQ Cluster provides a flexible approach to join multiple Queue Managers with minimal configuration. This enables multiple instances of the same service to be hosted through multiple Queue Managers, resulting in higher performance, capacity, and resiliency. Queue managers can dynamically join or leave clusters.

IBM MQ Namelist (mqnamelist)

Parent: Message Queue Resource

  • Name

  • Container: IBM MQ Queue Manager

Represents an MQ Namelist. An MQ namelist contains a list of names and is typically used to contain a list of MQ Queue Manager Clusters. These namelists are then specified in the cluster namelist property and may be used by all Queue Managers in that cluster for look up.

IBM MQ Queue (mqqueue)

Parent: MQ Queue

  • Name

  • Container: IBM MQ Queue Manager

A Queue is a container of messages in the MQ infrastructure and controls how messages are routed between Queue Managers in the MQ infrastructure. Queues may be set up in several configurations to control message ordering and delivery (F/LIFO, message priority, sequential delivery, guaranteed delivery, and so on) and are optimized to carry small amounts of information.

IBM MQ Queue Manager (mqqueue)

Parent: Message Queue Resource

  • Name

  • Container: IBM WebSphere MQ CI

Represents an MQ Queue Manager. A WebSphere MQ instance may have one or more Queue Managers. The Queue Manager is responsible for functions not directly related to data movement such as storage, timing, triggering, and so on. Queue managers use a proprietary IBM technology known as a bindings connection to communicate with the MQ objects it manages and with remote clients via a network.

IBM MQ Receiver Channel (mqreceiverchannel)

Parent: IBM MQ Channel

  • Name

  • Container: IBM MQ Queue Manager

A receiving channel receives messages from remote Queue Managers through a sending channel with the same name.

IBM MQ Sender Channel (mqsenderchannel)

Parent: IBM MQ Channel

  • Name

  • Container: IBM MQ Queue Manager

A sending channel is associated with a specific Transmission queue within the same parent Queue Manager and has a well-defined destination.

IBMWebSphereMQ (webspheremq)

Parent: Message Queuing Software

  • Name: Always IBM WebSphere MQ

  • Container: Node

Represents an instance of WebSphere MQ software installed on a server.

IpAddress    
IpServiceEndpoint    
Membership    
Node    
Usage