Network Deployment (Distributed operating systems), v8.0 > End-to-end paths > Messaging resources

Choosing a messaging provider

For messaging between application servers, perhaps with some interaction with a WebSphere MQ system, you can use the default messaging provider.

To integrate WAS messaging into a predominantly WebSphere MQ network, you 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, consider what the application needs to do, and the business need for the provider to integrate well with your enterprise infrastructure.

Enterprise applications in WAS can use asynchronous messaging through services based on JMS messaging providers and their related messaging systems. These messaging providers conform to the JMS v1.1 specification.

We can configure any of the following messaging providers:

• The default messaging provider (which uses service integration as the provider)
• The WebSphere MQ messaging provider (which uses your WebSphere MQ system as the provider)
• A third-party messaging provider (which uses another company's product as the provider)

The types of messaging providers that can be configured in WAS are not mutually exclusive:

• All types of provider can be configured within one cell.
• Different applications can use the same, or different, providers.
• One application can access multiple providers.

No one of these providers is necessarily better than another. The choice of provider depends on what your JMS application needs to do, and on other factors relating to your business environment and planned changes to that environment.

For backwards compatibility with earlier releases, WAS also includes support for the "V5 default messaging provider". See Maintain (deprecated) v5 default messaging resources.

Procedure

1. Determine the environment and application requirements.

   If we have to use a third-party messaging provider, or interoperate with WAS v5 resources, use the associated provider. See Manage messaging with a third-party or (deprecated) V5 default messaging provider.

   If your existing or planned messaging environment involves both WebSphere MQ and WAS systems, and it is not clear to you whether you should use the default messaging provider, the WebSphere MQ provider, or a mixture of the two, complete the task Choosing messaging providers for a mixed environment.

2. Choose the messaging provider:

   • Choose the default messaging provider.

     If you mainly want to use messaging between applications in WAS, perhaps with some interaction with a WebSphere MQ system, the default messaging provider is the natural choice because this provider is fully integrated with the WAS runtime environment. See Default messaging provider. To configure and manage messaging with the default messaging provider, see Manage messaging with the default messaging provider.

   • Choose the WebSphere MQ messaging provider.

     If your business also uses WebSphere MQ, and you want to integrate WAS messaging applications into a predominantly WebSphere MQ network, the WebSphere MQ messaging provider allows you to define resources for connecting directly to the queues in a WebSphere MQ system. See WebSphere MQ messaging provider.

     To configure and manage messaging with the WebSphere MQ messaging provider, see Manage messaging with the WebSphere MQ messaging provider.

   • Choose a third-party messaging provider.

     We can use any third-party messaging provider that supports the JMS v1.1 unified connection factory. You might want to do this, for example, because of existing investments.

     Notes:

     • To administer a third-party messaging provider, use the resource adaptor or client supplied by the third party. We can still use the console to administer the JMS connection factories and destinations that are within WAS, but you cannot use the administrative console to administer the JMS provider itself, or any of its resources that are outside of WAS.

     • To use message-driven beans (MDBs), third-party messaging providers must include Application Server Facility (ASF), an optional feature that is part of the JMS v1.1 specification, or use an inbound resource adapter that conforms to the Java EE Connector Architecture (JCA) v1.5 specification.

     To work with a third-party provider, see Manage messaging with a third-party JCA 1.5-compliant messaging provider or Manage messaging with a third-party non-JCA messaging provider.

Related

Choosing messaging providers for a mixed environment
Introduction: Messaging resources
Manage messaging with the WebSphere MQ messaging provider
Manage messaging with a third-party or (deprecated) V5 default messaging provider
Manage message-driven beans
Secure messaging
Tune messaging
Troubleshoot messaging
Program to use asynchronous messaging
Manage messaging with the default messaging provider
Configure JMS resources for the synchronous SOAP over JMS endpoint listener

+

Search Tips   |   Advanced Search