WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources

Manage 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 WebSphere MQ system, we can configure your messaging applications to use messaging resources provided by the default messaging provider.

For messaging between application servers, perhaps with some interaction with a WebSphere MQ system, we can use the default messaging provider as described in this topic. To integrate WAS messaging into a predominantly WebSphere MQ network, we can use the WebSphere MQ messaging provider. We can also use a third-party messaging provider. To choose the provider that is best suited to your needs, see Choose a messaging provider.

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.

We can use the dmgr 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 WAS, see the following topics:

• Default messaging
  
• Configure resources for the default messaging provider
  
• Interoperate with a WebSphere MQ network
  
• Configure the messaging engine selection process for JMS applications
  
• Manage messages and subscriptions for default messaging JMS destinations
  
• Use JMS from stand-alone clients to interoperate with service integration resources
  
• Use JMS from a third party application server to interoperate with service integration resources
  

Subtopics

• Configure resources for the default messaging provider
  Use the following tasks to configure JMS connection factories, activation specifications, and destinations for the default messaging provider.
• Interoperate with a WebSphere MQ network
  The default messaging provider (service integration) can interoperate with a WebSphere MQ network using a WebSphere MQ link or a WebSphere MQ server. Alternatively, we can use WebSphere MQ as your messaging provider. Each type of connectivity is designed for different situations, and provides different advantages. Choose the most appropriate interoperation method for each of your messaging applications.
• Configure the messaging engine selection process for JMS applications
  Configure the JMS connection factory for the application, in order to tune the process through which messaging engine connections are selected for the application.
• Manage messages and subscriptions for default messaging JMS destinations
  We can manage the messages and subscriptions that exist for JMS destinations of the default messaging provider. We can manage the messages on a JMS queue by acting on the queue point for the bus destination to which JMS queue has been assigned. We can administer the durable subscriptions on a JMS topic by acting on a publication point for the topic space to which JMS topic has been assigned.
• Use JMS from stand-alone clients to interoperate with service integration resources
  The Thin Client for JMS with WAS allows third party applications to interoperate with default messaging provider messaging engines on WAS.
• Use JMS from a third party application server to interoperate with service integration resources
  The Resource Adapter for JMS with WAS provides first class connectivity to service integration resources from the third party application server on which it is deployed.

Related

Choose a messaging provider

+

Search Tips   |   Advanced Search