IBM WebSphere MQ

Mohammed Qasim

1
 IBM WebSphere MQ

IBM WebSphere MQ

 Its a network communication software, it allows

applications on distributed systems to
communicate with each other.
 A middleware product that implements messaging
and queuing framework.

2
 Messaging and Queuing

 Messaging : Programs communicate with each

other by sending data in messages.

 Queuing : Queuing means that the messages are

placed on queues in storage , so that programs
can run independently of each other at different
speeds and times

3
Asynchronous VS Synchronous Communication

Asynchronous :Application sends request and

checks at some time in future.

Synchronous : Application sends request then

blocks until the request is processed.

Messaging and Queuing framework in WebSphere MQ is

Asynchronous

4
 MQ Characteristics

 Programs communicate by putting messages on

queues.
 Communication can be one way or two way.
 Communicating programs can run at different
times.
 Message Queues exist independently from
programs that use them.

5
 MQ Characteristics
 There can be one to many or many to one relationship
between programs.

 Doesn’t matter what OS is being used.

 Doesn’t matter what language they are written in.

 Doesn’t matter what communication protocol is being

used.

6
 WebSphere MQ Objects

 Queues

 Queue Manager

 Channels

7
 Queues
 Application queues
This is a queue that is used by an application through the MQI.
It can be a local queue on the queue manager to which an application is
linked, or it can be a remote queue that is owned by another queue
manager.
 Initiation queues
Initiation queues are queues that are used in triggering.
 Transmission queues
Transmission queues are queues that temporarily stores messages that
are destined for a remote queue manager.

8
 Queues
 Cluster transmission queues. Each queue manager within a cluster has a
cluster transmission queue called SYSTEM.CLUSTER.TRANSMIT.QUEUE.
 Dead-letter queues.
A dead-letter queue is a queue that stores messages that cannot be routed to
their correct destinations.
 Command queues. The command queue, named
SYSTEM.ADMIN.COMMAND.QUEUE, is a local queue to which suitably
authorized applications can send WebSphere MQ commands for processing.
 Reply-to queues. When an application sends a request message, the
application that receives the message can send back a reply message
to the sending application. This message is put on a queue, called a
reply-to queue.

9
 Queue Manager
 A queue manager provides queuing services to applications, and
manages the queues that belong to it.

 Queue Manager controls access to the queues.

 Queue Managers have names which are unique just like host names.

 It is accessed through MQI (Message Queue Interface).

10
 Channels

 Channels are objects that provide a communication path from

one queue manager to another.

 They shield applications from the underlying communications

protocols.

 Channels are used in distributed message queuing to move

messages from one queue manager to another.

11
Queue Manager Operations
 crtmqm –q host1/mqm1
Creates a Queue Manager q1 on host1

 strmqm
Starts Queue Manager.

 dspmq
Lists all the Queue Manager.

 rummqsc
Starts Queue Manager scripting interface.

12
 Queue Manager Operations
 ./amqsput
Put messages onto queue

 ./amqbcg
Read messages from the queue and messages will not be removed
from queue.

 ./amqsget
Get messaes from the queue and messages will be removed from
queue.

13
14