Default messaging provider
The default messaging provider is installed and runs as part of WebSphere Application Server, and is based on service integration technologies. For messaging between application servers, perhaps with some interaction with a WebSphere MQ system, you can configure your messaging applications to use messaging resources provided by the default messaging provider.
The default messaging provider supports JMS 1.1 domain-independent interfaces (sometimes referred to as "unified" or "common" interfaces). This enables applications to use 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.1 Java. EE applications can use messaging resources of the default messaging provider in later versions. This JMS interoperation from WebSphere Application Server Version 5.1 to later versions is enabled and managed by a WebSphere MQ client link created on the node in the later version. This JMS interoperation is only intended as an aid to the migration from the embedded messaging in WebSphere Application Server Version 5.1 to the default messaging provider in the later version.
Java EE applications running under the later version can use messaging resources of Version 5 embedded messaging without any need for a WebSphere MQ client link.
- Listing JMS resources for the default messaging provider
- Configuring a unified connection factory for the default messaging provider
- Administrative properties for JMS connections to a bus
- Configuring a queue connection factory for the default messaging provider
- Configuring a topic connection factory for the default messaging provider
- Configuring a queue for the default messaging provider
- Configuring a topic for the default messaging provider
- Configuring an activation specification for the default messaging provider