Technical data

Configuring JMS
Administration Guide 17-3
When you migrate WebLogic Server applications from a previous release, the
configuration information will be converted automatically, as described in “Migrating
Existing Applications” in Programming WebLogic JMS.
To configure WebLogic JMS attributes, follow the procedures described in the
following sections, or in the Administration Console Online Help, to create and
configure the JMS objects.
Once WebLogic JMS is configured, applications can send and receive messages using
the JMS API. For more information about developing WebLogic JMS applications,
refer to “Developing a WebLogic JMS Application” in Programming WebLogic JMS.
Note: To assist with your WebLogic JMS configuration planning, Programming
WebLogic JMS provides configuration checklists for the attribute
requirements and/or options that support various JMS features.
JMS Configuration Naming Rules
Each server within a domain must have a name that is unique for all configuration
objects in the domain. Within a domain, each server, machine, cluster, virtual host, and
any other resource type must be named uniquely and must not use the same name as
the domain. This unique naming rule also applies to all configurable JMS objects, such
as JMS servers, stores, templates, and connection factories.
The one exception to this unique naming rule, however, is for JMS queue and topic
destinations on different JMS servers in a domain, as follows:
n Queue destinations can use the same name as other queues on different JMS
servers; topic destinations can also use the same name as other topics on
different JMS servers.
n Queue destinations cannot use the same name with topic destinations, nor can
queues nor topics use the same name as any other configurable objects.
Starting WebLogic Server and Configuring JMS
The following sections review how to start WebLogic Server and the Administration
console, as well as provide a procedure for configuring a basic JMS implementation.