Develop messaging resources
WAS supports asynchronous messaging based on the Java Message Service (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 IBM 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 IBM MQ messaging provider (which uses the IBM 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 Version 1.0.2 specification.
Subtopics
- Programming to use asynchronous messaging
We can build enterprise applications that use Java Message Service (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 IBM MQ, there are some environmental differences needed to take into account.
End-to-end paths for messaging resources Administer messaging resources Script for messaging resources Secure messaging resources Messaging resources Tune messaging resources Troubleshoot messaging resources