Manage messaging with the default messaging provider

The default messaging provider is installed and runs as part of WAS, and is based on service integration technologies. For messaging between application servers, perhaps with some interaction with a WebSphere MQ system, you can configure the messaging applications to use messaging resources provided by the default messaging provider.

For messaging between appservers, perhaps with some interaction with a WebSphere MQ system, you can use the default messaging provider as described in this topic. To integrate WAS messaging into a predominantly WebSphere MQ network, you can use the WebSphere MQ messaging provider. You can also use a third-party messaging provider. To choose the provider that is best suited to the needs, see Choose a 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.

Use the WAS admin console to configure JMS resources for applications, and can manage messages and subscriptions associated with JMS destinations.

WAS V5.1 Java. EE applications can use messaging resources of the default messaging provider in later versions. This JMS interoperation from WAS V5.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 WAS V5.1 to the default messaging provider in the later version.

Java EE applications running under the later version can use messaging resources of V5 embedded messaging without any need for a WebSphere MQ client link.

See about using the default messaging provider of WAS, see the following topics:

 

See