WAS v8.5 > Administer applications and their environmentAdminister Messaging resources
The use of asynchronous messaging resources for enterprise applications with WebSphere Application Server.
WAS supports asynchronous messaging based on the JMS and the Java EE Connector Architecture (JCA) specifications, which provide a common way for Java programs (clients and Java EE applications) to create, send, receive, and read asynchronous requests, as messages.
JMS support enables applications to exchange messages asynchronously with other JMS clients using JMS destinations (queues or topics). Some messaging providers also allow WAS applications to use JMS support to exchange messages asynchronously with non-JMS applications; for example, WAS applications often need to exchange messages with WebSphere MQ applications. Applications can explicitly poll for messages from JMS destinations, or they can use message-driven beans to automatically retrieve messages from JMS destinations without explicitly polling for messages.
WAS supports 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).
- Third-party messaging providers that implement either a JCA v1.5 resource adapter or the ASF component of the JMS v1.0.2 specification.
Subtopics
- Manage messaging with the default messaging provider
The default messaging provider is installed and runs as part of WAS, 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.- Manage messaging with the WebSphere MQ messaging provider
Through the WebSphere MQ messaging provider in WAS, JMS messaging applications can use your WebSphere MQ system as an external provider of JMS messaging resources. To enable this approach, you configure the WebSphere MQ messaging provider in WAS to define JMS resources for connecting to any queue manager on the WebSphere MQ network.- Manage messaging with a third-party messaging provider
For messaging between application servers, 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). You might want to do this, for example, if we have existing investments.- Manage message-driven beans
We can manage the Java EE Connector Architecture (JCA) v1.5-compliant message-driven beans deployed as message endpoints, and we can manage the message listener resources for non-JCA message-driven beans deployed against listener ports.
Related information:
End-to-end paths for Messaging resources
Messaging resources
Scripting for Messaging resources
Secure Messaging resources
Develop Messaging resources
Tune Messaging resources
Troubleshooting Messaging resources