Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Weighted Distributed Topic: Configuration: General

Configuration Options     Related Tasks     Related Topics

Use this page to define the general configuration of a weighted distributed topic, whose members can carry extra message load or have extra capacity.

Configuration Options

Name Description
Name

The name of this weighted distributed topic.

JNDI Name

The name used to bind a virtual destination to the JNDI tree. Applications can use the JNDI name to look up the virtual destination.

If not specified, then the destination is not bound into the JNDI namespace.

MBean Attribute (Does not apply to application modules) :
DistributedDestinationBean.JNDIName

Load Balancing Policy

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

MBean Attribute (Does not apply to application modules) :
DistributedDestinationBean.LoadBalancingPolicy

Unit-of-Order Routing

Gets the "unit-of-order-routing" element.

A WLMessageProducer with Unit of Order will use the "unit-of-order-routing" element rather than the "load-balancing-policy" criteria to select the Distributed Destination Member.

Unit of Order may have been set programmatically with WLProducer, or administratively on the ConnectionFactory or Destination.

  • Hash

    - producers will compute the Distributed Destination Member from the hash code of the Unit of Order.

  • PathService

    - the configured Path Service will determine the Distributed Destination Member.



MBean Attribute (Does not apply to application modules) :
DistributedDestinationBean.UnitOfOrderRouting

Changes take effect after you redeploy the module or restart the server.

SAF Export Policy

MBean Attribute (Does not apply to application modules) :
DistributedDestinationBean.SafExportPolicy

Changes take effect after you redeploy the module or restart the server.

Related Tasks

Related Topics


Back to Top