public interface UniformDistributedTopicBean extends UniformDistributedDestinationBean, TopicBean
A uniform distributed topic is a distributed topic whose members are configured as part of its configuration; since members share the same configuration, they are uniform. There is one member on each JMS Server that conforms to the targeting criteria of the uniform distributed topic. For example, if a uniform distributed topic is targeted to a cluster, then one member will be created on each JMS server in the cluster. Members are created and destroyed as the targeting is changed.
Modifier and Type | Method and Description |
---|---|
String |
getForwardingPolicy()
The uniform distributed topic message Forwarding Policy specifies whether a sent message is forwarded to all members.
|
void |
setForwardingPolicy(String forwardingPolicy)
Sets the value of the Message ForwardingPolicy attribute for this topic.
|
getLoadBalancingPolicy, getUnitOfOrderRouting, setLoadBalancingPolicy, setUnitOfOrderRouting
getMulticast
addDestinationKey, getAttachSender, getDeliveryFailureParams, getDeliveryParamsOverrides, getDestinationKeys, getIncompleteWorkExpirationTime, getJMSCreateDestinationIdentifier, getJNDIName, getLocalJNDIName, getMaximumMessageSize, getMessageLoggingParams, getMessagingPerformancePreference, getQuota, getSAFExportPolicy, getTemplate, getThresholds, getUnitOfWorkHandlingPolicy, isConsumptionPausedAtStartup, isDefaultUnitOfOrder, isInsertionPausedAtStartup, isProductionPausedAtStartup, removeDestinationKey, setAttachSender, setConsumptionPausedAtStartup, setDefaultUnitOfOrder, setDestinationKeys, setIncompleteWorkExpirationTime, setInsertionPausedAtStartup, setJMSCreateDestinationIdentifier, setJNDIName, setLocalJNDIName, setMaximumMessageSize, setMessagingPerformancePreference, setProductionPausedAtStartup, setQuota, setSAFExportPolicy, setTemplate, setUnitOfWorkHandlingPolicy
getSubDeploymentName, isDefaultTargetingEnabled, setDefaultTargetingEnabled, setSubDeploymentName
String getForwardingPolicy()
The uniform distributed topic message Forwarding Policy specifies whether a sent message is forwarded to all members.
The valid values are:
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.
void setForwardingPolicy(String forwardingPolicy) throws IllegalArgumentException
Sets the value of the Message ForwardingPolicy attribute for this topic.
forwardingPolicy
- message forwarding policy for this topicIllegalArgumentException
UniformDistributedTopicBean.getForwardingPolicy()