Hi all,
I am working on one application where i need to put REQUEST MESSAGE in REQUEST QUEUE, after that i need to generate response and put it into RESPONSE QUEUE. Please tell me what are the required settings that i need to do at MQ server side to generate response after receiving the every request message.
Note:-Both my request and response queues are having same queue manager.
thanks,
madhu
Following objects are required for one-way communication (i.e. sending message) :
Sender Server(say Srv1) MQ objects required (obviously inside the QMGR) :
1) Remote queue definition (attributes : RNAME, RQMNAME)
2) Transmission local queue (attribute : USAGE(XMITQ))
3) Sender Channel (attributes : Reciever server IP and port number)
Reciever Server(Srv2) MQ required (obviously inside the QMGR) :
1) Listener (attributes : Port)
2) Reciever Channel
3) Local Queue
For response message i.e. from App2 to App1..... Srv2 will become sender server, while Svr1 will become receiver server. And just oposite set of MQ objects will be required on each MQ Server.
In case you have any further queries, please write back.
Akash, all this info about remote queues and channels is unecessary, as the original poster said the request and reply queues were on the same queue manager.
>sender channel => Listener => receiver channel
This is inaccurate. The Listener is not involved in message transmission, its only job is to start a Message Channel Agent when a new connection happens on its TCP port.
Message Channel Agent for Sender channel => TCP/IP network => Message Channel agent for Receiver channel
is a more accurate depiction.
Thanks for correcting me. Sometimes, I am not a good reader.
Well, coming back to the main question :
Are you having two applications connecting to the same queue manager?? Wherein one application generates a request message and the other application reverts a response?
I mean, the request and response messages certainly must be created by two different applications?? right ?? and both are connected to the same QMGR ??
If that's the case, how about just putting a message in a local queue and then putting a response in another local queue and having right reader application read it from those local queues.
A request/response design also needs to consider message affinity. Typically a number or requesters will share a request queue and possibly the response queue too, so a requester needs to be able to wait for and get the correct response message. Usually this is done using match on CorrelationId.
HTH, Glenn
Tags
Use the search field to
find all types of content in My developerWorks with that tag.
Use the slider bar to see more or fewer tags.
Popular tags shows the top tags for this particular type of content or application that you're viewing.
My tags shows your tags for this particular type of content or application that
you're viewing.
