WebSphere MQ nodes

When synchronizing with an IBM® Integration Bus (formerly WebSphere® Message Broker), supported WebSphere MQ nodes are analyzed and mapped to operations.
The following IBM Integration Bus nodes for WebSphere MQ are supported by HCL OneTest™ API:
  • MQInput
  • MQOutput
  • MQReply
  • MQGet
HCL OneTest™ API analyzes and maps supported WebSphere MQ nodes as follows:
  1. MQOutput nodes in the flow are examined:
    • Each MQOutput node with the reply flag set is assumed to be a reply to an MQInput node and discarded.
    • Each MQOutput node with the request flag set and a fixed destination is mapped across to a WebSphere MQ-based operation consumed by the flow.
    • If there is a reply-to-queue set on the MQOutput node, the operation is a request/reply. If there is no reply information, the operation is modeled as a publish.
    • If any MQInput or MQGet nodes consume from the reply queue, they are discarded.
  2. The remaining MQInput nodes are examined:
    • Each is mapped to a WebSphere MQ operation provided by the flow.
    • If there are any MQReply nodes (or MQOutput nodes with the reply flag set) in the flow, the operation is a request-reply. If there are no reply nodes, the operation is modeled as a subscribe.
    • Any MQGet nodes that consume messages from the same input queue are discarded.
  3. Any remaining MQOutput nodes are mapped to publish operations consumed by the flow.
  4. Any remaining MQGet nodes are mapped to subscribe operations consumed by the flow.
Feedback