IBM WebSphere MQ (MQ Series) is middleware for messaging and queuing. It uses the Message Queue Interface (MQI) to communicate with Message Queue Managers (MQMs) which manage queues and messages. MQ Series supports persistent and non-persistent messages up to 100 MB in size that can be segmented, grouped, sent to distribution lists, and assigned types like datagram, request, reply, or report. MQMs transfer messages between queues using channels and coordinate updates using two-phase commit.
The document provides an overview of the fundamentals of Websphere MQ including:
- The key MQ objects like messages, queues, channels and how they work
- Basic MQ administration tasks like defining, displaying, altering and deleting MQ objects using MQSC commands
- Hands-on exercises are included to demonstrate programming with MQ and administering MQ objects
This document provides an overview of WebSphere MQ Administration training notes. It discusses key concepts in message-oriented middleware including messaging, queuing, MQSeries, and the Message Queue Interface. It also describes common MQ objects like queue managers, queues, channels, and messages. The document outlines how applications use MQ calls to connect to queue managers and put and get messages from queues.
This document outlines a 16-session training course on IBM WebSphere MQ. The sessions cover MQ architecture, messaging concepts, objects like queues and channels, distributed queue management, triggering, commands, dead letter queues, utilities, installation, configuration files, clusters, multi-instance usage, and protocols. Hands-on exercises are included to demonstrate topics like one-way and two-way communication, triggering, dead letter queue processing, and how clusters work.
IBM WebSphere MQ is a messaging middleware that allows applications located anywhere to securely communicate with each other by sending and receiving messages. It uses queues to facilitate reliable communication between systems. There are two types of messages - persistent messages that are assured exactly one delivery and non-persistent messages that can be lost.
The MQ infrastructure consists of queue managers that maintain queues and messages. Queues store messages until they are retrieved. Channels connect queue managers and automatically route messages. Listeners act as mediators for external applications and queue managers to contact queue managers. Control commands like runmqsc and crtmqm are used to create and manage queue managers, queues, channels and listeners.
The document provides an overview of IBM WebSphere MQ (MQ), formerly known as MQSeries. MQ is a message-oriented middleware that provides reliable messaging across platforms. It allows for asynchronous communication through message queues and supports transactions. The core component is the Queue Manager, which controls access to queues and provides administration services.
IBM MQ (formerly known as MQSeries) is a middleware messaging product that allows applications on different platforms to communicate asynchronously by sending and receiving messages. It guarantees message delivery and supports advanced features like triggering actions on message receipt. MQ provides a common API for applications to connect to message queues, publish/consume messages, and ensures delivery across heterogeneous systems. It is widely used to integrate legacy mainframe systems with modern platforms.
The document discusses IBM's MQ infrastructure including MQ 7.1, MQ AMS, and MQ FTE. It provides an agenda covering universal connectivity with MQ, MQ File Transfer Edition, MQ security with MQ AMS, and features of MQ 7.1 including security policies. The document is presented by AJ Aronoff from Prolifics and focuses on MQ infrastructure for security and high availability.
Where is My Message?: Use MQ Tools to Work Out What Applications Have DoneMorag Hughson
Every MQ infrastructure team member has been asked this question, and most developers who have worked with MQ have asked it: "Where is my message?" In this session, we look into the tools that MQ provides to find your messages. We show how to analyze the MQ recovery log on distributed platforms to find out what happened to your persistent messages, with the assistance of a new tool. We also look at how to trace the route messages take through your MQ infrastructure, and how to generate and analyze activity reports showing the behavior of MQ applications.
The document provides an overview of the fundamentals of Websphere MQ including:
- The key MQ objects like messages, queues, channels and how they work
- Basic MQ administration tasks like defining, displaying, altering and deleting MQ objects using MQSC commands
- Hands-on exercises are included to demonstrate programming with MQ and administering MQ objects
This document provides an overview of WebSphere MQ Administration training notes. It discusses key concepts in message-oriented middleware including messaging, queuing, MQSeries, and the Message Queue Interface. It also describes common MQ objects like queue managers, queues, channels, and messages. The document outlines how applications use MQ calls to connect to queue managers and put and get messages from queues.
This document outlines a 16-session training course on IBM WebSphere MQ. The sessions cover MQ architecture, messaging concepts, objects like queues and channels, distributed queue management, triggering, commands, dead letter queues, utilities, installation, configuration files, clusters, multi-instance usage, and protocols. Hands-on exercises are included to demonstrate topics like one-way and two-way communication, triggering, dead letter queue processing, and how clusters work.
IBM WebSphere MQ is a messaging middleware that allows applications located anywhere to securely communicate with each other by sending and receiving messages. It uses queues to facilitate reliable communication between systems. There are two types of messages - persistent messages that are assured exactly one delivery and non-persistent messages that can be lost.
The MQ infrastructure consists of queue managers that maintain queues and messages. Queues store messages until they are retrieved. Channels connect queue managers and automatically route messages. Listeners act as mediators for external applications and queue managers to contact queue managers. Control commands like runmqsc and crtmqm are used to create and manage queue managers, queues, channels and listeners.
The document provides an overview of IBM WebSphere MQ (MQ), formerly known as MQSeries. MQ is a message-oriented middleware that provides reliable messaging across platforms. It allows for asynchronous communication through message queues and supports transactions. The core component is the Queue Manager, which controls access to queues and provides administration services.
IBM MQ (formerly known as MQSeries) is a middleware messaging product that allows applications on different platforms to communicate asynchronously by sending and receiving messages. It guarantees message delivery and supports advanced features like triggering actions on message receipt. MQ provides a common API for applications to connect to message queues, publish/consume messages, and ensures delivery across heterogeneous systems. It is widely used to integrate legacy mainframe systems with modern platforms.
The document discusses IBM's MQ infrastructure including MQ 7.1, MQ AMS, and MQ FTE. It provides an agenda covering universal connectivity with MQ, MQ File Transfer Edition, MQ security with MQ AMS, and features of MQ 7.1 including security policies. The document is presented by AJ Aronoff from Prolifics and focuses on MQ infrastructure for security and high availability.
Where is My Message?: Use MQ Tools to Work Out What Applications Have DoneMorag Hughson
Every MQ infrastructure team member has been asked this question, and most developers who have worked with MQ have asked it: "Where is my message?" In this session, we look into the tools that MQ provides to find your messages. We show how to analyze the MQ recovery log on distributed platforms to find out what happened to your persistent messages, with the assistance of a new tool. We also look at how to trace the route messages take through your MQ infrastructure, and how to generate and analyze activity reports showing the behavior of MQ applications.
HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...Matt Leming
Every MQ infrastructure team member has been asked this question, and most developers who have worked with MQ have asked it:
"Where is my message?" In this session, we look into the tools that MQ provides to find your messages.
We demonstrate how to analyze the MQ recovery log on distributed platforms to find out what happened to your persistent messages,
with the assistance of a new tool. We also look at how to trace the route messages take through your MQ infrastructure, and how to generate
and analyze activity reports showing the behavior of MQ applications.
WebSphere MQ is a middleware tool that facilitates reliable application-to-application communication by sending and receiving messages via messaging queues. It provides a secure transport layer that moves data unchanged in the form of messages between applications across platforms. WebSphere MQ uses APIs to support programming languages like Java, C, COBOL. It differentiates between persistent and non-persistent messages to ensure reliable delivery. The queue manager maintains objects like queues, channels, and listens to ensure message flow.
This session is aimed to bring you up to date with the latest additions and enhancements to the IBM Messaging family of products. This session describes the latest product announcements in-cluding V8, and is intended to introduce many of the other sessions this week.
WebSphere MQ V7 extends the MQ API (Application Programming
Interface) in a number of ways. In this presentation we will cover the new
API changes, excluding Publish/Subscribe:-
* Asynchronous Consumption of messages
* Asynchronous Put Response
* Read-ahead of messages
* Connection changes
* Message Properties + Selectors
* Simplified Browse + Co-operative Browse
IBM MQ (formerly known as MQSeries) is middleware that implements message queuing using queues to allow programs to communicate asynchronously. It runs on many platforms and supports transactional message passing between programs. Key objects in MQ include queue managers, queues, channels, and messages. Messages are placed on queues and can be retrieved later, even if the sending program has ended. MQ uses logging and recovery to ensure reliable message delivery even if failures occur. It provides benefits like loose coupling between applications, assured delivery through persistence, and ability to integrate with transactional systems.
Channel authentication records allow setting rules to control inbound connections to a queue manager. Rules can allow, block, or assign user IDs to connections. Attributes like IP address, hostname, SSL certificate, and user ID can be used to define rules. Obtaining hostnames requires reverse DNS lookup, which can be disabled. Rules can be restricted based on IP/hostname and certificate subject and issuer can be checked.
HHM-3481: IBM MQ for z/OS: Enhancing Application and Messaging Connectivity ...Matt Leming
Today's business environment is driving re-engineering of business systems using new techniques and architectures. This session will elaborate on the new environments MQ for z/OS is enabling for Java JMS applications, and enhanced interconnectivity capabilities that put MQ for z/OS at the vital heart of a hybrid messaging world.
Overview of Microsoft Message Queueing (MSMQ) messaging technology.
MSMQ is Microsoft's message queueing technology that also integrates well into the newer Windows Communication Foundation framework.
MSMQ provides most of the features and functionality typical of message queueing systems.
IBM MQ systems route billions of messages around the world each day. This presentation looks at the tools available in MQ for z/OS to allow you to understand where your messages are flowing, and things you can use if the messages aren't going where you expect.
IBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ ClustersDavid Ware
IBM WebSphere MQ Clustering can be used to solve many problems, from simplified administration and workload management in an MQ network, to horizontal scalability and continuous availability of messaging applications. This session will show the full range of uses of MQ Clusters to solve real problems, highlighting the underlying technology being used.
This has been superseded by http://www.slideshare.net/DavidWare1/ame-2273-mq-clustering-pdf
Message Queuing (MSMQ) technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline.
A review of new features in IBM's premier messaging product.
After a short look at 2013 updates, it gives an overview of all features of the V8 release. Other presentations go into deeper details on some of these features, but this gives the essential flavour for it all.
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Studies have shown that meditating for just 10-20 minutes per day can have significant positive impacts on both mental and physical health over time.
IBM MQ - Monitoring and Managing Hybrid Messaging EnvironmentsMarkTaylorIBM
This presentation was given at Interconnect 2016. It starts by showing the interfaces within MQ for management and monitoring, and then shows how these are used within a cloud environment to control the delivery of a service-based messaging system.
WebSphere MQ CHLAUTH - including V8 changesMorag Hughson
This document discusses IBM MQ CHLAUTH rules and how they were updated in MQ V8. CHLAUTH rules allow you to define which inbound connections are allowed or blocked based on attributes like IP address, hostname, SSL certificate details, client user ID, and remote queue manager name. The document provides examples of CHLAUTH rule configuration and discusses how hostnames are obtained and how rules can be restricted based on IP address/hostname. It also notes that fully qualifying rules with the issuer's DN in addition to the subject's DN is recommended to avoid clashes when multiple CAs are trusted.
Compares REST APIs and MQ. Then describes the capabilities of MQ's new built in REST messaging API. Finally covers MQ's support for z/OS Connect EE which is an alternative way of accessing MQ using REST.
WebSphere MQ is a middleware tool that facilitates application-to-application communication by sending and receiving messages via messaging queues. It provides a secure and reliable transport layer for moving data in the form of messages between applications across platforms. WebSphere MQ uses APIs that support programming languages like Java, C, COBOL, and Visual Basic. It differentiates between persistent and non-persistent messages, with persistent messages assured delivery even after system failures. WebSphere MQ manages objects like queues, channels, and listeners that applications use to communicate with each other via messaging.
Hhm 3479 mq clustering and shared queues for high availabilityPete Siddall
we review clustering and shared queue technologies, their differences and synergies, as a foundation for building a highly available messaging service with resilience during both planned and unplanned outages of z Systems components.
HHM-2833: Where is My Message?: Using IBM MQ Tools to Work Out What Applicati...Matt Leming
Every MQ infrastructure team member has been asked this question, and most developers who have worked with MQ have asked it:
"Where is my message?" In this session, we look into the tools that MQ provides to find your messages.
We demonstrate how to analyze the MQ recovery log on distributed platforms to find out what happened to your persistent messages,
with the assistance of a new tool. We also look at how to trace the route messages take through your MQ infrastructure, and how to generate
and analyze activity reports showing the behavior of MQ applications.
WebSphere MQ is a middleware tool that facilitates reliable application-to-application communication by sending and receiving messages via messaging queues. It provides a secure transport layer that moves data unchanged in the form of messages between applications across platforms. WebSphere MQ uses APIs to support programming languages like Java, C, COBOL. It differentiates between persistent and non-persistent messages to ensure reliable delivery. The queue manager maintains objects like queues, channels, and listens to ensure message flow.
This session is aimed to bring you up to date with the latest additions and enhancements to the IBM Messaging family of products. This session describes the latest product announcements in-cluding V8, and is intended to introduce many of the other sessions this week.
WebSphere MQ V7 extends the MQ API (Application Programming
Interface) in a number of ways. In this presentation we will cover the new
API changes, excluding Publish/Subscribe:-
* Asynchronous Consumption of messages
* Asynchronous Put Response
* Read-ahead of messages
* Connection changes
* Message Properties + Selectors
* Simplified Browse + Co-operative Browse
IBM MQ (formerly known as MQSeries) is middleware that implements message queuing using queues to allow programs to communicate asynchronously. It runs on many platforms and supports transactional message passing between programs. Key objects in MQ include queue managers, queues, channels, and messages. Messages are placed on queues and can be retrieved later, even if the sending program has ended. MQ uses logging and recovery to ensure reliable message delivery even if failures occur. It provides benefits like loose coupling between applications, assured delivery through persistence, and ability to integrate with transactional systems.
Channel authentication records allow setting rules to control inbound connections to a queue manager. Rules can allow, block, or assign user IDs to connections. Attributes like IP address, hostname, SSL certificate, and user ID can be used to define rules. Obtaining hostnames requires reverse DNS lookup, which can be disabled. Rules can be restricted based on IP/hostname and certificate subject and issuer can be checked.
HHM-3481: IBM MQ for z/OS: Enhancing Application and Messaging Connectivity ...Matt Leming
Today's business environment is driving re-engineering of business systems using new techniques and architectures. This session will elaborate on the new environments MQ for z/OS is enabling for Java JMS applications, and enhanced interconnectivity capabilities that put MQ for z/OS at the vital heart of a hybrid messaging world.
Overview of Microsoft Message Queueing (MSMQ) messaging technology.
MSMQ is Microsoft's message queueing technology that also integrates well into the newer Windows Communication Foundation framework.
MSMQ provides most of the features and functionality typical of message queueing systems.
IBM MQ systems route billions of messages around the world each day. This presentation looks at the tools available in MQ for z/OS to allow you to understand where your messages are flowing, and things you can use if the messages aren't going where you expect.
IBM WebSphere MQ: Managing Workloads, Scaling and Availability with MQ ClustersDavid Ware
IBM WebSphere MQ Clustering can be used to solve many problems, from simplified administration and workload management in an MQ network, to horizontal scalability and continuous availability of messaging applications. This session will show the full range of uses of MQ Clusters to solve real problems, highlighting the underlying technology being used.
This has been superseded by http://www.slideshare.net/DavidWare1/ame-2273-mq-clustering-pdf
Message Queuing (MSMQ) technology enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline.
A review of new features in IBM's premier messaging product.
After a short look at 2013 updates, it gives an overview of all features of the V8 release. Other presentations go into deeper details on some of these features, but this gives the essential flavour for it all.
The document discusses the benefits of meditation for reducing stress and anxiety. Regular meditation practice can help calm the mind and body by lowering heart rate and blood pressure. Studies have shown that meditating for just 10-20 minutes per day can have significant positive impacts on both mental and physical health over time.
IBM MQ - Monitoring and Managing Hybrid Messaging EnvironmentsMarkTaylorIBM
This presentation was given at Interconnect 2016. It starts by showing the interfaces within MQ for management and monitoring, and then shows how these are used within a cloud environment to control the delivery of a service-based messaging system.
WebSphere MQ CHLAUTH - including V8 changesMorag Hughson
This document discusses IBM MQ CHLAUTH rules and how they were updated in MQ V8. CHLAUTH rules allow you to define which inbound connections are allowed or blocked based on attributes like IP address, hostname, SSL certificate details, client user ID, and remote queue manager name. The document provides examples of CHLAUTH rule configuration and discusses how hostnames are obtained and how rules can be restricted based on IP address/hostname. It also notes that fully qualifying rules with the issuer's DN in addition to the subject's DN is recommended to avoid clashes when multiple CAs are trusted.
Compares REST APIs and MQ. Then describes the capabilities of MQ's new built in REST messaging API. Finally covers MQ's support for z/OS Connect EE which is an alternative way of accessing MQ using REST.
WebSphere MQ is a middleware tool that facilitates application-to-application communication by sending and receiving messages via messaging queues. It provides a secure and reliable transport layer for moving data in the form of messages between applications across platforms. WebSphere MQ uses APIs that support programming languages like Java, C, COBOL, and Visual Basic. It differentiates between persistent and non-persistent messages, with persistent messages assured delivery even after system failures. WebSphere MQ manages objects like queues, channels, and listeners that applications use to communicate with each other via messaging.
Hhm 3479 mq clustering and shared queues for high availabilityPete Siddall
we review clustering and shared queue technologies, their differences and synergies, as a foundation for building a highly available messaging service with resilience during both planned and unplanned outages of z Systems components.
RabbitMQ is an open-source message broker software that defines message queues to facilitate communication and data transfer between applications. It uses AMQP as the communication protocol and supports multiple programming languages. Messages are routed to queues based on bindings and routing keys. Channels provide sandboxing within a single connection. RabbitMQ offers features like retries, dead-letter queues, priorities, and persistence to ensure reliable message delivery. It uses a push model and does not use a database to store messages.
This document summarizes IBM MQ basics including messaging, queuing, asynchronous and synchronous messaging, message segmentation, message types, persistent vs non-persistent messages, message descriptors, MQ managers, queues, process definitions, channels, and more. Key points are that MQ uses queuing to enable program-to-program communication by sending and receiving messages without a direct connection. Messages have data and descriptor parts, and can be persistent or non-persistent. MQ managers connect applications to queues using channels and provide message queuing interfaces.
Srihitha Technologies provides WebSphere MQ Admin Training in Ameerpet by real time Experts. For more information about WebSphere MQ Admin training in Ameerpet call 9394799566 / 9290641808.
RabbitMQ is an open source message broker that implements the AMQP protocol. It provides various messaging patterns using different exchange types and supports clustering for scalability and high availability. Administration of RabbitMQ includes managing queues, exchanges, bindings and other components. Integrations exist for protocols like STOMP, MQTT and frameworks like Spring, while security features include authentication, authorization, and SSL/TLS encryption.
IBM MQ: Managing Workloads, Scaling and Availability with MQ ClustersDavid Ware
MQ Clustering can be used to solve many problems, from simplified administration and workload management in an MQ network, to horizontal scalability and continuous availability of messaging applications. This session will show the full range of uses of MQ Clusters to solve real problems, highlighting the underlying technology being used. A basic understanding of IBM MQ clustering would be beneficial.
M Bhupal has over 4 years of experience working with IBM WebSphere MQ. He has expertise installing, configuring, upgrading, and maintaining WebSphere MQ across Windows and Linux environments. Some of his responsibilities include resolving incident tickets, enabling fix packs, creating and modifying MQ objects using MQSC commands, configuring high availability clusters, and troubleshooting issues. He has worked as a WebSphere MQ System Analyst for TCS and as a WebSphere MQ Admin for Infosys on projects for clients like United Indian and Societe Generale.
Switching and multicast schemes in asynchronous transfer mode networksEditor Jacotech
This document summarizes various switching and multicast schemes used in asynchronous transfer mode (ATM) networks. It discusses shared memory ATM switching architectures and different approaches for supporting multicast traffic in shared memory switches including replication-at-receiving, replication-at-sending, multiple write multiple read, and single write single read schemes. It also covers requirements for ATM multicast and compares these schemes in terms of advantages and disadvantages related to memory usage and switching performance.
WebSphere MQ uses message queuing to allow application programs to pass messages between systems and across platforms. It defines several key objects including queues, queue managers, and channels that interact to route messages. Messages are placed on queues and then retrieved based on priorities and queues can be local or remote depending on which queue manager they belong to. The document provides an overview of these core WebSphere MQ concepts and components.
3450 - Writing and optimising applications for performance in a hybrid messag...Timothy McCormick
Messaging architectures in any environment, from local standalone deployments through to public clouds, must provide the highest reliability yet maximize their performance. This session gives you an insight into IBM MQ and how applications can be made to perform to their absolute best while maintaining the data integrity that IBM MQ is renowned for. We'll see how this can be achieved through a combination of good application design, system tuning and architectural patterns.
This document provides an overview of Spring RabbitMQ. It discusses messaging basics and RabbitMQ concepts like exchanges, queues, bindings. It then summarizes the Spring AMQP and Spring Integration frameworks for integrating RabbitMQ in Spring applications. Spring AMQP provides the RabbitAdmin, listener container and RabbitTemplate for declaring and interacting with RabbitMQ components. The document contains code examples for configuring RabbitMQ and consuming/producing messages using Spring AMQP.
This document discusses message queues (MQ), including key elements like publishers, brokers, and consumers. It defines MQ as a system that allows processes to communicate asynchronously via data exchange. Some benefits of MQ are non-blocking code, parallel execution, easy scaling, and resilience. However, integrating MQ can be challenging due to issues like concurrency bugs, testing difficulties, and increased operational complexity.
This document provides an overview and agenda for a presentation on OpenStack networking. It begins with an overview of OpenStack architecture and services like Compute, Networking, Identity and Image services. It then discusses basic network components like controllers, compute nodes and networking plugins. Next, it covers networking process flows and dives deeper into the Neutron networking plugin, including the Modular Layer 2 plugin framework and drivers like Open vSwitch. It concludes with a planned demonstration of networking functionality in an OpenStack lab environment.
This document discusses RabbitMQ, an open source message broker implementation of the Advanced Message Queuing Protocol (AMQP). It provides an overview of AMQP and its key mechanisms including message encoding, flow control, queuing, reliability, and security. RabbitMQ is implemented in Erlang and supports client APIs in several languages including Java. The document describes how to install RabbitMQ, connect to it from a Java client, declare exchanges and queues, publish and receive messages, and use request-response patterns. It also covers message properties, acknowledgements, and reliability concepts in RabbitMQ.
Come join us at the Online Meetup to learn more about MQ Integrations and Circuit Breakers. Help us spread the knowledge of Mule!
A brief agenda:
> Networking and Knowledge sharing.
> MuleSoft Latest Product Release Updates.
> Anypoint Messaging Queue in MuleSoft
> MQ Integrations with Circuit Breaker in MuleSoft
> Demo
> Finally, we will wrap-up this event with the agenda for the next meetup.
Stay connected to get updates on what's new in MuleSoft.
The document introduces EMQ X, an open-source distributed MQTT broker designed for large-scale IoT deployments. EMQ X aims to sustain millions of MQTT connections through a distributed and highly extensible architecture. It provides features such as clustering, authentication, access control, message persistence, bridging, and a plugin system to customize functionality. The document also covers installing, configuring, and optimizing EMQ X.
Internet companies with huge traffic and millions of users have tasks involved that cannot be served in a request. RabbitMQ can process tasks or communication between different app components asynchronously but close to real time.
This document discusses IBM MQ clustering and how it provides availability, scalability, and workload balancing. It describes how to set up a basic two node cluster with full repository queue managers and cluster receiver and sender channels. It then discusses more advanced clustering capabilities like supporting multiple applications and global deployments spanning different regions.
1. IBM WebSphere MQ (MQ Series) in a Nutshell
(Prepared by Channu Kambalyal)
Introduction
• MQ Series is a Middleware for Commercial Messaging and Queuing
• MQ Series API – also called Message Queue Interface (MQI) used to communicate with
a Message Queue Manager (MQM), the runtime program of MQSeries.
• MQI consists of 13 calls.
Messages
• Consists of 2 parts: Message Descriptor and Message Data
• Message descriptor identifies message id and contains control information such as
message type, expiry time, correlation ID, priority, reply queue name.
• MQ Series Version 5 supports maximum message length of 100 MB
• Messages can be segmented or grouped. If permitted queue manager segments a large
message when it does not fit in a queue. Application has the option to receive entire
message in piece or each segment separately. Application can also control the logical
boundaries or buffer size of the segment of a message. Queue Manager ensures that the
order of the segment is maintained.
• Several small messages can be grouped to build one larger physical message.
• Using a Distribution List, you can send a message to more than one destination.
Distribution List is a file contains a list of queue names and queue managers that own
them. Receiving Queue Manager replicates the messages and puts them into destination
queues (This function is called late fan-out).
• MQ Series knows 4 types of massages: Datagram (unsolicited message), Request (a
message for which response is expected), Reply and Report (an event such as
occurrence of an error or confirmation on arrival or delivery)
• MQ Series messages can be persistent and non-persistent.
• Message Descriptor contains: Version, Message ID/Correlation ID, Persistent/ Non-
Persistent, Priority, Date &m Time, Lifetime of a message, Return Address, Format,
Sender Application and Type, Report options/ Feedback (COA, COD), Back out counter,
Segmenting/ Grouping Information.
Queue Manager (MQM)
• Manages queues and messages for applications
• Transfers messages to other Queue Managers via channels using existing network
facilities.
• It refers to objects that are defined by the administrator.
• Coordinates updates to databases and queues using two-phase commit.
• Gets and puts from/to queues are committed together with SQL updates, or backed out if
necessary.
• Segments messages, if necessary, and assembles them.
• Can group messages and send them as one physical message to their destination,
where they are automatically disassembled.
• Can send one message to more than one destination using a user-defined dynamic
destination list.
• Allow administrators to create and delete queues, alter properties of existing queues,
control the operation of queue manager.
• MQ Series for Windows NT version 5.1 provides GUI to administer.
• MQ Series for Windows (different from NT) is a single-user queue manager and is not
intended to function as a queue manager for other MQ Series clients.
Page 1 of 4
2. Queue Manager Clusters
• MQSeries for MVS/ESA and Version 5.1 for distributed platforms, provides clustering
features
• Queue Managers that form a cluster can run in the same machine or in different
machines on different platforms.
• Two of Queue Managers maintain a repository that contains information about all queue
managers and queues in the cluster (full repository). Other Queue Managers maintain
only a repository of the objects they are interested in (partial repository).
• Queue Managers use special cluster channels to exchange information.
• Client application may specify a queue manager and direct the message to a specific
queue in a cluster or it may let a queue manager to determine where the queue is and to
which one to send the message.
• Client uses a Transmission Queue on its machine and destination queue is called “Target
Queue”.
• Administrator must define the name of the cluster, when a queue is defined.
• MQSeries distributes the messages round robin.
Queue Manager Objects
• A Queue Manager uses 3 types of objects, namely, Queues, Process Definitions and
Channels.
• Queues are used to store messages.
• Process Definition object defines an application to a queue manager. It contains a name
of a program (and its path) to be triggered when a message arrives for it.
• Channel is a communication link. There are 2 kinds of channels, namely, Message
Channels and MQI channels.
• Message Channel connects 2 queue managers via Message Channel Agents (MCA).
Message Channel is unidirectional.
• MCA is a program (also called mover) that transfers messages from a transmission
queue to a communication link and from communication link to a target queue.
• MQI channel connects MQSeries client to a queue manager and is bi-directional.
• Message Channel can run at 2 speeds: fast and normal. Fast Channels improve
performance but messages can be lost in case of channel failure.
Message Queues
• Message Queues belong to Queue Manager.
• Types of Messages Queues are:
o Local Queue – is a real queue!
o Cluster Queue – is a local queue that is known throughout a cluster of queue
managers.
o Remote Queue – structure describing a queue hosted by a different queue
manager.
o Transmission Queue – a local queue used for messages to be sent to a remote
queue.
o Initiation Queue – local queue with a special purpose
o Dynamic Queue – local queue created on the fly
o Alias Queue - - if you do not like the queue name
o Dead-Letter Queue – one for each queue manager
o Reply-to Queue – specified in request message
o Model Queue – model for local queues
o Repository Queue – hold cluster information
• Create a queue manager using the command: crtmqm. Example:
o Crtmqm /q /u system.dead.letter.queue MYQMGR
• To start a queue manager issue command: strmqm
Page 2 of 4
3. Manipulating Queue manager Objects
• Use the utility RUNMQSC to manipulate queue manager objects. Ensure queue manager
is started prior using the runmqsc utility. Example:
C:strmqm
runmqsc
define qlocal(‘QUEUE1’) replace descry (‘test queue’)
alter qmgr deadq(system.dead.letter.queue)
end
How MQSeries Works
Following diagram depicts how MQSeries works:
Figure: How MQSeries Works
Program 1 Program 2 Starts
MQM A MQM B
MQPUT
Channel Initiator Listener
Trigger Monitor
(Must be running) (Must be running)
(Must be running)
Monitors (Default port 1414)
Remote Q Starts MQGET
Starts
Monitors
MQSeries Channel MQSeries Channel
Agent Agent
Ch Init Q (MCA) (MCA) System
Init Q
Moves Moves
Xmit Q Network Local Q
MQM A - Detect message destined for MCA - Moves messages to a local Q and to
remote Q moves it to xmit Q and a Ch init Q System Init Q
Communication between Queue managers
How to Trigger Applications
Message Queuing Interface
MQCONN Connect to a Queue Manager
MQDISC Disconnect from a Queue Manager
MQOPEN Open a specific queue
MQCLOSE Close a queue
MQPUT Put message on a queue
MQPUT1 Get message from a queue
MQGET MQOPEN + MQPUT + MQCLOSE
MQINQ Inquire properties of an object
Page 3 of 4
4. MQSET Set properties of an object
MQCONNX Standard or fast path bindings
MQBEGIN Begin a unit of work (database coordination)
MQCMIT Commit a unit of work
MQBACK Back out
Page 4 of 4