This concludes the discussion of interoperability with IBM WebSphere MQ and JMS. In this chapter, we've examined the IBM product, looked at the default libraries that are available for Java, and seen how a recent SupportPac can be used to help provide connection for .NET clients .
The chapter introduced JMS and then presented some of the complexities of sharing a WebSphere MQ queue with both a JMS client and a .NET client. Continuing with the publish/subscribe features of JMS, the chapter examined a sample MDB (or Message Driven Bean), how that bean could subscribe to a JMS topic, and how it could call a .NET Web service based upon the operations of the bean. The chapter concluded by looking at the JMS support available with GLUE and a brief introduction to the MA0R SupportPac.
The goal of this chapter and Chapter 8 was to concentrate on direct access to each of the queuing products (MSMQ and WebSphere MQ) and examine the alternatives and options that exist for both platforms. In Chapter 10 and Chapter 11 ("Asynchronous Interoperability, Part 3: Bridging with Host Integration Server" and "Asynchronous Interoperability, Part 4: BizTalk Server"), we'll implement a bridge between the two queues by using both Microsoft Host Integration Server 2000 and Microsoft BizTalk Server 2004 Beta 1, and you'll see what each product can offer. In Chapter 11, our discussion of asynchronous interoperability will conclude by relating the contents of all four chapters on the topic back to the resource tier goals outlined in Chapter 2, "Business Requirements for Interoperability."