JMSDistributedTopic

JMSDistributedTopic

Description

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

Syntax
<JMSDistributedTopic


DeploymentOrder="number


JNDIName="String


LoadBalancingPolicy=( "Round-Robin" | "Random" )


Name="String


Notes="String


Targets="list of Target names


Template="JMSTemplate name


Type="String



/>
Parent Elements

Domain

Child Elements

JMSTemplate

Attributes

Attribute

Description

Range of Values and Default
DeploymentOrder A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes.Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters. Default: 1000Minimum: 0Maximum: 2³¹-1
JNDIName The JNDI name used to look up a virtual destination within the JNDI namespace. 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. Admin Console field label: JNDI NameRequired: no
LoadBalancingPolicy 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.
Admin Console field label: Load Balancing PolicyRequired: noDefault: Round-Robin
Name The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. Admin Console field label: NameRequired: no
Notes Optional information that you can include to describe this configuration. Admin Console field label: NotesRequired: no
Targets The targets in the current domain on which this item can be deployed. Required: no
Template The JMS template that the distributed destination is derived from. Required: no
Type Returns the type of the MBean. Required: no

Attribute	Description	Range of Values and Default
DeploymentOrder	A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes.Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.	Default: 1000Minimum: 0Maximum: 2³¹-1
JNDIName	The JNDI name used to look up a virtual destination within the JNDI namespace. 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.	Admin Console field label: JNDI NameRequired: no
LoadBalancingPolicy	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.	Admin Console field label: Load Balancing PolicyRequired: noDefault: Round-Robin
Name	The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.	Admin Console field label: NameRequired: no
Notes	Optional information that you can include to describe this configuration.	Admin Console field label: NotesRequired: no
Targets	The targets in the current domain on which this item can be deployed.	Required: no
Template	The JMS template that the distributed destination is derived from.	Required: no
Type	Returns the type of the MBean.	Required: no