Default messaging
Use these topics to learn about using the default messaging provider to support the use of the Java™ Message Service (JMS) by enterprise applications deployed on WebSphere® Application Server.
The default messaging provider is installed and runs as part of WebSphere Application Server.
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
as described in section 1.5 of the JMS 1.1 specification.
- A JCA activation specification to enable a message-driven bean to communicate with the default messaging provider.
- A JMS connection factory to connect to a service integration bus
- A JMS queue or topic assigned to a bus destination on the bus. Such JMS queues and topics are available, over a long period of time, to all applications with access to the bus destination.
- JCA activation specifications and service integration
- JMS connection factories and service integration
- JMS queue resources and service integration
- JMS topic resources and service integration
- The createQueue or createTopic method and the default messaging provider
- How JMS applications connect to a messaging engine on a bus