Java Message Service (JMS) is an API that enables the publishing and
subscribing of messages between one or more clients and a message broker, and
consists of the following elements:
JMS provider: a proprietary Java JMS implementation or an adapter to
a non-Java Message Oriented Middleware (MOM), such as Apache ActiveMQ, 29West,
JBoss, and TIBCO EMS.
JMS client: an application or process that creates and sends and/or
receives messages
JMS producer or publisher: a JMS client that creates and sends
messages to a JMS provider
JMS consumer or subscriber: a JMS client that receives messages from
a JMS provider. The client can specify message selectors, which allows a
consumer or subscriber to filter the messages to receive.
JMS message: an object that contains the data being delivered between
a JMS producer/publisher and a JMS consumer/subscriber
JMS topic: a mechanism for distributing and publishing messages to
multiple JMS consumers/subscribers
JMS queue: a staging area that contains messages that have been sent
but not yet received by the JMS consumer/subscriber
JMS messages can be transferred between a producer/publisher and a
consumer/subscriber in two ways. A JMS producer/publisher sends a message to a
destination in the JMS provider. This destination can be either a JMS queue or a
JMS topic. If the destination is a queue, only the consumer/subscriber at that
destination can receive the message. If the destination is a topic, any
subscriber actively subscribing to the topic receives the message.
For more information about JMS, see the JMS
Specification.
Kaazing WebSocket Gateway - JMS Edition uses the JMS API to extend the
functionality of JMS providers, such as Apache ActiveMQ, 29West, JBoss, and
TIBCO EMS.
The Gateway:
Enables the distribution of JMS messages across massive number of JMS
clients—more than a message broker could support on its own
Enables clients to seamlessly communicate with back-end JMS-compliant
message brokers across the Web, and through firewalls and proxies
Enables a variety of clients on different platforms to access the same
message broker
The Gateway includes JMS client libraries you can use to build a client for
your application to enable communication between your application and a
JMS-compliant message broker. The following figure shows an overview of how the
communication works:
Figure: An overview of how JMS client libraries enable
communication between your application and a JMS-compliant message
broker
If you are interested in using the WebSocket API, see Kaazing WebSocket
Gateway - HTML5 Edition.
No comments:
Post a Comment