29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

If the bus member is a cluster of application servers, a queue point is created<br />

and associated with each messaging engine defined within the bus member.<br />

The queue destination is partitioned across the available messaging engines<br />

within the cluster. In this configuration, message ordering is not maintained on<br />

the queue destination.<br />

► Publication points<br />

A publication point is the message point for a topic space. When creating a<br />

topic space destination, an administrator does not need to specify a bus<br />

member to hold messages for the topic space. Creating a topic space<br />

destination automatically defines a publication point on each messaging<br />

engine within the bus.<br />

Foreign bus and link<br />

A foreign bus is an external messaging product that is either another SIBus or a<br />

<strong>WebSphere</strong> MQ network. You can set up a link to it so that messages traverse<br />

from one bus to another. The <strong>WebSphere</strong> MQ network can be seen as a foreign<br />

bus by the <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> default messaging provider using a<br />

<strong>WebSphere</strong> MQ link.<br />

JMS and the default messaging provider<br />

Java Enterprise Edition (Java EE) applications (producers and consumers)<br />

access the SIBus and the bus members through the JMS API. JMS destinations<br />

are associated with SIBus destinations. A SIBus destination implements a JMS<br />

destination function. Session Enterprise JavaBeans (EJBs) use a JMS<br />

connection factory to connect to the JMS provider. Message Driven Beans<br />

(MDBs) use a JMS activation specification to connect to the JMS provider. See<br />

Figure 10-1 on page 343.<br />

342 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!