Configuring WebSphere MQ queues for WebSphere Application Server

To enable WebSphere Application Server to work with a connector, you need to create and configure WebSphere MQ queues.

The WebSphere Application Server environment allows you to map the names of physical WebSphere MQ queues to the JNDI names used in the binding properties of WebSphere Application Server. If circumstances at a later time require you to use a different queue or queue manager, you can change that name in the local configuration file, and change it in the WebSphere Application Server Administrative Console, without having to regenerate .wsdl files.

Creating and configuring the queues includes the following tasks:

Message queues provides information about how WebSphere MQ queues are used in the WebSphere business integration system. Setting the connection mode with the queue manager explains how to specify the connection mode in the connector's configuration file.

Creating the WebSphere MQ queues

The business integration system requires that you create queues with the properties listed below.

Note:
When you configure the connector, under Specifying the queues to be used by the connector, you will need to specify the name of each of these queues as a standard property in the connector's configuration file.

Ways to define queues

You can configure the WebSphere MQ queues needed for your adapter, using any of the following methods:

Tip

To make it easy to identify the connector with which a queue is associated, use the name of the connector as a prefix in the queue name. For example, name the Clarify connector's event delivery queue: clarifyconnector/deliveryqueue.

Using WebSphere Business Integration adapter batch files to configure WebSphere MQ queues

WebSphere Business Integration adapters provide a set of batch files that you can run to configure the WebSphere MQ queues needed for the adapters you are deploying. The batch files, located in ProductDir\templates, consist of:

For more information about using clear_mq.bat, seeClearing messages from WebSphere MQ queues.

The contents of the crossworlds_mq.tst file are shown below. You can use this one file to specify the queues needed by each adapter you are configuring. Edit the file as follows:

  1. Delete the statements:
    DEFINE QLOCAL(IC/SERVER_NAME/DestinationAdapter)

    DEFINE QLOCAL(AP/DestinationAdapter/SERVER_NAME)

    These apply only to business integration systems that use WebSphere InterChange Server.

  2. For each adapter you are deploying, create a separate set of queue definition statements using as a template the statements beginning with DEFINE QLOCAL(AdapterName/AdminInQueue).
  3. If you are using bindings mode with remote queue definitions, customize the statement, DEFINE CHANNEL(CHANNEL1) CHLTYPE(SVRCONN) TRPTYPE(TCP), with the requested information for each queue manager you need to configure. If you are using client mode for your queue configuration, leave the statement as is. For more information about supported queue configurations, see Defining the queue configuration.

*******************************************************************/
*   For each JMS queue (delivery Transport is JMS), 
*   default values follow the convention:
*           AdapterName/QueueName
********************************************************************/
    DEFINE QLOCAL(AdapterName/AdminInQueue)
    DEFINE QLOCAL(AdapterName/AdminOutQueue)
    DEFINE QLOCAL(AdapterName/DeliveryQueue)
    DEFINE QLOCAL(AdapterName/RequestQueue)
    DEFINE QLOCAL(AdapterName/ResponseQueue)
    DEFINE QLOCAL(AdapterName/FaultQueue)
    DEFINE QLOCAL(AdapterName/SynchronousRequestQueue)
    DEFINE QLOCAL(AdapterName/SynchronousResponseQueue)
********************************************************************/
*   Define the default CrossWorlds channel type                    */
********************************************************************/
    DEFINE CHANNEL(CHANNEL1) CHLTYPE(SVRCONN) TRPTYPE(TCP)
********************************************************************/
*   End of CrossWorlds MQSeries Object Definitions                 */
********************************************************************/

Using WebSphere MQ Explorer to configure WebSphere MQ queues

For information about configuring queues using WebSphere MQ Explorer, open WebSphere MQ Explorer and refer to its online help.

Using WebSphere MQ commands to configure WebSphere MQ queues

For information about configuring queues using WebSphere MQ commands, see WebSphere MQ: System Administration Guide and WebSphere MQ: Script (MQSC) Command Reference.

Defining the queue configuration

The WebSphere business integration system supports several queue managers and queue configurations. The connector can communicate with the queue manager in any of the following modes.

Bindings mode

With bindings mode, the integration broker and the connector can communicate directly with the queue manager, without using a TCP/IP connection. The integration broker and the connector need to be installed on the same machine so that they can use the same queue manager. This is the default mode.

Bindings mode with remote queue definitions

If WebSphere Application Server and the connector are installed on separate machines, with each machine running its own queue manager, the connector and the integration broker can still communicate with their respective queue managers using bindings mode. However, you need to specify remote queue definitions as explained in the example below.

Suppose brokerQM is the queue manager used by the integration broker and connQM is the queue manager used by the connector. To enable communication between the two queue managers, you need to set up the following channel definitions:

Client mode

If WebSphere Application Server and the connector must use TCP/IP to communicate with their respective queue managers, then they must use a client mode connection. Communication occurs through a client connection that uses TCP/IP as its underlying transport.

Copyright IBM Corp. 1997, 2004