Tune 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
- Tune messaging
To tune asynchronous messaging, we can, for example, configure message-driven bean (MDB) throttling for a JCA 1.5-compliant messaging provider. (ZOS) On z/OS platforms we can tune also MDB processing and tune destinations for the IBM MQ messaging provider.
End-to-end paths for messaging resources Administer messaging resources Script for messaging resources Secure messaging resources Developing messaging resources Messaging resources Troubleshoot messaging resources