Use this task to browse or change the properties of a JMS queue destination for point-to-point
messaging by WebSphere Application Server Version 5 applications. This task contains an optional step for you to create a new topic destination.

To configure a JMS queue destination for use by WebSphere application server Version 5 applications, use the administrative console to complete the following steps:

1. Display the version 5 default messaging provider. In the navigation pane, expand Resources > JMS Providers > V5 Default Messaging.

2. Optional: Change the Scope setting to the level at which the JMS destination is visible to applications. If you define a Version 5 JMS resource at the Cell scope level, all users in the cell can look up and use that JMS resource.

3. In the content pane, under Additional Properties, click WebSphere queue destinations This displays any existing queue destinations for the Version 5 default messaging provider in the content pane.

4. To browse or change an existing JMS queue destination, click its name in the list. Otherwise, to create a new queue destination, complete the following steps:

   1. Click New in the content pane.

   2. Specify the following required properties. You can specify other properties, as described in a later step.

      Name

      The name by which this queue destination is known for administrative purposes within IBM WebSphere Application Server.

      JNDI Name

      The JNDI name that is used to bind the queue destination into the name space.

   3. Click Apply . This defines the queue destination to WebSphere Application Server, and enables you to browse or change additional properties.

5. Optional: Change properties for the queue destination, according to your needs.

6. Click OK .

7. Save any changes to the master configuration.

8. To make a queue destination available to applications, you need to host the queue on a JMS server. To add a new queue to a JMS server or to change an existing queue on a JMS server, you define the administrative name of the queue to the JMS server, as described in Managing Version 5 JMS servers in a deployment manager cell.

9. To have the changed configuration take effect, stop then restart the application server.

Related tasks
Configuring a Version 5 queue connection factory
Configuring Version 5 default JMS resources
Managing WebSphere Version 5 JMS use of WebSphere version 6 JMS resources

Related reference
Version 5 WebSphere queue destination settings