Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# JMS Topic --> Configuration --> General

Tasks Related Topics Attributes

## Overview

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

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

## Tasks

Creating a JMS Topic

## Related Topics

"WebLogic JMS Fundamentals" in Programming WebLogic JMS

"Managing WebLogic JMS" in Programming WebLogic JMS

"Developing a WebLogic JMS Application" in Programming WebLogic JMS

## Attributes

Table 27-1

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. JMSTopicMBean` Attribute: `Name` |
JNDI Name | The JNDI name used to look up this topic within the JNDI namespace. If not specified, the topic 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. JMSTopicMBean` Attribute: `JNDIName` |
Replicate JNDI Name In Cluster | Specifies whether the JNDI name for this topic destination (if one is specified) is replicated across the cluster. If this option is not selected, then the JNDI name for the topic is only visible on the server instance hosting this topic. Note: Do not disable this parameter if you are using message-driven beans (MDBs) with distributed topics in a cluster. MDBs require JNDI names to look up JMS destinations. Therefore, if a topic is remote (e.g., distributed on other servers in a cluster), and the JNDI name replication is disabled, then the MDBs will not be able to look up the remote topics. MBean: `weblogic.management. configuration. JMSTopicMBean` Attribute: `JNDINameReplicated` | Default: true Valid values: false true
Enable Store | Specifies whether this topic destination supports persistent messaging by using the JMS store specified by the JMS server. default - The topic destination uses the JMS store defined for the JMS server--if one is defined--and supports persistent messaging. However, if a JMS store is not defined for the JMS server, then persistent messages are automatically downgraded to non-persistent. false - The topic destination does not support persistent messaging. true - The topic destination does support persistent messaging. However, if a JMS store is not defined for the JMS server, then the configuration will fail and the JMS server will not boot. This attribute is not dynamically configurable. MBean: `weblogic.management. configuration. JMSTopicMBean` Attribute: `StoreEnabled` | Default: default Valid values: default false true
Template | The JMS template from which this topic destination is derived. If a JMS template is specified, the topic destination attributes that are set to their default values will inherit their values from the JMS template at run time. However, if this attribute is not defined, then the attributes for the topic destination must be specified as part of the destination. The Template attribute setting per topic destination is static. The JMS template's attributes, however, can be modified dynamically. MBean: `weblogic.management. configuration. JMSTopicMBean` Attribute: `Template` |
Destination Keys | The sort ordering for messages that arrive on this topic destination. The keys are ordered from most significant to least significant. If more than one key is specified, a key based on the `JMSMessageID` property can only be the last key in the list. Note: If `JMSMessageID` is not defined in the key, it is implicitly assumed to be the last key and is set as "ascending" (first-in, first-out) for the sort order. MBean: `weblogic.management. configuration. JMSTopicMBean` Attribute: `DestinationKey` |