+

Search Tips   |   Advanced Search

Manage messaging with 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. For messaging between application servers, perhaps with some interaction with an IBM MQ system, we can configure our messaging applications to use messaging resources provided by the default messaging provider.

To integrate WAS messaging into a predominantly IBM MQ network, we can use the IBM MQ messaging provider. We can also use a third-party messaging provider. To choose the provider that is best suited to our 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 administrative console to configure JMS resources for applications, and can manage messages and subscriptions associated with JMS destinations.


Tasks