+

Search Tips   |   Advanced Search

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 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 WAS console to configure JMS resources:


Subtopics


Related concepts

  • Messaging security
  • JMS connection factories and service integration
  • JNDI namespaces and connecting to different JMS provider environments


    Related information:

  • Service integration