Interoperation with WebSphere MQ

You can enable JMS interaction with a WebSphere® MQ network by using the WebSphere MQ messaging provider. Service integration can also provide interoperation through a WebSphere MQ link or a WebSphere MQ server. Each type of connectivity is designed for different situations, and provides different advantages.

New feature:

In this release, the relationship between the available JMS messaging providers is explored in some detail in Choosing a messaging provider and (for messaging environments that involve both WebSphere MQ and WebSphere Application Server) Choosing messaging providers for a mixed environment.

In this release, the WebSphere MQ messaging provider has enhanced administrative options supporting the following functions:
  • WebSphere MQ channel compression.
  • WebSphere MQ client channel definition table
  • Client channel exits
  • Transport-level encryption using SSL
  • Automatic selection of the WebSphere MQ transport type
For more information, see Enhanced features of the WebSphere MQ messaging provider.
In this release, several enhancements have been introduced to improve interoperation with WebSphere MQ server:
  • In addition to interoperating with WebSphere MQ for z/OS® Version 6, WebSphere MQ server can also be used with WebSphere MQ Version 7 running on any platform that is supported by WebSphere MQ.
  • Because some WebSphere MQ topologies have many thousands of queues defined to a queue manager, the wizards that automatically discover available WebSphere MQ queues (as part of Creating a queue-type destination and assigning it to a WebSphere MQ queue and Mediating a destination by using a WebSphere MQ queue as the mediation point) now include a filter to limit the range of queues that are listed.
  • In the previous release, the system assumes that the WebSphere MQ gateway queue manager views the local bus as a remote queue manager with the same name as the bus. In this release, a new Virtual queue manager name has been added to the WebSphere MQ server bus member configuration, giving you greater control over the name by which the WebSphere MQ gateway queue manager knows the bus.
  • JMS provider-specific properties have been added that allow service integration bus applications to access the WebSphere MQ-specific message attributes that are required for interoperation with some WebSphere MQ applications.

In this release, the procedure to create a new WebSphere MQ link is simplified. Instead of configuring each resource separately, you use the foreign bus connection wizard to connect a bus and a WebSphere MQ network. You configure the connection for either point-to-point messaging or publish-subscribe messaging. As part of this process, the WebSphere MQ link is created and configured.

Similarly, in this release you use a wizard to remove a foreign bus connection between a service integration bus and a WebSphere MQ network. As part of this process, the associated WebSphere MQ link is deleted, along with any publish/subscribe broker profiles and topic mappings.

newfeat

For more information about WebSphere MQ, see the WebSphere MQ library.




Subtopics
Comparison of WebSphere Application Server and WebSphere MQ messaging
Interoperation with WebSphere MQ: Comparison of architectures
Interoperation with WebSphere MQ: Comparison of key features
Interoperation with WebSphere MQ: Key WebSphere MQ concepts
WebSphere MQ messaging provider
How messages are passed between service integration and a WebSphere MQ network
Interoperation using a WebSphere MQ link
Interoperation using a WebSphere MQ server
Related concepts
Introduction: Messaging resources
Concept topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 5:30:17 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=cmm_interop
File name: cmm_interop.html