OK, that takes some explaining. First, there's a new version of WAS available, WebSphere Application Server V7. Second, it contains a built-in JMS messaging provider that was first introduced in WAS 6, internally known as the service integration bus and what WAS calls "default messaging." Third, WAS can connect to WebSphere MQ as a JMS provider (see "Make WebSphere MQ the JMS provider for applications deployed in WebSphere Application Server").
The question has been how to set up WAS so that its apps can use both an SIBus and a set of WMQ queues (what we're now calling a WMQ network) without needing to know which queues where in which provider. No doubt, WAS could have two providers--an SIBus and a WMQ network--and apps could access queues in both. But ideally WAS apps should just use the SIBus and non-WAS apps should just use the WMQ network, and the bus and network should be grafted together somehow.
As of WAS 6, the grafting was accomplished using MQ Link. The two bus and network were still separate, but bridged via MQ link.
Now there is another option: Make a WMQ queue manager a member of an SIBus, essentially making the queue manager act like a messaging engine. Then, for the applications running in a WAS cluster that is a member of the bus, the queues in the queue manager act like queues in any other messaging engine--that is, they act like any other queues in the bus. While the SIBus in the WAS cluster and the WMQ queue manager are still separate, they're tied together as a single bus. This is a feature that was available in WAS 6, but only with WMQ 6 on z/OS. Now, with WAS 7 and WMQ 7 distributed (or WMQ 6 or later for z/OS), it works on all platforms.
For more info, see "Interoperating with a WebSphere MQ network," which outlines the three options:
- Connect WAS to WMQ as a JMS provider (works in WAS 6 and WESB 6)
- Connect an SIBus and WMQ network via MQ link (works in WAS 6 and WESB 6)
- Make a WMQ queue manager a member of an SIBus (new in WAS 7 for distributed platforms)
Why three approaches? Because none of them is always the best one. To learn the pros and cons, check out "Learning about interoperating with a WebSphere MQ network" and "Choose the most appropriate interoperation method for each of your messaging applications."
IBM's Graham Wallis also talks about these options in Connecting Buses.