Response queues

The default name of the response queue is SYSTEM.SOAP.RESPONSE.QUEUE. You can override this by specifying the replyToQueue parameter in the target URI. See Specifying the URI for further details. The demonstration programs create this default queue automatically in the demonstration queue manager. A script is provided (setupSOAPWMQ.cmd in Windows or setupSOAPWMQ.sh in UNIX) that configures MQ with default SOAP/WebSphere MQ queue configurations for a specified queue manager. If you nominate a non-default response queue name, it is your responsibility to ensure the queue is properly defined.

 

Dynamic response queues

Permanent and temporary dynamic response queues are supported. To use a dynamic response queue, specify a model queue name in the replyToQueue field of the SOAP/WebSphere MQ URI. A model queue called SYSTEM.SOAP.MODEL.RESPONSE.QUEUE is defined for a specified queue manager by the script setupWMQSOAP.cmd (for Windows) or setupWMQSOAP.sh (for UNIX). The model queue is set up as a permanent dynamic queue but we can change it according to your requirements. Alternatively, we can create your own model queue.

For both temporary and permanent dynamic response queues, a separate instance of dynamic queue is be created for each request, and is deleted at the first occurrence of any of the following:

• the response arrives and is processed.

• the request times out.

• the requesting program terminates.

For the best performance, y

ou should normally use temporary dynamic queues rather than permanent dynamic queues. However, if you use a persistent request message in conjunction with a temporary dynamic queue, the SOAP/WebSphere MQ listener fails to process the message and outputs an error. The client will then generally time out.