Service Virtualization

Expand all | Collapse all

How to Get the response for any particular Transaction ID from IBM Send Receive GET Queue

  • 1.  How to Get the response for any particular Transaction ID from IBM Send Receive GET Queue

    Posted 12-03-2018 07:25 AM

    Add IBM Native Send Receive queue

    Define Put Queue and Enter request under "Request Editor" section in IBM MQ PUT

    Define GET Queue

     

    But how can I customize the Get Queue so that it can browse the particular transaction from the queue and then fetch corresponding response?



  • 2.  Re: How to Get the response for any particular Transaction ID from IBM Send Receive GET Queue

    Posted 12-03-2018 07:35 AM

    In MQ, this is usually done with correlation schemes. If you've matched your correlation scheme with what the "real" provider does, your GET should get only the response to that PUT, because it's looking for the same ID.

     

    If your MQ is in JMS mode, there is an additional facility called JMS Message Selector, which allows a GET to inspect a JMS header property for a value, and only consume the message if it matches. JMS Message Selectors are configured in your config assets in DevTest.



  • 3.  Re: How to Get the response for any particular Transaction ID from IBM Send Receive GET Queue

    Posted 12-03-2018 07:56 AM

    Actually MQ is behaving in asynchronous way.

    Get queue is fetching response from some other transaction apart from the transaction ID placed in the PUT MQ.

     

    Can the transaction ID be defined in the "Match Options" section in GET Queue which can confirm that it pulls the response corresponding to the particular transaction ID?

     

    Or any other way to define mapping of transaction ID from PUT queue to Get queue so that it fetches corresponding response as defined in PUT request message



  • 4.  Re: How to Get the response for any particular Transaction ID from IBM Send Receive GET Queue

    Posted 12-04-2018 06:59 AM

    Can someone confirm solution for this scenario.