Administration Console Online Help

Configure JMS system modules
and add JMS resources

JMS system modules contains configuration JMS resources, such queues,
topics, templates, and connections factories, and are defined by XML
documents that conform to the weblogic-jmsmd.xsd
schema. System modules configured through the Administration Console are
stored in the config\jms subdirectory of the domain
directory, and a reference to the module is added in the domain's
configuration file as a JMSSystemResource element. This
reference includes the path to the JMS module file and a list of target
JMS servers, servers, and clusters on which the module is deployed.

System modules are globally available for targeting to servers and
clusters configured in the domain, and therefore are available to all
applications deployed on the same targets and to client
applications.

Note: JMS configuration resources can also be managed as
deployable application modules, either with a J2EE application as a
packaged module, which is available only to the enclosing application,
or as a stand-alone module that provides global access to the resources
defined in that module. For more information about configuring JMS
application modules, see Configuring JMS Application Modules for
Deployment

To configure a JMS system
module:

Create a JMS system
module to contain your JMS resources, such as queue and topic
destinations, connection factories, quota, and JMS templates. See
Configure JMS system
modules.

While creating a JMS system module, you can also add JMS
resources to the module by selecting the Would you like
to add resources? check box. The remaining steps explain
how to create resources by using the Summary of
Resources table on a JMS module's
Configuration page.

Before configuring
any queue or topic resources in your module, you can optionally create
other JMS resources in the module that can be referenced from within a
queue or topic, such as quota settings, templates, and destination
keys:

If the default connection factories provided by WebLogic Server
are not suitable for your application, create a new connection factory
to enable your JMS clients to create JMS connections. See Configure connection
factories.

In a clustered environment, you can create a distributed
destination, which is a set of queues or topics that are called under
a single JNDI name so they appear to be a single, logical destination
to a client. However, the members of the set are actually distributed
across multiple servers within a cluster, with each destination member
belonging to a separate JMS server.

If you need to access a foreign JNDI provider, you can configure
a Foreign Server, which represents a
JNDI provider that is outside WebLogic server. It contains information
that allows a local WebLogic Server instance to reach a remote JNDI
provider, thereby allowing for a number of foreign connection factory
and destination objects to be defined on one JNDI directory. See Configure foreign
servers.

If you need to reliably send messages to remote destinations
outside the local server instance, the JMS SAF (store-and-forward)
feature builds on the WebLogic SAF service to provide highly-available
JMS message production. For example, a JMS message producer connected
to a local server instance can reliably forward messages to a remote
JMS destination, even though that remote destination may be
temporarily unavailable when the message was sent. See Configure JMS SAF.