This topic is the entry-point into a set of topics about enabling WebSphere® Application Server applications to use messaging resources provided by the default messaging provider.
The default messaging provider is installed and runs as part of WebSphere Application Server, and is based on service integration technologies.
The default messaging provider supports JMS 1.1 domain-independent interfaces (sometimes referred to as "unified" or "common" interfaces). This enables applications to use the same, common, interfaces for both point-to-point and publish/subscribe messaging. This also enables both point-to-point and publish/subscribe messaging within the same transaction. With JMS 1.1, this approach is recommended for new applications. The domain-specific interfaces are supported for backwards compatibility for applications developed to use domain-specific queue interfaces, as described in section 1.5 of the JMS 1.1 specification.
You can use the WebSphere Application Server administrative console to configure JMS resources for applications and can manage messages and subscriptions associated with JMS destinations.
WebSphere Application Server Version 5 J2EE applications can use messaging resources of the WebSphere Application Server Version 6 default messaging provider. This JMS interoperation from WebSphere Application Server Version 5 to Version 6 is enabled and managed by a WebSphere MQ client link created on the WebSphere Application Server Version 6 node. This JMS interoperation is only intended as an aid to the migration from the embedded messaging in WebSphere Application Server Version 5 to the default messaging provider in WebSphere Application Server Version 6.
For more information about using the default messaging provider of WebSphere Application Server, see the following topics:
In this information ...Subtopics
Related tasks
| IBM Redbooks, demos, education, and more(Index) |