| Related resources |
|
| How do I?... |
|
| Overview |
|
| Tutorials |
|
| Samples |
This page provides a starting point for finding information about messaging resources. JMS support enables applications to exchange messages asynchronously with other JMS clients by using JMS destinations (queues or topics).
Applications can use message-driven beans to automatically retrieve messages from JMS destinations and JCA endpoints without explicitly polling for messages.
For inbound non-JMS requests, message-driven beans use a Java Connector Architecture (JCA) 1.5 resource adapter written for that purpose. For JMS messaging, message-driven beans can use a JCA-based messaging provider such as the default messaging provider that is part of WebSphere Application Server.
The messaging engine supports the following types of message providers: default messaging provider (service integration bus); using WebSphere MQ provider as an external messaging provider; or another "generic" messaging provider as long as it implements the ASF component of the JMS 1.0.2 specification. More introduction...
Searchable topic ID: welc6tech_msg