Skip navigation.
Downloads | Product Documentation | Support

Creating WebLogic Configurations Using the Configuration Wizard

# Configuring a Java Messaging Service

WebLogic JMS gives you access to enterprise messaging systems that make it possible for applications to communicate with one another. To familiarize yourself with the features of WebLogic JMS, see Programming WebLogic JMS at the following URL:

http://e-docs.bea.com/wls/docs81/jms/index.html

The wizard gives you the option of configuring a JMS messaging service. To configure JMS, define the following components:

- Connection factory—Encapsulated connection configuration information that enables JMS applications to create a connection.
- File and JDBC stores—Disk-based file stores and JDBC-accessible database stores, respectively; used to store persistent messages.
- Destination Keys and JMS Templates—Keys to define the sort order for messages that arrive at a destination and templates to define multiple destinations with similar attribute settings.
- JMS servers—Servers that manage connections and message requests on behalf of clients.
- Destinations—Queues (in point-to-point models) or topics (in publish/subscribe models) that serve as destinations and distributed destinations for a JMS server.

The Messaging (JMS) Options window prompts you to configure WebLogic Java Message Service (JMS). If you select No, the wizard uses settings for your JMS configuration exactly as defined in the configuration source that you selected earlier. If you select Yes, you are prompted, in subsequent windows, to define the configuration as described in the following table.

Note: If you are creating an extension template using the Configuration Template Builder and you select No, the next step in your procedure is to set up security for your application. See Configuring Security Options in Your Extension Template.

For this task . . . | Do the following . . .
--- | ---
Configuring JMS Connection Factories | Configure connection factories, JMS objects that encapsulate connection configuration information, and enable JMS applications to create connections.
Configuring JMS Destination Keys | Configure JMS destination keys that are used to define the sort order for messages that arrive at a specific destination.
Configuring JMS Templates | Configure JMS templates which provide an efficient means of defining multiple destinations (queues and topics) with similar configuration settings.
Assigning JMS Destination Keys | Assign destination keys to templates.
Configuring JMS File Stores | Configure JMS file stores. A JMS file store is a disk-based file that is used to store persistent messages.
Configuring JMS JDBC Stores | Configure JMS JDBC stores, a JDBC-accessible database used to store persistent messages. A JMS connection factory is required for creating a JMS JDBC store.
Configuring JMS Servers | Configure JMS servers to manage connections and message requests on behalf of clients.
Assigning JMS Servers to WebLogic Server Instances | Assign the JMS servers to WebLogic Server instances. This window is displayed only if you have defined one or more JMS servers.
Configuring JMS Topics | Configure JMS topics. JMS topics support the publish/subscribe (Pub/sub) messaging model which enables an application to send a message to multiple applications. Pub/sub messaging applications send and receive messages by subscribing to a topic.
Configuring JMS Queues | Configure JMS queues. JMS queues support the point-to-point (PTP) messaging model which enables one application to send a message to another application. PTP messaging applications send and receive messages using named queues.
Configuring JMS Distributed Topics | Configure JMS distributed topics, a set of physical topics that can support service continuity in the event of a WebLogic Server failure within a cluster. This window is displayed only if you have configured a cluster.
Configuring JMS Distributed Queues | Configure JMS distributed queues, a set of physical queues that can support service continuity in the event of a WebLogic Server failure within a cluster. This window is displayed only if you have configured a cluster.
Assigning JMS Distributed Destinations | Assign JMS distributed queues or topics to a WebLogic Server or cluster.
Configuring JMS Distributed Topic Members | Assign members to a particular JMS distributed topic. This window is displayed only if you have configured a distributed topic.
Configuring JMS Distributed Queue Members | Assign members to the JMS distributed queue. This window is displayed only if you have configured a distributed queue.

## Related Topics

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

# Configuring JMS Connection Factories

A connection factory object encapsulates connection configuration information, and enables JMS applications to create connections.

The Configure JMS Connection Factories window prompts you to create JMS connection factories. This step is optional.

#### To configure JMS connection factories:

1. Review the current list of JMS connection factories. Default values may vary based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

2. Add or modify entries as required by your configuration using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS connection factory, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid name for a JMS connection factory: a string of characters that can include spaces. The default value for this field is `new_JMSConnectionFactory_``n`, where `n` specifies a numeric value that is used to differentiate among default connection factory names; the value on `n` for the first JMS connection factory is 1. The value is incremented by 1 for each connection factory that is added.
JNDI name* | Enter a valid pathname to be used to look up the connection factory within the JNDI namespace.
Default delivery mode (Optional) | From the drop-down list, select a default delivery mode to be used for messages for which a delivery mode is not explicitly defined. The following default delivery modes are available: `Persistent`—Guarantee of delivery once-and-only-once (default) `Non-Persistent`—Guarantee of a maximum of one delivery, but messages may be lost if a system failure occurs. `Unspecified`—System default delivery mode is used. For more information, see "Message Persistence" in Programming WebLogic JMS at the following URL: http://e-docs.bea.com/wls/docs81/jms/fund.html#fund004
Default priority (Optional) | Enter a default priority to be used for messages for which a priority is not explicitly defined. Any numeric value between 0 and 9 is valid, with 0 specifying the lowest priority: Levels 0-4 indicate gradations of normal priority Levels 5-9 indicate gradations of expedited priority The default value is `4`.
Acknowledge policy (Optional) | From the drop-down list, specify an acknowledge policy to be used for non-transacted sessions run in `CLIENT_ACKNOWLEDGE` mode. Options include: `All` specifies that when acknowledge is called on a message, all unacknowledged messages received on the session are acknowledged (default) `Previous` specifies that when acknowledge is called on a message, only unacknowledged messages up to, and including, the given message are acknowledged `Unspecified` For more information, see "Non-transacted Session" in Programming WebLogic JMS at http://e-docs.bea.com/wls/docs81/jms/fund.html#nontransacted

## Related Topics

"Connection Factory Object" in Programming WebLogic JMS at http://e-docs.bea.com/wls/docs81/jms/fund.html#jms_connection_factory

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

# Configuring JMS Destination Keys

Destination keys are used to define the sort order for messages that arrive on a specific destination.

The Configure JMS Destination Key(s) window prompts you to configure JMS destination keys. In subsequent windows, you can create JMS templates and, if you like, assign these destination keys to JMS templates. This step is optional.

#### To configure JMS destination keys:

1. Review the current list of JMS destination keys. Default values may vary based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

2. Add or modify entries as required by your configuration using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS destination key, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid name for the JMS destination key: a string of characters that can include spaces. The default for this field is `new_JMSDestinationKey_``n`, where `n` specifies a numeric value that is used to differentiate among default destination key names; the value of `n` for the first destination key is 1. The value is incremented by 1 for each connection factory that is added.
Property* | From the drop-down list, select a message sort key or the name of a message header field on which to sort, or enter a value in the field. Message header field keys start with the letters JMS and ignore the key type setting. The drop-down list offers the following values: `JMSCorrelationID` `JMSDeliveryTime` `JMSExpiration` `JMSMessageID` `JMSPriority` `JMSRedelivered` `JMSTimestamp` `JMSType` Note: For better performance, use message header fields as sorting keys, rather than message sort keys.
Key type (Optional) | From the drop-down list, select the expected property type for this destination key. This setting is ignored for message header field keys, which have an implied type. Valid values for the key type are: `Boolean` `Byte` `Short` `Int` `Long` `Float` `Double` `String` (default) `Unspecified`
Direction (Optional) | From the drop-down list, select the direction in which the key will sort messages: `Ascending`—uses a FIFO (first in, first out) sort order (default) `Descending`—uses a LIFO (last in, first out) sort order `Unspecified`

# Configuring JMS Templates

A JMS template provides an efficient means of defining multiple destinations with similar attribute settings. When you use JMS templates, you can take advantage of the following benefits:

- You do not need to re-enter every attribute setting each time you define a new destination; you can use the JMS template and override any setting to which you want to assign a new value.
- You can modify shared attribute settings dynamically, simply by modifying the template.

The Configure JMS Template(s) window prompts you to configure JMS templates. This step is optional.

Note: Default values may vary, based on the configuration source you selected earlier. To toggle the display mode for the list of templates between table and tab formats, click Switch Display.

#### To configure JMS templates:

1. Review the current list of JMS templates and rename them if necessary for your configuration.
2. Perform the following steps as required for your configuration:

- To add a JMS template, click Add.

Enter a valid name for the JMS template: a string of characters that can include spaces.

The default for this field is `new_JMSTemplate_``n`, where `n` specifies a numeric value that is used to differentiate among all default JMS template names; the value of `n` for the first JMS template is 1. The value is incremented by 1 for each template that is added.

- To delete a JMS template, select the template name and click Delete.
- To rename a template, select the template name and enter a new name.

3. When you finish updating the settings in the window, click Next.

## Related Topics

Configuring JMS Destination Keys

Assigning JMS Destination Keys

"JMS Template Tasks" in the WebLogic Server Administration Console Online Help at http://e-docs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#jms_template_create

# Assigning JMS Destination Keys

The JMS Destination Key Assignment window prompts you to assign destination keys to a template. This window is displayed only if you have defined JMS destination keys and one or more JMS templates. This step is optional.

#### To assign destination keys to a JMS template:

1. In the JMS Template pane, select the JMS template to which you want to assign a JMS destination key.

The current assignments for the selected JMS template are displayed in the left pane.

2. In the left pane, do one of the following:

- To assign a JMS destination key to the selected JMS template, select the associated check box.
- To remove a JMS destination key from the selected JMS template, clear the associated check box.

To select all destination keys in the list and assign them to the selected template, choose Select All. To unselect all JMS destination keys in the list, choose Unselect All.

The list of JMS destination keys associated with each JMS template is updated to reflect your changes.

3. Repeat steps 1 and 2 for each JMS destination key that you want to assign to a JMS template. You can assign a destination key to more than one template.
4. Click Next to proceed to the next configuration window.

## Related Topics

Configuring JMS Destination Keys

Configuring JMS Templates

# Configuring JMS File Stores

A JMS file store is a disk-based file in which persistent messages can be saved.

The Configure JMS File Stores window prompts you to configure JMS file stores as required for your configuration. This step is optional.

#### To configure JMS file stores:

1. Review the current list of JMS file stores. Default values may vary based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

2. Add or modify entries as required by your configuration using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS file store, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a name for the JMS file store: a string of characters that can include spaces. The name of the JMS file store must be unique among all configuration component names within the domain. The default value for this field is `new_JMSFileStore_``n`, where `n` specifies a numeric value that is used to differentiate among all default file store names; the value of `n` for the first file store is 1. The value is incremented by 1 for each file store that is added.
Directory* | Enter the pathname of the directory on the file system where the JMS file store is kept. This directory must reside on your system. Alternatively, you can click in this field to enable the Browse button to navigate to the directory on the file system where the JMS file store is kept. If such a directory does not exist, enter the pathname for one in the Location field. In this case, you are prompted to indicate whether you want to have this type of directory created for you.
Synchronous write policy | From the drop-down list, select one of the following synchronous write policies to determine how the file store writes data to disk: `Cache-Flush`—specifies that transactions cannot be completed until all their write operations have been flushed down to disk. `Disabled`—specifies that transactions are complete as soon as their writes are cached in memory. When this policy is active, the completion of transactions does not depend on waiting for writes to reach the disk. `Direct-Write`—specifies that write operations are performed directly to disk. This policy is supported on Solaris and Windows. If this policy is active on an unsupported platform, the file store automatically switches to the `Cache-Flush` policy. `Unspecified` (default) This parameter setting affects performance, scalability, and reliability. Note: If the JMS file store is used exclusively for paging non-persistent messages to disk, the synchronous write policy is ignored. For more information, see "Improving JMS File Store Performance" in the WebLogic Server Administration Console Online Help at the following URL: http://e-docs.bea.com/wls/docs81/ConsoleHelp/ jms_tuning.html#sync_write_to_filestore

# Configuring JMS JDBC Stores

A JMS JDBC store is a JDBC-accessible database used to save persistent messages. A JMS connection factory is required for creating a JMS JDBC store.

The Configure JMS JDBC Store window prompts you to create JMS JDBC stores as required for your configuration. This step is optional.

#### To configure JMS JDBC stores:

1. Review the current list of JMS JDBC stores. Default values may vary based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

2. Add or modify entries as required by your configuration, using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS JDBC store, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid name for the JMS JDBC store: a string of characters that can include spaces. The name of the JMS JDBC store must be unique among all configuration component names within the domain. The default value in this field is `new_JMSJDBCStore_``n`, where `n` specifies a numeric value that is used to differentiate among default JDBC store names; the value of n for the first JDBC store is 1. The value is incremented by 1 for each JMS JDBC store that is added. Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services.
Connection pool* | From the drop-down list, select a valid JDBC connection pool for this persistent store. Note: Only connection pools that use non-XA drivers are supported. If you are using a template that specifies a connection pool with a non-XA driver as a JMS JDBC store, and you change the driver to an XA driver, the JMS JDBC store is invalid and the connection pool is not available in the drop-down list.
Prefix name (Optional) | Enter a prefix name that uniquely identifies JMS tables in the backing store. Any continuous string of characters may be used as a valid name; spaces within names are not supported. By specifying unique prefixes you can enable multiple stores to reside in the same database. Such prefixes are prepended to table names when: The database management system (DBMS) requires fully qualified names. You must differentiate between JMS tables for two instances of WebLogic Server in order to accommodate the storage of multiple tables on a single DBMS. When prepended to a JMS table name, a prefix specified in the following format will result in a valid table name: `[schema.[catalog.]]prefix`

## Related Topics

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

# Configuring JMS Servers

A JMS server manages connections and message requests on behalf of clients.

The Configure JMS Servers window prompts you to create JMS servers as required for your configuration. This step is optional.

#### To configure JMS servers:

1. Review the current list of JMS servers. Default values may vary based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

2. Add or modify entries as required by your configuration, using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS server, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid JMS server name: a string of characters that can include spaces. The name of the JMS server must be unique among all configuration component names within the domain. The default value in this field is `new_JMSServer_``n`, where `n` specifies a numeric value that is used to differentiate among all default JMS server names; the value of `n` for the first JMS server is 1. The value is incremented by 1 for each JMS server that is added. Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services.
Store | From the drop-down list, select one of the following for the JMS server: A valid JMS persistent store A valid JMS JDBC store `Unspecified` A persistent store or JDBC store may be used by only one JMS server. A value of `Unspecified` means that persistent messaging is not supported.
Paging store | From the drop-down list, select a valid JMS paging store for the JMS server or `Unspecified.` Each JMS server must have its own paging store, which is used exclusively for paging out non-persistent messages for the JMS server and its destinations. Before you can select a paging store, you must first configure a JMS file store to be used exclusively as a paging store. The selected paging store cannot be any of the following: a) the same as the selected non-paging store; b) the same store used by any other JMS server; or c) a JMS JDBC store. Note: By default, message paging is disabled. However, a message paging store is created automatically when either bytes paging or messages paging is enabled on the JMS server or destinations of the JMS server and a message paging store is not already configured. For more information, see "Paging Out Messages to Free Up Memory" in the WebLogic Server Administration Console Online Help.To access this document, select the help icon from the Administration Console interface or go to: http://e-docs.bea.com/wls/docs81/ConsoleHelp/ jms_tuning.html#using_message_paging
Temporary template Note: This field refers to a JMS template, not a configuration or extension template. | From the drop-down list, select an existing JMS template to be used for the creation of temporary queues and topics for this JMS server. When a value is specified for this field, JMS applications can create temporary destinations. The attribute values for a temporary destination are derived from this JMS template. If provided as part of the template, the Store attribute values are ignored because temporary destinations do not support persistent messaging. If this attribute is set to none, attempts to create a temporary destination (queue or topic) fail.
Expiration scan interval | Enter the amount of time, in seconds, that you want the JMS server to pause between its cycles of scanning its destinations for expired messages to process (according to the specified Expiration Policy for the destinations). A value of 0 indicates that active scanning is disabled: expired messages are passively removed as they are discovered. The default value in this field is 30. For guidelines on setting this value, see the JMS server configuration information in the WebLogic Server Administration Console Online Help. To access this information, select the help icon from the Administration Console interface or go to: http://e-docs.bea.com/wls/docs81/ConsoleHelp/ domain_jmsserver_config_general.html#ExpirationScanInterval

## Related Topics

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

# Assigning JMS Servers to WebLogic Server Instances

The Assign JMS Servers to WebLogic Servers window prompts you to assign the JMS servers to WebLogic Server instances. This window is displayed only if you have defined one or more JMS servers.

#### To assign JMS servers to WebLogic Server instances:

1. In the Server pane, select the WebLogic Server instance to which you want to assign a JMS server.
2. Assign the JMS server to the designated WebLogic Server instance in one of the following ways:

- Double-click the name of the JMS server in the JMS Server pane.
- Select the name of the JMS server in the JMS Server pane and click the right arrow.

The name of the JMS server is removed from the JMS Server pane and added, below the name of the target WebLogic Server instance, in the Server pane.

3. Repeat steps 1 and 2 for each JMS server that you want to assign to a WebLogic Server instance.
4. Review the WebLogic Server instance assignments.

If necessary, you can remove a JMS server from a WebLogic Server instance in one of the following ways:

- Double-click the name of the JMS server in the Server pane.
- Select the name of the JMS server in the Server pane and click the left arrow.

The name of the JMS server is removed from the Server pane and restored to the JMS Server pane.

5. Click Next to proceed to the next configuration window.

## Related Topics

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

# Configuring JMS Topics

JMS topics support the publish/subscribe (pub/sub) messaging model, which enables an application to send a message to multiple applications. Pub/sub messaging applications send and receive messages by subscribing to a topic.

The Configure JMS Topics window prompts you to configure JMS topics required for your configuration.This step is optional.

#### To configure JMS topics:

1. Review the current list of JMS topic configurations. Default values may vary, based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

If multiple JMS Servers are defined, the wizard displays the JMS topics for each JMS Server on a separate tab. To view a particular JMS Server, you select the corresponding tab.

2. Add or modify entries as required by your configuration using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS topic, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid name for the JMS topic: a string of characters that can include spaces. The default value in this field is `new_JMSTopic_``n`, where `n` specifies a numeric value that is used to differentiate among all default JMS topic names; the value of `n` for the first JMS topic is 1. The value is incremented by 1 for each topic that is added. Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services.
JNDI name* | Enter a valid JNDI pathname to be used to look up the topic within the JNDI namespace. The JNDI name must be unique among all JMS servers defined for the WebLogic Server instance.
Store enabled (Optional) | From the drop-down list, select a flag to specify whether or not the destination uses the persistent store specified by the JMS server. If the `true` flag is selected, but no persistent store is defined for the JMS server, then the configuration fails and WebLogic JMS does not boot. If the `false` flag is selected, then the destination does not support persistent messages. If the `default` flag is selected, then the destination uses the persistent store, if one is defined for the JMS server, and supports persistent messaging. If `Unspecified` is selected, no value is output to the `config.xml` file.
Template (Optional) Note: This field refers to a JMS template, not a configuration or extension template. | From the drop-down list, select a valid JMS template from which the destination is to be derived. If a template is not defined (`Unspecified`), then the attributes for the destination must be specified as part of the destination. The Template attribute setting for each destination is static. Template attributes, however, can be modified dynamically. Attributes that are set to default values inherit their destination values from the JMS template at run time. If this attribute is not defined, then the attributes for the destination must be specified as part of the destination.

## Related Topics

"Messaging Models" in Programming WebLogic JMS at http://e-docs.bea.com/wls/docs81/jms/fund.html#fund001``

# Configuring JMS Queues

JMS queues support the point-to-point (PTP) messaging model. This model enables one application to send a message to another. PTP messaging applications send and receive messages using named queues.

The Configure JMS Queues window prompts you to configure JMS queues required for your configuration. This step is optional.

#### To configure JMS queues:

1. Review the current list of JMS queues. Default values may vary, based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

If multiple JMS Servers are defined, the wizard displays the JMS topics for each JMS Server on a separate tab. To view a particular JMS Server, you select the corresponding tab.

2. Add or modify entries as required by your configuration using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS queue, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a name for the JMS queue: a string of characters that can include spaces. The default value in this field is `new_JMSQueue_``n`, where `n` specifies a numeric value that is used to differentiate among all default JMS queue names; the value of n for the first JMS queue is 1. The value is incremented by 1 for each JMS queue that is added. Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services.
JNDI name* | Enter a valid JNDI pathname to be used to look up the queue within the JNDI namespace. The JNDI name must be unique among all JMS servers defined for the WebLogic Server instance.
Store enabled (Optional) | From the drop-down list, select a flag specifying whether or not the destination uses the persistent store specified by the JMS server. If the flag you select is: `true`, but no persistent store is defined for the JMS Server, then the configuration fails and WebLogic JMS does not boot. `false`, then the destination does not support persistent messages. `default`, then the destination uses the persistent store, if one is defined for the JMS server, and supports persistent messaging. `Unspecified`
Template (Optional) | From the drop-down list, select a valid JMS template from which the destination is to be derived. If no template is defined (`Unspecified`), then the attributes for the destination must be specified as part of the destination. The Template attribute setting for each destination is static. Template attributes, however, can be modified dynamically. Attributes that are set to their default values inherit their destination values from the JMS template at run time. If this attribute is not defined, then the attributes for the destination must be specified as part of the destination.

Note: If you are creating an extension template using the Configuration Template Builder, the next step in your procedure is to set up security for your template. See Configuring Security Options in Your Extension Template.

## Related Topics

"Messaging Models" in Programming WebLogic JMS at http://e-docs.bea.com/wls/docs81/jms/fund.html#fund001

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

# Configuring JMS Distributed Topics

A distributed topic consists of a set of physical topics that maintain continuous service in the event of a WebLogic Server failure within a cluster. For more information about JMS distributed topics, see "Using Distributed Destinations," in Programming WebLogic JMS at the following URL:

http://e-docs.bea.com/wls/docs81/jms/implement.html#using_distributed_destinations

The Configure JMS Distributed Topics window prompts you to configure JMS distributed topics required for your configuration. This window is displayed only if you have configured a cluster, as described in Configuring Clusters. This step is optional.

#### To configure JMS distributed topics:

1. Review the current list of JMS distributed topic configurations. Default values may vary based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

2. Add or modify the entries as required by your configuration using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS distributed topic, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid name for the JMS distributed topic: a string of characters that can include spaces. The default value in this field is `new_JMSDistributedTopic_``n`, where `n` specifies a numeric value that is used to differentiate among all default JMS distributed topic names; the value of `n` for the first JMS distributed topic is 1. The value is incremented by 1 for each distributed topic that is added. Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services.
JNDI name* | Enter a valid JNDI pathname to be used to look up the distributed topic within the JNDI namespace.
Load balancing policy (Optional) | From the drop-down list, select a load-balancing policy that can be used by producers sending messages to this distributed queue in order to balance the message load across the members of a distributed destination. The following options are available: `Round-Robin` `RANDOM` `Unspecified`

# Configuring JMS Distributed Queues

A distributed queue consists of a set of physical queues that maintain continuous service in the event of a WebLogic Server failure within a cluster. For more information about JMS distributed queues, see "Using Distributed Destinations," in Programming WebLogic JMS at the following URL:

http://e-docs.bea.com/wls/docs81/jms/implement.html#using_distributed_destinations

The Configure JMS Distributed Queues window prompts you to configure the JMS distributed queues required for your configuration. This window is displayed only if you have configured a cluster, as described in Configuring Clusters. This step is optional.

#### To configure JMS distributed queues:

1. Review the current list of JMS distributed queue configurations. Default values may vary based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

2. Add or modify entries as required by your configuration using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS distributed queue, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid name for the JMS distributed queue: a string of characters that can include spaces. The default value in this field is `new_JMSDistributedQueue_``n`, where `n` specifies a numeric value that is used to differentiate among all default JMS distributed queue names; the value of `n` for the first JMS distributed queue is 1. The value is incremented by 1 for each JMS distributed queue that is added. Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services.
JNDI name* | Enter a valid JNDI pathname to be used to look up the distributed queue within the JNDI namespace.
Load balancing policy (Optional) | From the drop-down list, select a load-balancing policy that can be used by producers sending messages to this distributed queue in order to balance the message load across the members of a distributed destination. The following options are available: `Round-Robin` `RANDOM` `Unspecified`
Forward Delay (Optional) | Enter the amount of time, in seconds, that a distributed queue member holding messages for which it has no consumers waits before forwarding the messages to other queue members that do have consumers. A value of -1 indicates that no messages are forwarded to other queue members.

# Assigning JMS Distributed Destinations

The Assign JMS Distributed Destinations to Servers or Clusters window prompts you to assign JMS distributed queues or topics to a WebLogic Server instance or cluster. This window is displayed only if you have defined JMS distributed queues or topics. This step is optional.

#### To assign distributed queues or topics to a server or cluster:

1. Select, in the Target pane, the WebLogic Server or cluster to which you want to assign a JMS distributed queue or topic.
2. Assign the queue or topic to the designated WebLogic Server or cluster in one of the following ways:

- Double-click the name of the JMS distributed queue or topic in the JMS Distributed Destination pane.
- Select the JMS distributed queue or topic and click the right arrow.

The name of the JMS distributed queue or topic is removed from the JMS Distributed Destination pane and added, below the name of the target WebLogic Server or cluster, to the Target pane.

3. Repeat steps 1 and 2 for each distributed queue or topic that you want to assign to a WebLogic Server or cluster.
4. Review the WebLogic Server and cluster assignments.

If necessary, you can remove a JMS distributed queue or topic from a WebLogic Server or cluster in one of the following ways:

- Double-click the name of the JMS distributed queue or topic in the Target list.
- Select the name of the JMS distributed queue or topic and click the left arrow.

The name of the JMS distributed queue or topic is removed from the Target list and restored to the JMS Distributed Destination pane.

5. Click Next to proceed to the next configuration window.

# Configuring JMS Distributed Topic Members

The Configure JMS Distributed Topic Members window prompts you to assign members to the JMS distributed topic. This window is displayed only if you have configured a distributed topic, as described in Configuring JMS Distributed Topics. This step is optional.

#### To configure JMS distributed topic members:

1. Review the current list of JMS distributed topic member configurations. Default values may vary based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

If multiple JMS Distributed Topics are defined, the wizard displays the distributed topic members for each JMS Distributed Topic on a separate tab. To view a particular component, you select the corresponding tab.

2. Add or modify the entries required by your configuration using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS distributed topic member, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid name for the JMS distributed topic member: a string of characters that can include spaces. The default value in this field is `new_JMSDistributedTopicMember_``n`, where `n` specifies a numeric value that is used to differentiate among all default JMS distributed topic member names; the value of `n` for the first JMS distributed topic member is 1. The value is incremented by 1 for each JMS distributed topic member that is added. Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services.
JMS topic* | From the drop-down list, select the associated JMS topic. If you are adding a JMS distributed topic member, this drop-down list is not populated until you select a JMS distributed topic from the JMS Distributed Topic field. Only JMS topics with the same target as the associated JMS distributed topic are displayed in the drop-down list.
Weight (Optional) | Enter a numeric value to indicate the weight (that is, a measure of ability to handle message load) of the topic member with respect to other topic members in the distributed destination. The default value is 1. For more information, see "Random Distribution" in Programming WebLogic JMS at the following URL: http://e-docs.bea.com/wls/docs81/jms/implement.html#random_weight
JMS distributed topic* | If you are adding a distributed topic member, select the JMS distributed topic to which this member is assigned from the drop-down list. For existing distributed topic members, no action is required; the JMS distributed topic associated with the distributed topic member is displayed in the field.

# Configuring JMS Distributed Queue Members

The Configure JMS Distributed Queue Members window prompts you to assign members to the JMS distributed queue. This window is displayed only if you have configured a distributed queue, as described in Configuring JMS Distributed Topics.

#### To configure JMS distributed queue members:

1. Review the current list of JMS distributed queue member configurations. Default values may vary based on the configuration source you selected earlier.

Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.

If multiple JMS Distributed Queues are defined, the wizard displays the distributed topic members for each JMS Distributed Queue on a separate tab. To view a particular component, you select the corresponding tab.

2. Add or modify the entries required by your configuration, using the guidelines provided in the following table. (Fields marked with an asterisk are required.) To delete a JMS distributed queue member, click in one of its fields and click Delete. When you finish updating your settings, click Next.

In this field . . . | Do the following . . .
--- | ---
Name* | Enter a valid name for the JMS distributed queue member: a string of characters that can include spaces. The default value in this field is `new_JMSDistributedQueueMember_``n`, where `n` specifies a numeric value that is used to differentiate among all default JMS distributed queue member names; the value of `n` for the first JMS distributed queue member is 1. The value is incremented by 1 for each JMS distributed queue member that is added. Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services.
JMS queue* | From the drop-down list, select the associated JMS queue. If you are adding a JMS distributed queue member, this drop-down list is not populated until you select a JMS distributed queue from the JMS Distributed Queue field. Only JMS queues with the same target as the associated JMS distributed queue are displayed in the drop-down list.
Weight | (Optional) Enter a numeric value for the weight (that is, a measure of ability to handle message load) of the queue member with respect to other queue members in the distributed destination. The default value is 1. For more information, see "Random Distribution" in Programming WebLogic JMS at the following URL: http://e-docs.bea.com/wls/docs81/jms/implement.html#random_weight
JMS distributed queue* | If you are adding a distributed queue member, select the JMS distributed queue to which this member is assigned from the drop-down list. For existing distributed queue members, no action is required; the JMS distributed queue associated with the distributed queue member is displayed in the field.