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 » Design for MQGET

Post new topic  Reply to topic
 Design for MQGET « View previous topic :: View next topic » 
Author Message
narki
PostPosted: Sun Feb 18, 2007 7:31 am    Post subject: Design for MQGET Reply with quote

Acolyte

Joined: 19 Dec 2005
Posts: 67

There is requirement to call two service . One is MQ enabled and another one is HTTP enabled. MQ enabled service is request and reply. MQ eabled service needs to be called before HHTP service. There is some data which is reauired by HTTP service from MQ Service.

I am hoping to desin my flow something like this

MQInput-->Compute-->MQOutput1(Q1)-->MQGET(Q2)-->Compute-->HTTPRequest--->MQOutput2

MY Question is
1. Is there any risk in thhis design. I hear that there are some problem with MQget node
2. Also I am sending request to MQ Service which is listening on Q1 through MQOutput1 . Q2 is the queue on which we are expecting response and MQGET is listening. Always the message is going to No Message terminal of MQGET I am not sure why. My understating is MQGET node is used to retrive message from Queue and it can be place any where in messageflow. In this case I am trying to rettive response message from MQ Service through MQGET node.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Sun Feb 18, 2007 8:15 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Quote:
I hear that there are some problem with MQget node


From who? Why do you believe them?

You likely do not have the transaction mode correct on your MQOutput node, so your request is never going to the service until your flow completes, and thus the reply is never coming back until you've finished waiting for it.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
au@kosa
PostPosted: Mon Feb 19, 2007 2:13 am    Post subject: Reply with quote

Centurion

Joined: 04 Jan 2007
Posts: 103
Location: pune

Do you need the data from
1. MQ Service request
as well as
2. MQ Service response

for creating Http service request?

Regards,
Amit Upadhyaya
Back to top
View user's profile Send private message Yahoo Messenger
jsware
PostPosted: Tue Feb 20, 2007 10:09 am    Post subject: Re: Design for MQGET Reply with quote

Chevalier

Joined: 17 May 2001
Posts: 455

narki wrote:
MY Question is
1. Is there any risk in thhis design. I hear that there are some problem with MQget node
2. Also I am sending request to MQ Service which is listening on Q1 through MQOutput1 . Q2 is the queue on which we are expecting response and MQGET is listening. Always the message is going to No Message terminal of MQGET I am not sure why. My understating is MQGET node is used to retrive message from Queue and it can be place any where in messageflow. In this case I am trying to rettive response message from MQ Service through MQGET node.

I don't think it this will scale well. You won't be able to do another MQInput until the MQOutput2 has finished unless you multithread.

In WBIMB v5 with MQGET plugin, the MQGET plugin does not work with multithreaded flows (all hell breaks loose as the plugin does not appear thread safe). I am sure the v6 MQGET node multi-threads fine. In v5 you can deploy the flow to multiple execution groups to avoid the thread-safe issue.

The MQGET node is not designed to wait for a message for any significant length of time. I would recommend splitting the flow into two:

MQInput(Q1)->Compute->MQOutput(Q2)
and
MQInput(Q3)->Compute->HTTPRequest->MQOutput(Q4)

I am assuming you have a 3rd flow which is doing:
MQInput(Q2)->SomeStuff->MQOutput(Q3)
to join the MQOutput(Q2) to MQInput(Q3).

If context needs to be sent between the two flows that does not get transferred in the message returned to Q3, then there are a number of ways of doing this, including storing in a database, using the aggregation nodes or a "cache queue" using MQGET.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Design for MQGET
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.