Learning about messaging with WAS
Use this topic to learn about the use of asynchronous messaging for enterprise applications with WAS.
Overview
WAS supports asynchronous messaging as a method of communication based on the JMS and Java Connector Architecture (JCA) programming interfaces. These interfaces provide a common way for Java programs (clients and J2EE applications) to create, send, receive, and read asynchronous requests, as messages. For additional information about messaging resources, see: Messaging resources.
Procedure
- JMS provider support
- Styles of messaging in applications
- JMS interfaces - explicit polling for messages
- Message-driven beans - automatic message retrieval
- Configure JMS resources for the WebSphere MQ messaging provider
- Message-driven beans - JCA components
- WAS cloning and WebSphere MQ clustering
- Asynchronous messaging - security considerations
JMS provider support
Styles of messaging in applications
JMS interfaces - explicit polling for messages
Message-driven beans - automatic message retrieval
WAS cloning and WebSphere MQ clustering
Asynchronous messaging - security considerations
Messaging: Resources for learning
Related concepts
Using a JNDI namespace to connect to different JMS provider environments
Related tasks
Learning about the default messaging provider
Related Reference
JMS interfaces
Related information
http://java.sun.com/products/jms/docs.html