Fusion Middleware Control Help for WebLogic Server

Previous Next Open TOC in new window
Content starts here

Uniform Distributed Topic: Configuration: General

Configuration Options     

Use this page to define the general configuration for this distributed topic, such as selecting a destination key for sorting messages as they arrive on the distributed topic members.

Configuration Options

Name Description
Name

The name of this distributed topic.

MBean Attribute (Does not apply to application modules) :
UniformDistributedDestinationBean.Name

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

Scope

The scope in which this uniform distributed topic was created.

JNDI Name

The JNDI name used to look up this topic within the JNDI namespace.

If the JNDI Name is not specified, the topic destination name is not advertised through the JNDI namespace and cannot be looked up and used.

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

Template

The JMS template from which the destination is derived. A template provides an efficient means of defining multiple destinations with similar configuration values.

If a JMS template is specified, destination parameters that are set to their default values will instead inherit their values from the JMS template at run-time. However, if a JMS template is not defined, then the configuration values for the destination must be specified as part of the destination.

Although you can dynamically modify the configuration of a JMS template, the configuration values on a destination are static.

MBean Attribute (Does not apply to application modules) :
DestinationBean.Template

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

Load Balancing Policy

Determines how messages are distributed to the members of this destination.

Choose from the following distribution techniques:

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

Note: This attribute is ignored by standalone/singleton Queues and Topics, it only applies to distributed destinations.

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

Unit-of-Order Routing

Determines how a distributed destination member is selected as the destination for a message that is part of a unit-of-order. Hash, indicates that a message producer computes the member destination from the hashCode of the unit-of-order. PathService indicates that the configured Path Service determines the member destination.

Unit-of-Order Routing can be set programmatically with WLProducer, or administratively on the connection factory or destination.

Unit of Order Routing is not dynamically configurable.

Note: This attribute is ignored by standalone/singleton Queues and Topics, it only applies to distributed destinations.

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

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

Targeting Policy

Specifies whether this JMS resource defaults to the parent module's targeting or uses the subdeployment targeting mechanism.

When set to true, this resource implicitly inherits the targeting of its parent module. When set to false, this resource gets targeted based its subdeployment's targets, if one is specified.

MBean Attribute (Does not apply to application modules) :
UniformDistributedTopicBean.DefaultTargetingEnabled

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

Subdeployment

Gets the name of the sub-deployment to use when targeting this entity

Entities are targeted using a sub-deployment with this name. The targets of the sub-deployment will be the targets of this entity.

MBean Attribute (Does not apply to application modules) :
UniformDistributedTopicBean.SubDeploymentName

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


Back to Top