Administration Console Online Help

JMS Distributed Topic --> Configuration --> General

Tasks Related Topics Attributes

Overview

This tab defines general configuration attributes for a set of JMS distributed topics.

Tasks

Creating a Distributed Topic and Creating Members Automatically

Creating a Distributed Topic and Adding Existing Physical Topics as Members Manually

Attributes

Table 15-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. JMSDistributedTopicMBean` Attribute: `Name`
JNDI Name	The JNDI name used to look up the distributed destination within the JNDI namespace. Applications can use the JNDI name to look up the distributed destination. If not specified, then the destination is not bound into the JNDI namespace. MBean: `weblogic.management. configuration. JMSDistributedTopicMBean` Attribute: `JNDIName`
Load Balancing Policy	The load balancing policy for producers sending messages to a distributed destination in order to balance the message load across the members of the distributed set. Valid values are: Round-Robin - The system maintains an ordering of the underlying physical topics within the distributed set by distributing the messaging load across the topic members one at a time in the order that they are defined in the configuration file. Each WebLogic Server instance maintains an identical ordering, but may be at a different point within the ordering. If weights are assigned to any of the topic members in the set, then those members appear multiple times in the ordering. Random - The weight assigned to the distributed topic members during configuration is used to compute a weighted distribution for the underlying physical topics in the distributed set. The messaging load is distributed across the topic members by pseudo-randomly accessing the distribution. In the short run, the load will not be directly proportional to the weight. In the long run, the distribution will approach the limit of the distribution. A pure random distribution can be achieved by setting all the weights to the same value, which is typically set to 1. MBean: `weblogic.management. configuration. JMSDistributedTopicMBean` Attribute: `LoadBalancingPolicy`	Default: Round-Robin Valid values: Round-Robin Random Dynamic: yes

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

Attribute: Name

JNDI Name

The JNDI name used to look up the distributed destination within the JNDI namespace. Applications can use the JNDI name to look up the distributed destination. If not specified, then the destination is not bound into the JNDI namespace.

MBean: weblogic.management. configuration. JMSDistributedTopicMBean

Attribute: JNDIName

Load Balancing Policy

The load balancing policy for producers sending messages to a distributed destination in order to balance the message load across the members of the distributed set. Valid values are:

Round-Robin - The system maintains an ordering of the underlying physical topics within the distributed set by distributing the messaging load across the topic members one at a time in the order that they are defined in the configuration file. Each WebLogic Server instance maintains an identical ordering, but may be at a different point within the ordering. If weights are assigned to any of the topic members in the set, then those members appear multiple times in the ordering.

Random - The weight assigned to the distributed topic members during configuration is used to compute a weighted distribution for the underlying physical topics in the distributed set. The messaging load is distributed across the topic members by pseudo-randomly accessing the distribution. In the short run, the load will not be directly proportional to the weight. In the long run, the distribution will approach the limit of the distribution. A pure random distribution can be achieved by setting all the weights to the same value, which is typically set to 1.

MBean: weblogic.management. configuration. JMSDistributedTopicMBean

Attribute: LoadBalancingPolicy

Default: Round-Robin

Valid values:

Round-Robin

Random

Dynamic: yes