Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Create queues in a system module

Before you begin

- Configure JMS templates

The point-to-point (PTP) messaging model enables one application to send a message to another. PTP messaging applications send and receive messages using named queues. A queue sender (producer) sends a message to a specific queue. A queue receiver (consumer) receives messages from a specific queue.

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

      Once you create a queue, 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 queue within the JNDI name space. Applications use the JNDI Name to look up the queue.

      If you do not specify a JNDI name for the queue, 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 queue using the `javax.jms.queueSession.createqueue()` API or in an application-scoped context.

   3. If you are using a configured JMS template to define the queue's settings, in Template, select the template for the queue.
7. Click Next to proceed to the targeting page or click Finish to create the queue.

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

   On the targeting page, you can either target the queue to a system-selected JMS server or optionally proceed to an advanced targeting page where you can either select an existing subdeployment or create a new subdeployment. A subdeployment for JMS destinations is a mechanism by which multiple standalone destinations are grouped and targeted to a single JMS server.

8. For basic system-selected targeting, simply select a JMS server in the Targets box, and then click Finish. A system-owned subdeployment is automatically generated for the queue and the selected JMS server, using the BEA_JMS_SUBDEPLOYMENT_XXXX name space, where XXXX is the name of the targeted JMS server.

   Note: JMS administrators cannot create any subdeployment beginning with BEA_JMS_SUBDEPLOYMENT. This naming restriction is validated during the subdeployment creation process.

   Upon clicking Finish, the configured queue is added to the module's Summary of Resources table, which displays its system-generated 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. For advanced targeting, click Advanced Targeting, which allows you to select an existing subdeployment or to create a new one.
   - To select an existing subdeployment for the queue, 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 standalone queue can only be targeted to a single JMS server.) Click Finish to add the queue to the selected subdeployment.
   - To create a new subdeployment for the queue, 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 standalone queue can only be targeted to a single JMS server.) Click Finish to add the queue and JMS server to the new subdeployment.

   Upon clicking Finish, the configured queue 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.

10. 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 queue, including general properties, thresholds and quotas, producer overrides, logging, and delivery failure properties, see Configure queues.