Programming to use JMS and messaging directly
Use these tasks to implement WebSphere J2EE applications that use JMS programming interfaces directly.
Overview
WAS supports asynchronous messaging as a method of communication based on the JMS programming interface.
The base JMS support enables WebSphere enterprise applications to exchange messages asynchronously with other JMS clients by using JMS destinations (queues or topics). An enterprise application can explicitly poll for messages on a destination.
Use the base support for JMS, you can build enterprise beans that use the JMS API directly to provide messaging services along with methods that implement business logic.
You can use the WebSphere administrative console to administer the JMS support of WAS. For example, you can configure JMS providers and their resources, and can control the activity of the JMS server.
For more information about JMS, see the JMS documentation at http://java.sun.com/products/jms/docs.html.
Procedure
- Designing an enterprise application to use JMS
- Developing a J2EE application to use JMS
- Developing a JMS client
- Deploying a J2EE application to use JMS
Designing an enterprise application to use JMS
Developing a J2EE application to use JMS
Developing a JMS client
Deploying a J2EE application to use JMS