Configure a JMS queue destination for WebSphere MQ

 

Use this task to browse or change a JMS queue destination for point-to-point messaging with WebSphere MQ as a messaging provider. This task contains an optional step for you to create a new JMS queue destination.

 

Overview

To browse or configure a JMS queue destination for use with WebSphere MQ as a messaging provider, use the console to complete the following steps:

 

Procedure

1. Display the WebSphere MQ messaging provider. In the navigation pane, expand Resources > JMS > JMS Providers.

2. Select the WebSphere MQ provider for which you want to configure a queue destination.

    

3. Optional: Change the Scope setting to the level at which the JMS destination is visible to applications.

4. In the contents pane, under Additional Properties, click Queues This displays a table listing any existing JMS queue destinations, with a summary of their properties.

5. To browse or change the properties of an existing JMS queue destination, click its name in the list. Otherwise, to create a new queue, 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 WAS.

      JNDI name

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

      Base Queue Name

      The name of the queue to which messages are sent, on the queue manager specified by the Base Queue Manager Name property.

      CCSID

      The coded character set identifier for use with the WebSphere MQ queue manager; for example: 850.

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

    

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

    

7. Optional: If you want WAS to try to use the WebSphere MQ queue manager's remote administration utilities to create the queue, configure the WebSphere MQ Queue Connection properties.

   If you have already created your underlying queue in WebSphere MQ using its administration tools (such as runmqsc or MQ Explorer), you do not need to configure any of the WebSphere MQ Queue Connection properties. You only need to configure these properties if you want WAS to try to use the WebSphere MQ queue manager's remote administration utilities to create the queue. To be able to browse or change these MQ Config properties, have installed the WebSphere MQ client. If you have not done this, the console displays messages like the following:

   The WMQQueueDefiner MBean has encountered an error. WMSG0331E: The MQ Client is required for this functionality, but it is not installed.
   

   For any changes to these properties to take effect on the queue manager, the WebSphere MQ Queue Manager on which the queue resides (or will reside) must be configured for remote administration and be running.

   For more details about these properties, see WebSphere MQ config properties for the queue destination.

8. Click OK.

9. Save any changes to the master configuration.

10. To have the changed configuration take effect, stop then restart the appserver.

---

}

 

Related tasks

Configure a JMS queue connection factory for WebSphere MQ
Configure JMS resources for the WebSphere MQ messaging provider

 

Related Reference

WebSphere MQ queue settings
WebSphere MQ queue settings (MQ Config)