WAS v8.5 > Develop applicationsDevelop 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 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
- Programming to use asynchronous messaging
We can build enterprise applications that use JMS APIs directly to provide asynchronous messaging services. We can also use message-driven beans as asynchronous message consumers. If we are writing messaging programs that interoperate between WAS and WebSphere MQ, there are some environmental differences needed to take into account.
Related information:
End-to-end paths for Messaging resources
Administer Messaging resources
Scripting for Messaging resources
Secure Messaging resources
Messaging resources
Tune Messaging resources
Troubleshooting Messaging resources