OTN Home > Oracle WebLogic Server 10.3.6.0 Documentation > Administration Console Online Help > Create a partitioned uniform distributed topic in a system module

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create a partitioned uniform distributed topic in a system module

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:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the Administration Console, expand Services > Messaging and select JMS Modules.
  3. In the JMS Modules table, click the name of JMS module in which to configure the topic resource.
  4. On the module's Settings page, click the New button in the Summary of Resources table.
  5. On the Create a New JMS System Module Resource page, select Distributed Topic from the list of JMS resources.
  6. Click Next.
  7. On the Distributed Topic Properties page, define the uniform distributed topic's basic properties:
    1. In Name, enter a name for the 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.
    2. In JNDI Name, enter the JNDI name used to look up the uniform distributed topic within the JNDI namespace. Applications use the JNDI Name to look up the distributed topic.

      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.
    3. In Destination Type, specify Uniform.
    4. In Forwarding Policy, specify Partitioned.
    5. Optionally, in Template, select a template to define configuration values.
  8. Click Next to proceed to the targeting page or click Finish to create the partitioned distributed topic.

    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.
  9. For basic default targeting, accept the default targets presented in the Targets box and then click Finish. The default targets are based on the parent JMS system module targets.

    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.
  10. For advanced targeting, click Advanced Targeting, which allows you to select an existing subdeployment or to create a new one. A subdeployment is a mechanism by which JMS module resources (such as stand-alone destinations, partitioned distributed destinations, and connection factories) are grouped and targeted to server resources (such as JMS servers, server instance(s), or cluster).
    • To select an existing subdeployment for the partitioned distributed topic, select one from the Subdeployments drop-down. When a valid subdeployment is selected, its targeted JMS server(s), server(s), or cluster appear as selected in the Targets box. (A subdeployment with stand-alone destinations can only be targeted to a single JMS server.) Click Finish to add the partitioned distributed topic to the selected subdeployment.
    • To create a new subdeployment for the partitioned distributed topic, click the Create a new Subdeployment button. On the Subdeployment Properties page, enter a name for the subdeployment, and then click OK. On the ensuing subdeployment targeting page, select a JMS server(s), server instance(s), or cluster in the Targets box. (A subdeployment with stand-alone destinations can only be targeted to a single JMS server.) Click Finish to add the partitioned distributed topic to the new subdeployment.

    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.
  11. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

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.


Back to Top