Author: Rohit Umarjikar
Posted: Thu Apr 13, 2017 10:08 pm (GMT 5.5)
So the problem is with Vendor application which indirectly causing the whole trx slow down. is that what you are telling?
I am not sure if this will work.
1. Get all the trailer data PUT in request -MQ ('X') with some timestamp token and continue your further processing ...
2. add a transaction that triggers the Vender application program
3. Let the Vendor his part and PUT back the response into response-MQ ( 'Y')
4.at the end of the main program you get do a GET on 'Y' MQ and validate the timestamp token and once matched then formulate the final response back to the caller else you can DELAY and GET again till whatever time caller and you agree upon the WAIT.
_________________
Regards,
Rohit Umarjikar
"Knowledge is knowing that a tomato is a fruit, but Wisdom is knowing not to put it in a fruit salad."![icon_razz.gif]()
Posted: Thu Apr 13, 2017 10:08 pm (GMT 5.5)
So the problem is with Vendor application which indirectly causing the whole trx slow down. is that what you are telling?
I am not sure if this will work.
1. Get all the trailer data PUT in request -MQ ('X') with some timestamp token and continue your further processing ...
2. add a transaction that triggers the Vender application program
3. Let the Vendor his part and PUT back the response into response-MQ ( 'Y')
4.at the end of the main program you get do a GET on 'Y' MQ and validate the timestamp token and once matched then formulate the final response back to the caller else you can DELAY and GET again till whatever time caller and you agree upon the WAIT.
_________________
Regards,
Rohit Umarjikar
"Knowledge is knowing that a tomato is a fruit, but Wisdom is knowing not to put it in a fruit salad."
