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.
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.
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.