Using JMS and messaging in applications
Use these tasks to implement WebSphere J2EE applications that use JMS.
WebSphere Application Server supports asynchronous messaging as a method of communication based on the Java Message Service 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.
Using 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.
One can use the WebSphere administrative console to administer the JMS support of WebSphere Application Server. For example, you can configure JMS providers and their resources, and can control the activity of the JMS server.
For more information about implementing WebSphere enterprise applications that use JMS, see the following topics:
- An overview of WebSphere asynchronous messaging using JMS
- Administering WebSphere JMS support
- Developing a J2EE application to use JMS
- Developing a JMS client
- Deploying a J2EE application to use JMS
- Resolving problems with WebSphere JMS
For more information about JMS, see the JMS documentation at
http://java.sun.com/products/jms/docs.html .
An overview of WebSphere asynchronous messaging using JMS
Using message-driven beans in applications
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.