Author |
Message
|
jeeth_m |
Posted: Thu Jul 24, 2008 3:28 am Post subject: MQInput node and Http node in message flow |
|
|
Voyager
Joined: 21 Jan 2002 Posts: 93
|
Hi,
Is there any best practice around using MQInput and http node in same message flow. Is it discouraged or something? |
|
Back to top |
|
 |
Gaya3 |
Posted: Thu Jul 24, 2008 4:05 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
infact i didnt understand your question?
you can use the same and build a webservice flow thats all i can say here.. _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
jeeth_m |
Posted: Thu Jul 24, 2008 4:30 am Post subject: |
|
|
Voyager
Joined: 21 Jan 2002 Posts: 93
|
Hi,
I apologise for not giving in more detail.
I need to expose a service orver http and MQ. I am planning to use a single flow to accept both MQ and http request.
I would like to know if this is a reccomended approach.
Another approach will be to have two flows, of which one will have http node and another with MQ node. The one listening to MQ will have the service implementation. flow with http will convert incoming http to MQ and calls the second flow which has the service implementation.
Does this make it clear? |
|
Back to top |
|
 |
Gaya3 |
Posted: Thu Jul 24, 2008 5:27 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
MQInput -->Compute (SOAP Conversion) --> HTTPRequest --> ResponseOutput --Invoking WebService
HTTPInput -->Compute ---> HTTPReply --Getting response from the WS and broker does the service
i agree with your second idea. _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
sridhsri |
Posted: Thu Jul 24, 2008 5:40 am Post subject: |
|
|
Master
Joined: 19 Jun 2008 Posts: 297
|
jeeth_m, I agree with your approach. In my opinion it is good design to convert you HTTP request to MQ and then back to HTTP. MQ is more reliable than HTTP. |
|
Back to top |
|
 |
jeeth_m |
Posted: Thu Jul 24, 2008 6:24 am Post subject: |
|
|
Voyager
Joined: 21 Jan 2002 Posts: 93
|
MQ --->\
\ / ----> MQ Reply
/---> compute node --->/
Http --->/ \
\ ----> Http reply
This is the approach i would like to take. in my compute node i can always check if the input message is from MQ or http based on that save the correlation, and send the replies via http or MQ.
Any comments on this? |
|
Back to top |
|
 |
jeeth_m |
Posted: Thu Jul 24, 2008 6:25 am Post subject: |
|
|
Voyager
Joined: 21 Jan 2002 Posts: 93
|
oops.. my picture ddnt come properly  |
|
Back to top |
|
 |
sridhsri |
Posted: Thu Jul 24, 2008 7:36 am Post subject: |
|
|
Master
Joined: 19 Jun 2008 Posts: 297
|
It would be very similar to the sample provided by the toolkit for web services. You will find that HTTP is converted to MQ and back to HTTP in that sample. |
|
Back to top |
|
 |
AkankshA |
Posted: Thu Jul 24, 2008 7:55 pm Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
jeeth_m wrote: |
Another approach will be to have two flows, of which one will have http node and another with MQ node. The one listening to MQ will have the service implementation. flow with http will convert incoming http to MQ and calls the second flow which has the service implementation.
|
There's no harm in any of the suggested implementations...
using two flows ll bring in modularity and also this http to MQ can be reused for further implementations however if u use same flow then MQMD build code ll be duplicated there also... though not much of a concern..
In case you need to send HTTP responce back once the entire flow is complete then go for one flow approach. .else u can go with two flows...
Entirely depends on your functional as well as Non functional requirements and SLAs
 _________________ Cheers |
|
Back to top |
|
 |
jeeth_m |
Posted: Fri Jul 25, 2008 12:39 am Post subject: |
|
|
Voyager
Joined: 21 Jan 2002 Posts: 93
|
perfect! thanks much for all the responses |
|
Back to top |
|
 |
|