Manage messaging with a third-party or (deprecated) V5 default messaging provider
For messaging between appservers, most requirements are best met by either the default messaging provider or the WebSphere MQ messaging provider. However, we can instead use a third-party messaging provider (that is, use another company's product as the provider). For backwards compatibility with earlier releases, there is also support for the V5 default messaging provider.
If not sure which provider combination is best suited to the needs, see Types of messaging providers.
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.
The choice of provider depends on what the JMS application needs to do, and on other factors relating to the business environment and planned changes to that environment.
- Choose a third-party messaging provider.
You can configure any third-party messaging provider that supports the JMS V1.1 unified connection factory. We might want to do this, for example, because of existing investments.
To administer a third-party messaging provider, you use the resource adaptor or client supplied by the third party. We can still use the WAS admin console to administer the JMS connection factories and destinations that are within WAS, but we cannot use the admin 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 messaging provider.
- Choose the (deprecated) V5 default messaging provider.
This deprecated provider is identical to the WAS V5 default provider. Only the name has changed. It provides backwards compatibility that enables WAS V6 or later applications to connect to WAS V5 resources in a mixed cell. It also allows WAS V5 applications to connect to WAS Version 6 or later resources in a mixed cell. To configure and manage messaging to interoperate with WAS V5, see Maintain (deprecated) V5 default messaging resources.
Manage messaging with a third-party messaging provider
Maintain (deprecated) V5 default messaging resources
Related concepts
Introduction: Messaging resources
Related tasks
Manage messaging with the WebSphere MQ messaging provider
Administer activation specifications and listener ports for message-driven beans
Secure messaging
Tuning messaging
Troubleshooting messaging
Programming to use asynchronous messaging
Manage messaging with the default messaging provider
Related information
Choose a messaging provider