JMS Section Index | Page 10
The act of serving, like beauty, is in the eye of the beholder. Any application that provides services to another application is a server. The JMS message broker provides both direct and indirec...more
There are two possible domains in JMS: (1) the publish/subscribe domain and (2) the point-to-point domain. Not all JMS implementations provide both domans. With the point-to-point domain, client...more
These terms are sometimes used interchangeably. Note, however, that, technically, a JMS implementations is any implementation of the JMS API. Thus, an arbitrary collection of application compone...more
JMS messages implement the Message interface. JMS messages include a header, properties, and the message body. Headers provide identifying and routing information. Properties allow arbitrary orn...more
Each JMS-enabled client must establish the following: A connection object provided by the JMS server (the message broker) Within a connection, one or more sessions, which provide a context for me...more
The term peer-to-peer is used in a variety of ways in distributed and network computing. One usage, at the application level, is to describe a distributed application scenario in with each distri...more
With publish/subscribe message passing the sending application/client establishes a named topic in the JMS broker/server and publishes messages to this queue. The receiving clients register (spec...more
With point-to-point message passing the sending application/client establishes a named message queue in the JMS broker/server and sends messages to this queue. The receiving client registers with...more
Does the specification require that all JMS implementations provide both point-to-point and publish/subscribe messaging?
No. Many JMS implementations provide both, but the specification defines compliance for each messaging style separately.
See the following introduction to Java Message Service.
The JMS site at Sun provides links to the specification, as well as the online javadocs for JMS. more
The JMS site at Sun is a good starting point. The vendors' page points to several sites and many of the vendors provide whitepapers and tutorials.
Is it possible to develop distributed applications with JMS alone? Is it necessary to have a Java application server, EJB server, and so on?
Yes. No. Minimally, a computing task can be distributed among two or more Java applications that interoperate by sending and receiving data via JMS. Thus, the minimal JMS-ready environment incl...more
What software do I need in order to add JMS message passing to my enterprise's existing distributed applications?
The "J" in JMS stands for Java, so the first prerequisite is a Java development and runtime environment. The second prerequisite is Java-based distributed applications, as opposed to C++/CORBA app...more
The answer depends on your point of view. From one point of view, nothing is missing. In terms of common distributed computing-related functionality, typically present in larger Java application...more