WebSphere JMS support - components
Overview
WebSphere Application Server supports asynchronous messaging based on the Java Messaging Service of a JMS provider that conforms to the JMS specification version 1.0.2 and supports the Application Server Facility (ASF) function defined within that specification. WAS provides an embedded JMS provider and administration objects for MQ as the JMS provider. One can use the embedded JMS provider, install MQ JMS on top of the embedded WebSphere JMS, or install and configure another JMS provider.
JMS functions (of JMS providers) within the WAS administration domain are served by one or more JMS servers. There can be at most one JMS server on each node in the administration domain, and any appserver within the domain can access JMS resources served by any JMS server on any node in the domain.
A connection factory is used to create connections with the JMS provider for a specific JMS queue or topic destination. Each connection factory encapsulates the configuration parameters needed to create a connection to a JMS destination.
A WebSphere J2EE application can explicitly poll for messages on a destination then retrieve messages for processing by business logic beans (enterprise beans).
The WAS support for message-driven beans and extended messaging builds on this base JMS support. For more information, see the related topics.
Message-driven beans - components
An overview of WebSphere asynchronous messaging using JMS
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.