Managing 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 a IBM MQ system, you can configure your messaging applications to use messaging resources provided by the default messaging provider.
Before you begin
For messaging between application servers, perhaps with some interaction with a IBM MQ system, you can use the default messaging provider as described in this topic. To integrate WebSphere Application Server messaging into a predominantly IBM MQ network, you can use the IBM MQ messaging provider. You can also use a third-party messaging provider. To choose the provider that is best suited to your needs, see Choosing a messaging provider.
About this task
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.
For more information about using the default messaging provider of WebSphere Application Server, see the following topics:
Procedure
- Default messaging
- Configuring resources for the default messaging provider
- Interoperating with an IBM MQ network
- Configuring the messaging engine selection process for JMS applications
- Managing messages and subscriptions for default messaging JMS destinations
- Using JMS from stand-alone clients to interoperate with service integration resources
- Using JMS from a third party application server to interoperate with service integration resources