MQ Transport: Advanced settings

You can specify temporary destination settings, Request/Reply Correlation Semantics, and Connection Resilience settings by using the Advanced tab.
The Advanced page of the MQ transport.
Table 1. . Advanced MQ Settings
MQ transport advanced setting options Description
Temporary Destination Settings
  • Model queue: Use Default Model Queue: HCL OneTest™ API uses temporary queues for recording. Select the Use Default Model Queue check box (by default, it is selected) to specify SYSTEM.DEFAULT.MODEL.QUEUE as the object from which to copy attributes. To specify a different model queue, clear the Use Default Model Queue check box and enter a queue name in the Model Queue field.
  • Open options: You can override default options when opening the queues. To specify a different open options:
    1. Click More button to select one, or more, open options that are supported for the operation.
    2. Click OK. The selected open options are converted into a decimal value, which is displayed in the field.
  • Queue Prefix: Use this field to customize the prefix for temporary dynamic queues. By default, the Queue Prefix field is blank and prefix used will be "AMQ". If you enter a value in the field, it is prefixed by "AMQ." and suffixed by "." For example, if you enter "RIT" in the Queue Prefix field, the names of any temporary queues created will have the format "AMQ.RIT.*" where "*" represents a 16-character string.
Request/Reply Correlation Settings
To associate the reply message from WebSphere® MQ with the specific request message, you can specify any of the following semantics for the message:
  • Reply CorrelationID is set to request Correlation ID: The reply message is set to use the request message correlation ID. This is set as the default option.
  • Reply CorrelationID is set to request Message ID: The correlation ID of the reply message is set to use the request message ID.
  • Reply CorrelationID not automatically set: The correlation ID of the reply message is not set automatically. Select this option if the reply message passes through another application before reaching HCL OneTest API
Connection Resilience

Connection resilience settings determine the ways in which the transport should attempt to re-establish a connection to a queue manager when the connection breaks. If the connection is re-established within the time specified in the resilience settings, the current action is attempted again; if the connection cannot be re-established, the current action is canceled.

MQ connection resilience applies only to subscribe actions, which include stubs and subscribe test steps only, and not to other cases. For example, no attempts are made to re-establish a connection while publishing a message.

  • Maximum retry attempts: Set the maximum number of attempts that HCL OneTest API should make to reestablish a connection to a queue manager. To have the transport attempt to re-establish the connection indefinitely, select the infinite check box.
  • Retry Interval: Set the duration (in seconds) that HCL OneTest API should wait between each retry attempt. During this interval, stubs and tests remain idle.