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.
Most new applications will use the Partitioned forwarding policy in combination with a logical subscription topology on a uniform distributed topic that consists of:
-
A same named physical subscription created directly on each physical member.
-
A Client ID Policy of
Unrestricted. -
A Subscription Sharing Policy of
Sharable.
For more information on how to create and use the partitioned distributed topic, see:
-
"Create a partitioned uniform distributed topic in a system module" in Oracle WebLogic Server Administration Console Help.
-
Configuring and Deploying MDBs Using Distributed Topics in Programming Message-Driven Beans for Oracle WebLogic Server
-
Developing Advanced Pub/Sub Applications in Programming JMS for Oracle WebLogic Server
Load Balancing Partitioned Distributed Topics
Partitioned topic publishers have the option of load balancing their messages across multiple members by tuning the connection factory Affinity and Load Balance attributes. The Unit of Order messages are routed to the correct member based on the UOO routing policy and the subscriber status. See Configure connection factory load balancing parameters in Oracle WebLogic Server Administration Console Help.
