Network Deployment (Distributed operating systems), v8.0 > End-to-end paths
End-to-end paths for Messaging resources
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 by 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 WAS 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 Version 1.5 resource adapter or the ASF component of the JMS v1.0.2 specification.
- 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.
Messaging resources
Migrate Messaging resources
Administer Messaging resources
Scripting for Messaging resources
Secure Messaging resources
Develop Messaging resources
Tune Messaging resources
Troubleshoot Messaging resources