The Application Server support for JMS messaging, in general, and for message-driven beans, in particular, requires messaging middleware that implements the JMS specification: a JMS provider. The Application Server uses the Sun Java System Message Queue software as its native JMS provider. The Message Queue software is tightly integrated into theApplication Server, providing transparent JMS messaging support. This support is known within Application Server as the JMS Service. The JMS Service requires only minimal administration.
The relationship of the Message Queue software to the Application Server can be one of these types: LOCAL or REMOTE. The results of these choices and their interactions with clustering are as follows:
If the type is LOCAL, the Message Queue broker starts when the Application Server starts. This is the default for a stand-alone Application Server instance.
To create a 1:1 relationship between Application Server instances and Message Queue brokers, set the type to LOCAL and give each Application Server instance a different default JMS host. You can do this regardless of whether clusters are defined in the Application Server or the Message Queue software.
If the type is REMOTE, the Message Queue broker must be started separately. This is the default if clusters are defined in the Application Server. For information about starting the broker, see the Sun Java System Message Queue 3 2005Q4 Administration Guide.
For more information about setting the type and the default JMS host, see Configuring the JMS Service.
For more information about the Message Queue software, refer to the documentation at http://docs.sun.com/app/docs/coll/1307.1.
For general information about the JMS API, see the JMS web page at http://java.sun.com/products/jms/index.html.