Messaging resources
WAS supports asynchronous messaging as a method of communication based on either...
- JMS
- Java Connector Architecture (JCA)
WAS also supports the use of message-driven beans as asynchronous message consumers.
The JMS and JCA programming interfaces provide a common way for Java programs (clients and J2EE applications) to...
- create
- send
- receive
- read
...asynchronous requests as messages. The application explicitly polls the destination for messages whereas a message-driven bean is invoked by the EJB container when a message arrives at a pre-configured destination.
To handle non-JMS requests inbound to WAS from enterprise information systems, message-driven beans use a JCA 1.5 resource adapter written for that purpose. In the JCA 1.5 specification, such message-driven beans are commonly called message endpoints or simply endpoints. You use a J2C activation specification to configure such message-driven beans as JCA 1.5 resources.
Message-driven beans that implement the...
javax.jms.MessageListener...interface can be used for JMS messaging.
For JMS messaging, message-driven beans can use a JCA-based messaging provider such as the default messaging provider that is part of WAS. You use a J2C activation specification to configure such message-driven beans as JCA 1.5 resources. For compatibility with WAS V5, you can configure JMS message-driven beans against a listener port.
You can use the console to administer the WAS support for asynchronous messaging. For example, you can configure JCA resource, adapters, J2C activation specifications, JMS providers, and JMS resources, and can control the activity of messaging services.
Tools for working with messaging include...
Rational Application Developer Developing and packaging J2EE applications that use JMS, message-driven beans, and other programming techniques for messaging. Assembly tools Working with the packaging and deployment descriptors for WAS applications, as described in Assembling applications Product system administration tools Installing and managing WAS applications, as described in Introduction: System administration
See also
- Learn about messaging with WebSphere
- Install a messaging provider
- Use the default messaging provider
- Maintain V5 default messaging resources
- Use JMS resources of WebSphere MQ
- Use JMS resources of a generic provider
- Administering listener ports and activation specifications for message-driven beans
- Programming to use asynchronous messaging
- Troubleshooting WebSphere messaging