Skip navigation links

weblogic.management.configuration
Interface JMSDistributedDestinationMBean

All Superinterfaces:

ConfigurationMBean, DeploymentMBean, DescriptorBean, DynamicMBean, JMSConstants, JMSVirtualDestinationMBean, MBeanRegistration, NotificationBroadcaster, SettableBean, WebLogicMBean

All Known Subinterfaces:

JMSDistributedQueueMBean, JMSDistributedTopicMBean

Deprecated. 9.0.0.0 Replaced by and weblogic.j2ee.descriptor.wl.UnifrormDistributedDestinationBean

public interface JMSDistributedDestinationMBean

extends JMSVirtualDestinationMBean

This class represents a JMS distributed destination, which is comprised of multiple physical JMS destinations (topics or queues) as members of a single distributed set of destinations that can be served by multiple WebLogic Server instances within a cluster.

Since:

7.0.0.0

See Also:

UniformDistributedDestinationBean

getTemplate

JMSTemplateMBean getTemplate()

Deprecated. 

The JMS template from which the distributed destination is derived.

Returns:

The template value

setTemplate

void setTemplate(JMSTemplateMBean template)

Deprecated. 

Sets the value of the Template attribute.

See Also:

JMSDistributedDestinationMBean.getTemplate()

getLoadBalancingPolicy

String getLoadBalancingPolicy()

Deprecated. 

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

• Round-Robin

  - The system maintains an ordering of physical topic members within the 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 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 topic members is used to compute a weighted distribution for the members of the 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.

Returns:

The loadBalancingPolicy value

setLoadBalancingPolicy

void setLoadBalancingPolicy(String loadBalancingPolicy)
                            throws InvalidAttributeValueException

Deprecated. 

Sets the value of the LoadBalancingPolicy attribute.

Parameters:

loadBalancingPolicy - The new loadBalancingPolicy value

Throws:

InvalidAttributeValueException

See Also:

JMSDistributedDestinationMBean.getLoadBalancingPolicy()

Skip navigation links