OTN Home > Oracle WebLogic Server 10.3.1.0 Documentation > Administration Console Online Help > Create topics in a system module

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create topics in a system module

Before you begin


The publish/subscribe (pub/sub) messaging model enables an application to send a message to multiple applications. Pub/sub messaging applications send and receive messages by subscribing to a topic.

To create a topic in a JMS system module:

  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 Topic from the list of JMS resources, and then click Next.
  6. On the Topic Properties page, define the topic's basic properties:
    1. In Name, enter a name for the topic.

      Once you create a topic, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
    2. In JNDI Name, enter a name for accessing the topic within the JNDI name space. Applications use the JNDI Name to look up the topic.

      If you do not specify a JNDI name for the topic, it will not be available for JNDI lookup even after it has been targeted to a JMS server. Therefore, you will only be able to access the topic using the javax.jms.topicSession.createtopic() API or in an application-scoped context.
    3. If you are using a configured JMS template to define the topic's settings, in Template, select the template for the topic.
  7. Click Next to proceed to the targeting page or click Finish to create the topic.

    Caution: If you click Finish at this point, the topic will be created but without any targeting information. As a result, the topic will not be deployed and thus will not be available to applications until you manually select a subdeployment target, as described in Specify a subdeployment for topics.

  8. You can target the topic by selecting an existing subdeployment or creating a new subdeployment. A subdeployment for stand-alone destinations is a mechanism by which multiple stand-alone destinations are grouped and targeted to a single JMS server.
    • To select an existing subdeployment for the topic, select one from the Subdeployments drop-down. When a valid subdeployment is selected, its targeted JMS server appears as selected in the Targets box. (A stand-alone topic can only be targeted to a single JMS server.) Click Finish to add the topic to the selected subdeployment.
    • To create a new subdeployment for the 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 in the Targets box. (A stand-alone topic can only be targeted to a single JMS server.) Click Finish to add the topic and JMS server to the new subdeployment.

    Upon clicking Finish, the configured topic is added to the module's Summary of Resources table, which displays the user-defined subdeployment name and JMS server target. You can also reconfigure subdeployment targets later if you wish. For more information about managing subdeployments, refer to Configure subdeployments in JMS system modules.
  9. 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 the new topic, including general properties, thresholds and quotas, producer overrides, logging, message delivery failure, and multicast properties, see Configure topics.


Back to Top