Getting Started with WebSphere Application Server
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 6 – Messaging 111<br />
3. Messages - These are objects that are used to communicate information between<br />
JMS clients.<br />
4. Administered objects - These are preconfigured JMS objects that are created by<br />
an administrator of the JMS provider for the use of JMS clients. In Community<br />
Edition, these are called the JMS resource group.<br />
- Destination - A destination encapsulates addressing information for a specific<br />
JMS provider. A JMS client uses a destination object to address a message to<br />
a specific destination on the underlying JMS provider.<br />
- ConnectionFactory - A connection factory encapsulates the configuration<br />
information that is required to connect to a specific JMS provider. A JMS client<br />
uses a connection factory to create a connection to that JMS provider.<br />
6.2.2 JMS application models<br />
As messaging technologies have evolved, two types of asynchronous messaging models<br />
have emerged, Point-to-Point and Publish/Subscribe. These models describe how JMS<br />
clients communicate <strong>with</strong> each other through JMS destination provided by the JMS<br />
provider.<br />
6.2.2.1 Point-to-Point<br />
In this model, there is a one-to-one mapping between the sender and receiver of a<br />
message. The destination is usually referred to as a queue. Figure 6.2 shows the Point-to-<br />
Point messaging model.<br />
Figure 6.2 - Point-to-Point messaging model<br />
6.2.2.2 Publish/Subscribe<br />
In this model, there is potentially a one-to-many relationship between the sender and<br />
receiver of a message. The destination is usually referred to as a topic. Figure 6.3 shows<br />
the Publish/Subscribe messaging model.
Change language