A distributed queue is one that can be load-balanced across a cluster
Deprecated.
| Security roles | The following roles have read, write, and invoke permission for all non-encrypted attributes and operations in this MBean:
|
||
| Fully Qualified Interface Name | If you use the getMBeanInfo operation in MBeanTypeServiceMBean, supply the following value as this MBean's fully qualified interface name:weblogic.j2ee.descriptor.wl.DistributedTopicBean
|
||
| Factory Methods | |||
| Additional Access Points |
In addition to accessing this MBean by invoking a factory method, you can also access this MBean from the following MBean attributes:
|
||
| Deprecated Factory Methods and Access Points |
|
This section describes attributes that provide access to other MBeans.
|
|
Gets array of all distributed-topic-member elements
Distributed topic members are configuration information about the particular specific topics that make up the aggregate distributed topic. The name of the specific topic and any configuration information about that topic can be configured with a distributed topic member bean
| Factory Methods | createDistributedTopicMember
(java.lang.String name)
Factory methods do not return objects. |
| Lookup Operation | lookupDistributedTopicMember(String name)
Returns a |
| Privileges | Read only |
| Type | DistributedDestinationMemberBean[] |
| Relationship type: | Containment. |
This section describes the following attributes:
Return the unique identifier of this bean instance.
| Privileges | Read only |
| Type | long |
| Redeploy or Restart required | Changes take effect after you redeploy the module or restart the server. |
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.
| Privileges | Read/Write |
| Type | java.lang.String |
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.
- 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.
- 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.
| Privileges | Read/Write |
| Type | java.lang.String |
| Default Value | Round-Robin |
| Legal Values |
|
The name of this entity, represented in XML as an attribute.
Many of the elements within the JMS module are named entities. All of the named entities encased by a type in the XML file must be unique. This is the identifier used to delineate a particular entity within the JMS module.
This attribute cannot be modified externally from the module (for example, with a deployment plan) because it may be used inside the module referentially.
| Privileges | Read/Write |
| Type | java.lang.String |
Optional information that you can include to describe this named JMS descriptor bean.
JMS module saves this note in the JMS descriptor file as XML
PCDATA. All left angle brackets (<) are converted to the XML
entity <. Carriage returns/line feeds are
preserved.
If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.
| Privileges | Read/Write |
| Type | java.lang.String |
The SAF Export Policy controls which applications can send JMS messages to this destination through Store-and-Forward.
- This destination allows everyone to send JMS messages to it through SAF.
- This destination does not allow anyone to send JMS messages from a remote server to it through SAF.
This attribute is dynamically configurable. A dynamic change of this attribute will affect only messages sent after the update has been made.
| Privileges | Read/Write |
| Type | java.lang.String |
| Default Value | All |
| Legal Values |
|
Gets the "unit-of-order-routing" element.
A WLMessageProducer with Unit of Order uses 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.
- producers will compute the Distributed Destination Member from the hash code of the Unit of Order.
- the configured Path Service will determine the Distributed Destination Member.
| Privileges | Read/Write |
| Type | java.lang.String |
| Default Value | Hash |
| Legal Values |
|
This section describes the following operations:
|
|
Return true if the given property has been explicitly set in this bean.
| Operation Name | "isSet" |
| Parameters | Object [] { propertyName }
where:
|
| Signature | String [] {
"java.lang.String" } |
| Returns |
boolean
|
| Exceptions |
|
Restore the given property to its default value.
| Operation Name | "unSet" |
| Parameters | Object [] { propertyName }
where:
|
| Signature | String [] {
"java.lang.String" } |
| Returns |
void
|
| Exceptions |
|