Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources


Manage messaging with the default messaging provider


Overview

The default messaging provider supports JMS 1.1 domain-independent interfaces (sometimes referred to as "unified" or "common" interfaces), enabling 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.

We can use the WAS administrative console to configure JMS resources for applications, and can manage messages and subscriptions associated with JMS destinations.

WAS v5.1 Java EE applications can use messaging resources of the default messaging provider in later versions. This JMS interoperation from WAS v5.1 to later versions is enabled and managed by a WebSphere MQ client link created on the node in the later version. This JMS interoperation is only intended as an aid to the migration from the embedded messaging in WAS v5.1 to the default messaging provider in the later version.

Java EE applications running under the later version can use messaging resources of v5 embedded messaging without any need for a WebSphere MQ client link.


See

  1. Default messaging
  2. Configure resources for the default messaging provider
  3. Interoperating with a WebSphere MQ network
  4. Migrate from WAS v5 embedded messaging
  5. Enable WAS v5.1 JMS usage of messaging resources in later versions of the product
  6. Configure the messaging engine selection process for JMS applications
  7. Manage messages and subscriptions for default messaging JMS destinations
  8. Use JMS from stand-alone clients to interoperate with service integration resources
  9. Use JMS from a third party application server to interoperate with service integration resources
  10. Default messaging


See

  1. Implementing a queue manager alias and cluster with WebSphere MQ

+

Search Tips   |   Advanced Search