Compatibility

An MQe network can exist independently of MQ, but in many situations the two products together are needed to meet the application requirements. MQe can integrate into an existing MQ network with compatibility including the aspects summarized below:

Addressing and naming:
  • Identical addressing semantics using a queue manager or queue address
  • Common use of an ASCII name space
Applications:
  • MQe is able to support existing MQ applications without application change.
Connections:
  • The MQe gateway uses MQ client channels.
Message interchange and content:
  • Interchange of messages between MQe and MQ
  • Message network invisibility (messages from either MQe or MQ can cross the other network without change)
  • Mutual support for identified fields in the MQ message header
  • Once and once-only assured message delivery
MQe does not support all the functions of MQ. Apart from environmental, operating system and communication considerations, these are some of the more significant differences:
  • No clustering support
  • No distribution list support
  • No grouped or segmented messages
  • No load balancing or warm standby capabilities
  • No reference message
  • No report options
  • No shared queue support
  • No triggering
  • No unit of work support, no XA-coordination
  • Different scalability and performance characteristics
However, within MQe many application tasks can be achieved through alternative means using MQe features, or through the exploitation of subclassing, the replacement of the supplied classes, or the exploitation of the rules, interfaces, and other customization features built into the product.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.