When configuring uniform distributed topics, WebLogic Server uniformly creates the necessary members on the JMS servers to which a JMS module is targeted. This ensures the consistent configuration of all distributed destination parameters, particularly in regards to weighting, security, persistence, paging, and quotas.
The legacy weighted distributed topic feature is still available for users who prefer to manually fine-tune distributed topic members. However, BEA strongly recommends configuring uniform distributed topics to ensure the consistent configuration and deployment of topic members across a cluster. For more information on creating a weighted distributed topic, see Create weighted distributed topics.
To create a uniform distributed topic:
Note: A
distributed topic that does not have a JNDI Name can be
referenced by passing the Name of the distributed topic to
javax.jms.TopicSession.createTopic()
.
Note: Once you create a uniform distributed topic, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
When a SubDeployment is selected, its targeted JMS server, server, or cluster appear as selected in the Targets box.
You can also reconfigure deployment targets later if you wish. For more information about targeting uniform distributed topics, refer to Uniform distributed topics - configure targets.
The new uniform distributed topic is added to the module's Summary of Resources table.
After you finish
If you want to configure additional parameters for a new uniform distributed topic, including general properties, thresholds and quotas, producer overrides, logging, message delivery failure, and multicast properties, see Configure uniform distributed topics.