Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create a Distributed Topic

Configuration Options     Related Tasks     Related Topics

Use this page to create a either a uniform distributed topic or a weighted distributed topic in a JMS module.

To create a uniform distributed topic, select the Allocate Members Uniformly check box. This will automatically creates uniformly-configured topic members on selected JMS servers, or on all JMS servers on a target server or cluster. This feature ensures the consistent configuration of all distributed topic parameters, particularly in regards to weighting, security, persistence, paging, and quotas.

To create a weighted distributed topic, clear the Allocate Members Uniformly check box. Then you can manually configure and fine-tune "weighted" distributed topic members.

Configuration Options

Name Description

The name of this distributed topic.


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) :

Destination Type

The type of this topic, either Uniform or Weighted.

Forwarding Policy

The uniform distributed topic message Forwarding Policy specifies whether a sent message is forwarded to all members.

The valid values are:

  • Replicated

    - The default. All physical topic members receive each sent message. If a message arrives at one of the physical topic members, a copy of this message is forwarded to the other members of that uniform distributed topic. A subscription on any one particular member will get a copy of any message sent to the uniform distributed topic logical name or to any particular uniform distributed topic member.

  • Partitioned

    - The physical member receiving the message is the only member of the uniform distributed topic that is aware of the message. When a message is published to the logical name of a Partitioned uniform distributed topic, it will only arrive on one particular physical topic member. Once a message arrives on a physical topic member, the message is not forwarded to the rest of the members of the uniform distributed destination, and subscribers on other physical topic members do not get a copy of that message. The Partitioned capability was added in WebLogic 10.3.4 (11gR1PS3).

A publisher that uses a logical JNDI name of a Replicated distributed topic is created on one member and every send call publishes messages to the same member regardless the value of the Load Balancing Enabled attribute. This is behavior is backward compatible with previous WebLogic Server releases when using a uniform distributed topic. Under the same conditions, a Partitioned distributed topic publishes to the same member only when the value of the Load Balancing Enabled attribute is set to false. If the value of the Load Balancing Enabled attribute is to true, a publisher to a Partitioned distributed topic publishes messages that are load balanced accross all the members of the uniform distributed topic.

Most new applications will use the new Partitioned forwarding policy in combination with a logical subscription topology on a uniform distributed topic that consists of: (1) a same named physical subscription created directly on each physical member, (2) a Client ID Policy of Unrestricted, and (3) a Subscription Sharing Policy of Sharable. WL 10.3.4 Message Driven Beans (MDBs) provides a Topic Messages Distribution Mode option to automatically setup this kind of topology.

MBean Attribute (Does not apply to application modules) :

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


The name of the template used to defining multiple destinations with similar configuration values.

Related Tasks

Related Topics

Back to Top