IBM WebSphere Application Server supports asynchronous messaging through
the use of the Java Message Service (JMS).
The default messaging provider enables enterprise applications deployed
on WebSphere Application Server to perform asynchronous messaging without
the need for you to install a JMS provider. The default messaging provider
is installed and runs as part of WebSphere Application Server.
The default messaging provider is based on service integration technologies.
You can use the WebSphere Application Server administrative console to configure JMS resources:
- JMS connection factories that applications use to connect
to a service integration bus.
- JMS queues that applications use to send messages to and
receive messages from. An application sends messages to a specific queue and
those messages are retrieved and processed by another application listening
to that queue. JMS queues are assigned to queue destinations on a service
integration bus. Such JMS queues are available, over a long period of time,
to all applications with access to the bus.
- JMS topics that applications can use as named
collection points for messages. To send messages, applications publish messages
to topics. To receive messages, applications subscribe to topics. JMS topics
are assigned to topic spaces on the bus. Such JMS topics are available, over
a long period of time, to all applications with access to the bus.