Before you begin
If you have an existing uniform distributed topic that you want to convert to a partitioned uniform distributed topic, go directly to step 10.
To create a partitioned uniform distributed topic:
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.
If you do not specify a JNDI name for the distributed topic,
it will not be available for JNDI lookup even after it has been
targeted to a server resource. Therefore, you will only be able
to access the distributed topic using the
javax.jms.topicSession.createtopic() API or in
an application-scoped context.
On the targeting page, you can either simply accept the parent JMS system module's default targets or proceed to an advanced targeting page where you can use the subdeployment mechanism for targeting this partitioned distributed topic. Oracle recommends using Advanced Targeting to target destinations to JMS servers or SAF agents.
Upon clicking Finish, the configured partitioned distributed topic is added to the module's Summary of Resources table, which displays its default targets. The default targeting will also be reflected by the Default Targeting Enabled checkbox on the partitioned distributed topic's Configuration: General page.
Upon clicking Finish, the configured partitioned distributed topic is added to the module's Summary of Resources table, which displays the user-defined subdeployment name and its targets. You can also reconfigure subdeployment targets later if you wish. For more information about managing subdeployments, refer to Configure subdeployments in JMS system modules.
After you finish
If you want to configure additional parameters for a partitioned partitioned distributed topic, including general properties, thresholds and quotas, producer overrides, logging, message delivery failure, and multicast properties, see Configure uniform distributed topics.