This page provides a starting point for finding information about the use of asynchronous messaging resources for enterprise applications with WebSphere® Application Server.
WebSphere® Application Server supports asynchronous messaging based on the JavaTM Message Service (JMS) and the Java EE Connector Architecture (JCA) specifications, which provide a common way for Java programs (clients and Java EE applications) to create, send, receive, and read asynchronous requests, as messages.
JMS support enables applications to exchange messages asynchronously with other JMS clients by using JMS destinations (queues or topics). Some messaging providers also allow WebSphere Application Server applications to use JMS support to exchange messages asynchronously with non-JMS applications; for example, WebSphere Application Server applications often need to exchange messages with WebSphere MQ applications. Applications can explicitly poll for messages from JMS destinations, or they can use message-driven beans to automatically retrieve messages from JMS destinations without explicitly polling for messages.
WebSphere Application Server supports the following messaging providers:
More introduction...
This set of topics describes the migration of JMS applications from the embedded messaging in WebSphere Application Server Version 5.1 to the default messaging provider in later versions.
There are certain limitations and restrictions to bear in mind when deciding whether to use a JMS client developed for WebSphere Application Server Version 5.1 with a later version of the product.
Normally the WebSphere MQ resource adapter is automatically updated when you apply a WebSphere Application Server fix pack. However, when you migrate profiles from maintenance level 7.0.0.0 to later maintenance levels, or from later maintenance levels to the 7.0.0.0 maintenance level, you must manually adjust the resource adapter configuration.