| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Subflow within a subflow |
« View previous topic :: View next topic » |
| Author |
Message
|
| kspranava |
 Posted: Thu Aug 24, 2006 5:09 am Post subject: Subflow within a subflow |
 |
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Dear Gurus,
I am on MBv6 and Windows, I have the following setup,
Mainflow_1:
MQI/pnode --> FlowOrderNode (1)(2)--> (1)Subflow_1 --> MQO/pnode
--> (2)Subflow_2 --> MQO/pnode
Subflow_1:
i/pterminal --> compute_1 --> route to label
label_1 --> compute_2 --> o/pterminal
label_2 --> compute_3 --> o/pterminal
Subflow_2:
i/pterminal --> compute_1 --> Subflow_1 --> o/pterminal
While trying to deploy the above Mainflow_1, I get compilation error stating that,
'Duplicate label name 'label_1'. Looks like broker is not liking to have 2 or more instances of same subflow (containing route to label and label nodes) in a message flow.Have any one come across such a problem?
Problem 2:
After removing route to label and label nodes in above Subflow_1, I am able to deploy the main message flow. But then whenever a message comes out of 'o/pterminal' of Subflow_1 (called from subflow_2) in FlowOrderNode path(2), control is returned to either MQO/pnode or o/pterminal of subflow_2, it is random; where as I expect the control to be returned to o/pterminal of Subflow_2 always.
Any insights are much appreciated.
Thanks,
kspranava. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Aug 24, 2006 5:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay, what?
If I understand what you're trying to do, you're trying to send the same message through the same subflow twice. But the second time, you want to do some additional manipulation on it first.
I would wire it like this, then.
FlowOrderNode(1)(2) --> (1)(a)SubFlow_1 -->MQO/pnode
--> (2)compute_1 from subflow_2 -->(a)
Or if you really need to put that Compute in a subflow, then SubFlow 2 should just be i/pterminal->compute_1->o/p terminal. And then your flow would look closer to what you started with, except instead of going to another MQOutput node, it would go to SubFlow_1.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kspranava |
| Posted: Thu Aug 24, 2006 5:48 am Post subject: |
|
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Hi Jefflowrey,
It is just not only one compute node in subflow_2. There are many other operations done in subflow_2.
Thanks,
-kspranava. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 24, 2006 7:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Regardless, I wouldn't try and embed the subflow - just have multiple connections to it's in Terminal.
I'm not aware of a good reason why embedding it would cause a problem - but it does seem to be causing one for you. This may even be a design feature.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Aug 24, 2006 8:54 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
While trying to deploy the above Mainflow_1, I get compilation error stating that,
'Duplicate label name 'label_1'. Looks like broker is not liking to have 2 or more instances of same subflow (containing route to label and label nodes) in a message flow.Have any one come across such a problem?
|
This makes sense...remember that sublows are ONLY artifacts of the toolkit, when deployed, the broker doesn't know anything about sub-flows ... what you've done would cause 'label_1' to be defined TWICE in the flow....
the random return points is harder to understand....
Go with Jeff's suggestion....
_________________
-wayne |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
