MuleESB / IBM MQ Interview Questions

QueueManager is a primary component of WebSphere MQ or WMQ. QueueManager is responsible for storing and routing messages to other Queue Manager within MQ and it also communicates with the outside world, for example, Java program or any other MQ client.

In WebSphere MQ or WMQ, Queue Manager uses the channel to transmit messages to other QueueManager. Channel carries one-way traffic in MQ Series (i.e., channels are uni directional). You can have either sending channel or receiving channel in MQ.

Dead letter Queue in WebSphere MQ is a queue that is used by QueueManager to archive messages for a non-existent queue. For an example of QueueManager QMGR, receives a message for queue ABC and if it didn't exist on that QueueMangaer then the message will be routed to the dead letter queue.

MQ abbreviates Message Queuing. When it comes to message-driven processes, IBM enables users to simply keep up the pace with the WebSphere with which all application programs can simply be managed. There is no strict upper limit on the platforms when it comes to communicating and the good thing is vast support is available from IBM to enable the users to manage everything simply.

A lot of messages arrive in the queue and especially when there is a lot of traffic. When such a thing happens, an automatic process that relates to the triggering starts. It is possible to stop the application with a simple instruction after it has done its work.

In WebSphere MQ, local queues are queue on the same queue manager while remote queue refers to queues on different QueueManager.

MQSC commands enable you to perform administration tasks, for example defining, altering, or deleting a local queue object.

• Integration,
Asynchrony, Assured Delivery, Scalability.

With message queuing, the exchange of messages between the sending and receiving programs are independent of time. This means that the sending and receiving application programs are decoupled; the sender can continue processing without having to wait for the receiver to acknowledge receipt of the message. The target application does not even have to be running when the message is sent. It can retrieve the message after it has been started.

• Request messages, a message sent for which a response/reply is expected.
• Reply messages, a response Message for a requested message.
• Report messages, a Message that describes the occurrence or event.
• Datagram messages, a message sent with no response expected.

A message is a string of bytes that is meaningful to the applications that use it. Messages are used to transfer information from one application program to another (or between different parts of the same application). The applications can be running on the same platform, or on different platforms.

WebSphere MQ messages have two parts:

• The application data, the content and structure of the application data are defined by the application programs that use it.
• A message descriptor, message descriptor identifies the message and contains additional control information, such as the type of message and the priority assigned to the message by the sending application. WebSphere MQ defines the format of the message descriptor. For a complete description of the message descriptor.

• Queue Manager,
• Queues,
• Channels,
• Processes,
• Name lists.

1414.

Infrared360 is a lightweight yet very powerful MQ monitor giving you ALL of the features for monitoring your MQ environment-including the MQ Appliance.

• Provides Proactive MQ Monitoring.
• Leverage Internal Integrations.
• Associate Alerts to Lines of Business.