| Author |
Message
|
| chenna.hari |
 Posted: Thu Jan 13, 2011 5:34 am Post subject: MQInput Node Out Terminal connecting to two nodes |
 |
|
Centurion
Joined: 21 Mar 2009
Posts: 103
|
Can we connect the MQInput Node Out Terminal to two nodes.
if we can connect, what is the main purpose to connect like this
Can any one pls suggest on this query? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jan 13, 2011 5:39 am Post subject: Re: MQInput Node Out Terminal connecting to two nodes |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chenna.hari wrote: |
| Can we connect the MQInput Node Out Terminal to two nodes. |
What happens when you try it?
| chenna.hari wrote: |
| if we can connect, what is the main purpose to connect like this |
Why are you asking? You clearly have a requirement in mind. The obvious (and accurate) answer of "to connect 2 nodes to the input" doesn't seem to be enough for you.
| chenna.hari wrote: |
| Can any one pls suggest on this query? |
I suggest you try it & observe the results.
(Hint: no part of your set up will suffer physical damage during this experiment)
Perhaps if you gave a little more detail on the nature of your query we might be able to suggest further. Also if you mention why the FlowOrder node has not met your requirement?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| chenna.hari |
| Posted: Thu Jan 13, 2011 5:51 am Post subject: |
|
|
Centurion
Joined: 21 Mar 2009
Posts: 103
|
i tried connecting the Out terminal as below
MQInput -> Compute Node -> MQOutput
-> MQOutput1
the message went to MQOutput, MQOutput1 both.
the query, this should work always or we cannot predict the beviour??
is this behaviour will work for all other nodes like computenode... |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jan 13, 2011 6:05 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I know of one major Airline that does message duplication this way.
Yeah I know this sounds crazy but the have broker so using it this way is cheap.
You probably can't predict which order the message wil arrive on the queues but if the whole thing is transactional then their commit times will be pretty close together.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 13, 2011 6:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chenna.hari wrote: |
| the query, this should work always or we cannot predict the beviour?? |
It works always. What you can't predict for a given input message is which leg will execute first. So if it matters if you write to MQOutput before you write to MQOutput1 then you need a FlowOrder node.
You also need to be aware in your design of what happens if a node on one leg abends (like the Compute node in your example).
| chenna.hari wrote: |
| is this behaviour will work for all other nodes like computenode... |
Yes, with the same restrictions and problems I outline above.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| chenna.hari |
| Posted: Thu Jan 13, 2011 11:49 pm Post subject: |
|
|
Centurion
Joined: 21 Mar 2009
Posts: 103
|
|
| Back to top |
|
|
|
|
