WAS v8.5 > WebSphere applications > Messaging resourcesDefault messaging
Use these topics to learn about using the default messaging provider to support the use of the JMS by enterprise applications deployed on WebSphere Application Server.
The default messaging provider is installed and runs as part of WAS.
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.
The default messaging provider is based on service integration technologies. We can use the dmgr console to configure JMS resources:
- 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
Subtopics
- JCA activation specifications and service integration
A JCA 1.5 activation specification enables a message-driven bean to communicate with the default messaging provider.- JMS connection factories and service integration
A JMS connection factory is used to create connections to JMS resources on a service integration bus.- JMS queue resources and service integration
JMS queue resources (queues and queue connection factories) are provided by the default messaging provider for JMS point-to-point messaging and supported by a service integration bus.- JMS topic resources and service integration
JMS topic resources (topics, topic spaces, connection factories, durable subscriptions) are provided by the default messaging provider for JMS publish/subscribe messaging, and supported by a service integration bus.- The createQueue or createTopic method and the default messaging provider
We can use the Session.createQueue(String) method or Session.createTopic(String) method instead of using JNDI lookup to create a JMS Queue or JMS Topic with the default messaging provider.- How JMS applications connect to a messaging engine on a bus
There are several factors that affect how JMS applications connect to a service integration bus, so they can use resources provided by the bus.
Related concepts:
Messaging security
JMS connection factories and service integration
JNDI namespaces and connecting to different JMS provider environments
Related information:
Service integration