Configuring a queue for the default messaging provider


 

+

Search Tips   |   Advanced Search

 

Overview

Use this task to configure a JMS queue for point-to-point messaging with the default messaging provider.

This task configures a JMS queue to use a queue destination on a service integration bus. The queue destination is the virtual location on the bus where messages are stored and processed for the JMS queue. If you have not created the required destination, use the task described in Configuring a destination for JMS queues. To configure a JMS queue for the default messaging provider, use the administrative console to complete the following steps.


Procedure

  1. Display the default messaging provider. In the navigation pane, click Resources > JMS > JMS providers .

  2. Select the default provider for which you want to configure a queue.

  3. Optional: Change the Scope check box to set the level at which the JMS queue is to be visible, according to your needs.

  4. In the content pane, under the Additional properties heading, click Queues. This displays any existing JMS queues for the default messaging provider in the content pane.

  5. Display the properties of the JMS queue. If you want to display an existing JMS queue, click one of the names listed.

    Alternatively, if you want to create a new JMS queue, click New, then specify the following required properties:

    Name Type the name by which the queue is known for administrative purposes.
    JNDI name Type the JNDI name that is used to bind the queue into the namespace.
    Queue name Select the name of the queue on a service integration bus that this JMS queue is to use.

  6. Specify properties for the JMS queue, according to your needs.

  7. Click OK.

  8. Save your changes to the master configuration.


Listing JMS resources for the default messaging provider
Configuring a unified connection factory for the default messaging provider
Administrative properties for JMS connections to a bus
Configuring a queue connection factory for the default messaging provider
Configuring a topic connection factory for the default messaging provider