IBM WEBSPHERE MESSAGE QUEUE

IBM MESSAGE QUEUE:

 Message Queue: Message queue is a middleware product that can communicate or integrate two applications by sending or receiving the data.

Message: A message is a representation of data or information exchanged between the applications.

·         Binary information

·         Text data

·         Structured data

What message contain:

·         MQ Message Description

·         Body of the Message or Message body

MQ Message Description: In message description there are different values

·         Expire date and time        

·         Message ID

·         correlation ID

·         Group ID

·         Sequence Number

·         Put date and Time

·         Application name

·         QManager name

·         Queues name

Message body: Message body can contains the data or information for the application.

METHODS OF MESSAGING:

   Two types of messaging methods are there. Those are

·         Synchronous messaging

·         Asynchronous messaging

Synchronous messaging: The sender can send a message and wait for the acknowledgement from the receiver.

Asynchronous messaging: The sender can send a message continuously without waiting for the acknowledgement from the receiver.   

TYPES OF MESSAGES:

There are four types of messages

·         Data gram

·         Request

·         Reply

·         Report

Data gram: A message cannot expect response is called data gram message.

Request message: A message that can expect a response is called request message.

Reply message: A message in response to a request message is called reply message.

Report message: Report message is  a message that tells about an occurrence or an event is called 

report message.

APPLICATION PERSPECTIVE MESSAGE TYPES:

Those are two types

·         Persistent message

·         Non Persistent message

Persistent message: A message that can recoverable when failure occurs.

Non Persistent message: A message that cannot recoverable when failure occurs.

WHAT ARE THE METHODS BY USING APPLICATION TO CONNECT MQ:

Application can connect to the MQ

1.      Binding mode

2.      External mode

Binding mode: Application and MQ should be on same server.

External mode: Application and MQ on different servers.

WHAT ARE THE MQI CALLS:

  MQI calls: Application can use MQI calls to connect to the MQ Qmanager.These are divided into two categories.

1.      Major calls

2.      minor calls

Major calls:

1.      MQCONN and MQCONNX: TO connect to the Queue Manager.

2.      MQOPEN :It is using for open a queue.

3.      MQCLOSE: It is using for to close a queue.

4.      MQDISC : It is using to end the connection to the Queue Manager.      

5.      MQPUT : It is using to put a message on a queue.

6.      MQPUT1 : it means The combination of MQOPEN , MQPUT and MQCLOSE.

7.      MQGET: To get a message from the Queue.

Minor calls:

1.      MQBEGIN: To begin a unit of work.

2.      MQCMIT: To commit a unit of work.

3.      MQSET: Can be used by application to set the some of the attribute on the queue.

4.      MQBACK: To rollback the commands for unit of work.

5.      MQINQ: To Inquire about attributes of an object.

DIFFERENCES BETWEEN MQ VERSION8 AND MQ VERSION 9.

MQ Version 8

1.       new feature introduced in v8 is apiexits  which themselves make apicalls.

2.      On unix and linux systems the object authority manager (OAM) can now use userbased authorization as well as group based authorization.

3.      In IBM V8 a new Queue Manager security parameter conauth chcklocl has been introduced.

MQ Version 9

1.      A new delivary and suport model for IBMMQ has been introduced.

From version 9 two release types will be made available

                       1. long term support release(lTS)

                      2.Continues delivery Release.

     2. In v9 WEB UI has been introduced to administer MQ.