WebSphere Message Brokers
File: ae27000_
Writer: Bill Oppenheimer

Concept topic

This build: July 31, 2007 21:28:51

Overview of message serialization on z/OS

Some messaging transactions depend upon the exact sequence of messages from a queue, and for that sequence to be maintained in the event of a failure of the queue manager. In these instances you must serialize the access to those messages.

Serialization of messages is achieved through the use of specialized connection options, and a unique connection token when the application that empties the messages from a queue issues a connect call to the WebSphere MQ queue manager that owns that queue.

A typical situation in which WebSphere Message Broker can exploit this feature is the case where multiple brokers, with multiple execution groups, are each running message flows that empty from a shared input queue. If one broker queue manager fails, then the message flow can be automatically started on another broker while maintaining the transactional integrity and original sequencing of the messages on the shared queue.

The following examples demonstrate how these features can be applied:
  1. Serialization of input between separate brokers on z/OS
  2. Serialization of input between separate execution groups running on the same broker on z/OS
  3. Serialization of input within an execution group on z/OS
Note the following:
Related concepts
z/OS customization overview
Serialization of input between separate brokers on z/OS
Serialization of input between separate execution groups running on the same broker on z/OS
Serialization of input within an execution group on z/OS
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:28:51

ae27000_ This topic's URL is: