The Ibm®websphere®application Server V7 contains important improvements that improve its interoperability with IBM WebSphere MQ, which serves as the Java™message Service (JMS) provider.
Introduction
Many organizations use IBM WebSphere MQ to deliver enterprise messaging and deploy their Java Platform, Enterprise Edition (Java EE) applications using IBM WebSphere application Server 。 When you use the WebSphere MQ messaging provider support that was originally introduced in V5 in WebSphere application Server, you can deploy Java EE applications to take advantage of the enterprise messaging capabilities of WebSphere MQ directly. This article outlines the new WebSphere MQ messaging provider and related enhancements added to the WebSphere application Server V7.
This article assumes that you have a basic understanding of WebSphere application Server and WebSphere MQ and the Java message Service (JMS) APIs.
What is a WebSphere MQ message delivery provider?
Java EE applications that use the WebSphere MQ messaging provider (the "MQ messaging provider") are messaging through the JMS APIs, while WebSphere MQ supports wide selection of other programming APIs and environments. This means that Java EE applications can use MQ messaging providers to communicate with the following applications: CICS applications, back-end applications running on z/os®, and other existing applications written in various languages, with only a few examples (Figure 1).
Figure 1. Using WebSphere MQ to communicate between different systems
With an MQ messaging provider, a Java EE application that uses local or global transactions can use WebSphere MQ as a transaction resource. For example, you can asynchronously notify the purchase of a management application: the "Fill in Account" message from WebSphere MQ has arrived. In response to the message, the application may update the inventory database and, if the customer has insufficient credit, send another WebSphere MQ message to the commodity-pricing application (Figure 2).
Figure 2. Example of using global transactions