Administer JMS resources

 

Overview

A JMS provider enables asynchronous messaging based on the Java Message Service (JMS). Application components can use JMS to communicate with each other. JMS provides two messaging models:

• Point-to-point

  In this one-to-one messaging model, message producers called senders and message consumers called receivers communicate through virtual channels called queues. Each message has one sender and one recipient. JMS point-to-point uses queue connection factories and queue resources to communicate with the embedded JMS provider.

• Publish/subscribe

  In this one-to-many messaging model, message producers called publishers and message consumers called subscribers communicate through virtual channels called topics. One message producer submits a message to a topic, and all of the message consumers that are subscribed to that topic can receive the message. JMS publish/subscribe uses topic connection factories and topic resources to communicate with the embedded JMS provider.

Message-driven beans (MDBs) use JMS message listeners. These listeners are associated with a queue connection factory and a queue or with a topic connection factory and a topic, depending on the JMS messaging model that the listener uses. You must configure the message listener service before you install MDB application components.

 

See also

• Message-driven beans in applications
• Use Java Messaging Service to transport Web services requests
• Migrate JMS applications
• Troubleshoot: JMS Message Service
• Administer generic JMS providers
• Administer resources for the embedded WebSphere JMS provider
• Administer resources for the WebSphere MQ JMS provider