Introduction: Messaging resources


 

+

Search Tips   |   Advanced Search

 

WAS supports asynchronous messaging based on JMS and JCA.

JMS support enables apps to exchange messages asynchronously with other JMS clients by using JMS destinations:

Some messaging providers allow apps to use JMS for exchanging messages asynchronously with non-JMS apps such as WebSphere MQ.

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:

To use messaging between apps in WAS, perhaps with some interaction with a WebSphere MQ system, choose the default messaging provider. To integrate WAS messaging apps into a predominately WebSphere MQ network, choose the WebSphere MQ messaging provider.

 

Related

Styles of messaging in apps
Types of messaging providers
Learning about default messaging
Interoperation with WebSphere MQ
Message-driven beans - automatic message retrieval
JMS interfaces - explicit polling for messages
JMS components on V5 nodes
Messaging: Links
Styles of messaging in apps
Types of messaging providers
Interoperation with WebSphere MQ
Message-driven beans - automatic message retrieval
JMS interfaces - explicit polling for messages
JMS components on V5 nodes
Messaging: Links
Use a JNDI namespace to connect to different JMS provider environments
Learn about default messaging
JMS interfaces
http://java.sun.com/products/jms/docs.html
WebSphere MQ library