Technical data

17 Managing JMS
17-2 Administration Guide
Figure 17-1 WebLogic Server JMS Messaging
As illustrated in the figure, WebLogic JMS accepts messages from producer
applications and delivers them to consumer applications.
Configuring JMS
Using the Administration Console, you define configuration attributes to:
n Enable JMS.
n Create JMS servers and target a WebLogic server instance.
n Create and/or customize values for JMS servers, connection factories,
destinations (queues and topics), destination templates, destination sort order
(using destination keys), persistent stores, session pools, and connection
consumers.
n Set up custom JMS applications.
n Define thresholds and quotas.
n Enable any desired JMS features, such as server clustering, concurrent message
processing, destination sort ordering, persistent messaging, and message paging.
WebLogic JMS provides default values for some configuration attributes; you must
provide values for all others. If you specify an invalid value for any configuration
attribute, or if you fail to specify a value for an attribute for which a default does not
exist, WebLogic Server will not boot JMS when you restart it. A sample
examplesJMSServer configuration is provided with the product in the Examples
Server. For more information about starting the Examples Server, see “Starting the
Default, Examples, and Pet Store Servers” in the Installation Guide.