ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQInput node and Http node in message flow

Post new topic  Reply to topic
 MQInput node and Http node in message flow « View previous topic :: View next topic » 
Author Message
jeeth_m
PostPosted: Thu Jul 24, 2008 3:28 am    Post subject: MQInput node and Http node in message flow Reply with quote

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
View user's profile Send private message Yahoo Messenger MSN Messenger
Gaya3
PostPosted: Thu Jul 24, 2008 4:05 am    Post subject: Reply with quote

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
View user's profile Send private message
jeeth_m
PostPosted: Thu Jul 24, 2008 4:30 am    Post subject: Reply with quote

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
View user's profile Send private message Yahoo Messenger MSN Messenger
Gaya3
PostPosted: Thu Jul 24, 2008 5:27 am    Post subject: Reply with quote

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
View user's profile Send private message
sridhsri
PostPosted: Thu Jul 24, 2008 5:40 am    Post subject: Reply with quote

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
View user's profile Send private message
jeeth_m
PostPosted: Thu Jul 24, 2008 6:24 am    Post subject: Reply with quote

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
View user's profile Send private message Yahoo Messenger MSN Messenger
jeeth_m
PostPosted: Thu Jul 24, 2008 6:25 am    Post subject: Reply with quote

Voyager

Joined: 21 Jan 2002
Posts: 93

oops.. my picture ddnt come properly
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
sridhsri
PostPosted: Thu Jul 24, 2008 7:36 am    Post subject: Reply with quote

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
View user's profile Send private message
AkankshA
PostPosted: Thu Jul 24, 2008 7:55 pm    Post subject: Reply with quote

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
View user's profile Send private message Visit poster's website
jeeth_m
PostPosted: Fri Jul 25, 2008 12:39 am    Post subject: Reply with quote

Voyager

Joined: 21 Jan 2002
Posts: 93

perfect! thanks much for all the responses
Back to top
View user's profile Send private message Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MQInput node and Http node in message flow
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.