bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

JMS Queue --> Configuration --> General

Tasks Additional Documentation Attributes

Overview

This tab defines general configuration attributes for a JMS queue. After defining a JMS server, you can configure its queues. You can configure one or more queues for each JMS server.

Note: You configure queues explicitly or by configuring a JMS template that can be used to define multiple queues with similar attribute settings, as described in JMS Template Tasks.

Tasks

Create a JMS Queue

Clone a JMS Queue

Delete a JMS Queue

Additional Documentation

(Requires an Internet connection.)

"Managing JMS"in the Administration Guide

"WebLogic JMS Fundamentals" in Programming WebLogic JMS

"Managing WebLogic JMS" in Programming WebLogic JMS

"Developing a WebLogic JMS Application"in Programming WebLogic JMS

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Name | The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. MBean: weblogic.management. configuration. JMSQueueMBean Attribute: Name | Configurable: yes Readable: yes Writable: yes
JNDIName | The JNDI name of the destination. This value is the name used to look up the destination within the JNDI namespace. If not specified, the destination name is not advertised through the JNDI namespace and cannot be looked up and used. This attribute is not dynamically configurable. MBean: weblogic.management. configuration. JMSQueueMBean Attribute: JNDIName | Configurable: yes Readable: yes Writable: yes
Enable Store | Return one of "true", "false", or "default". Flag specifying whether or not the destination uses the persistent store specified by the JMS server: If this flag is enabled (true), but no persistent store is defined for the JMS Server, then the configuration fails and WebLogic JMS does not boot. If this flag is disabled (false), then the destination does not support persistent messages. If this flag is set to "default", then the destination uses the persistent store--if one is defined for the JMS server--and supports persistent messaging. This attribute is not dynamically configurable. MBean: weblogic.management. configuration. JMSQueueMBean Attribute: StoreEnabled | Default: default Valid values: default false true Configurable: yes Readable: yes Writable: yes
Template | The JMS template from which the destination is derived. If this attribute is not defined, then the attributes for the destination must be specified as part of the destination. The Template attribute setting per destination is static. The template attributes, however, can be modified dynamically. Note:Attributes that are set to their default values will 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. MBean: weblogic.management. configuration. JMSQueueMBean Attribute: Template | Configurable: yes Readable: yes Writable: yes
Destination Keys | Return a read-only array of the destination keys of the template or destination. MBean: weblogic.management. configuration. JMSQueueMBean Attribute: DestinationKeys | Configurable: yes Readable: yes Writable: yes