WebSphere MQ Tutorials
Welcome to the WebSphere MQ Tutorials. The intent of these tutorials is to provide in depth understanding of WebSphere MQ software. In addition to WebSphere MQ Tutorials, you can find interview questions, how to tutorials and issues and their resolutions of WebSphere MQ Product.
What is WebSphere MQ?
This document contains step by step technical information to learn MQ series, by using this one can start working with control and WebSphere MQ script commands through the Windows Explorer and UNIX/AIX Command line interface.
MQSeries runs on a variety of platforms. The MQSeries products enable programs to Communicate with each other across a network of unlike components, such as processors, subsystems, operating systems and communication protocols. MQSeries programs use a consistent application program interface (API) across all platforms.
MQSeries can be configured to provide assured delivery of the messages. Assured delivery means that even if the hardware or software platform crashes the messages within the system will still be delivered, once the platforms are brought back up. On a typical target system MQSeries consists of a queue manager and a number of queues and channels.
Message in MQ
An WebSphere MQ Series message is simply a collection of data sent by one program and intended for another program. The message consists of control information and application specific data. The control information is required in order to route the message between the programs to some extent. A message can be classed as persistent or non- persistent. A persistent message will survive a software or hardware crash / reboot, once communicated to a queue manager, whereas a non-persistent message will not survive. Persistent messages are used as part of the implementation of the assured delivery service supported by MQSeries.
MQ Queue Manager
It is the queue manager that provides the queuing services to the application programs. A queue manager in MQ Series also provides additional functions so that administrators can create new queues, alter the properties of existing queues and control the operation of the queue manager. Many applications can make use of the queue manager’s facilities at the same time, and they can be completely unrelated. It is possible to connect queue managers on different platforms together, this is achieved via a mechanism called channels.
Websphere Message Queues
Queues are named message repositories upon which messages accumulate until they are retrieved by programs that service those queues. WebSphere MQ Queues reside in, and are managed by, a queue manager. Programs access queues via the services provided by the queue manager. They can open a queue, put messages on it, get messages from it, and close the queue. It is also possible to programmatically set, and inquire about, the attributes of queues. Queues are either defined as local or remote. Local queues allow programs to both put messages on, and get messages off, while remote queues only allow programs to put messages on. Remote queues are used in order to provide put access to queues that are local to another platform. Any message put onto a remote queue is automatically routed to the associated platform and local queue by the queue manager via the channels mechanism.
Channels are named links between platforms across which messages are transmitted. On the source platform the channel would be defined as a sender and on the destination platform as a receiver. It is the sender channel definition that contains the connectivity information, such as the destination platform’s name or IP address. MQ Series Channels must have the same name on both the source and destination platform.
For Indepth understanding of WebSphere MQ Tutorials