| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Subflow NodeLabel issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| bdrummond |
 Posted: Tue Apr 07, 2015 2:30 am Post subject: Subflow NodeLabel issue |
 |
|
Disciple
Joined: 06 May 2004
Posts: 164
|
I am having a small issue when trying to capture the name of a particular node within a subflow.
Eg: Main Flow calls a subflow with a name of ‘SubFlow1’ but we have labelled the subflow node ‘SFNode1’
Within this subflow, there is a compute node labelled ‘compute’.
If I use the ESQL variable ‘NodeLabel’ in this compute node, the string ‘SubFlow1.compute’ is returned.
However, when the same code was used back in 6.1, the returned value was ‘SFNode1.compute’.
I have imported the flow into IIB v 9.0.0.2, converted all subflows to a *.subflow file and I no longer see the same variable value as I used to.
If I don’t convert the subflows and check the ‘Compile and in-line resources’ box on the BAR file, I see the 6.1 behaviour with the NodeLabel.
Can anyone shed any light on what may be the issue or is this simply something that has changed in newer versions of WMB/IIB..? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Apr 07, 2015 4:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| I think you should rewrite your subflow to use a configurable property/udp instead of relying on the name of the node as configured in the flow. |
|
| Back to top |
|
|
| bdrummond |
| Posted: Tue Apr 07, 2015 5:14 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Looks like that is what we may have to do. These are old flows that have been running for some time (v6.1) so changing them was something we didn't want to do.
I was just intrigued about the change in behaviour with IIB v9 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Apr 07, 2015 5:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
.subflow files are deployed separately unless you compile and in-line them.
This means that they are not a direct part of any flow that calls them. And so they take the names of the nodes in the subflow itself, rather than from the names of the instance of the subflow in a given message flow. |
|
| 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
|
|
|
|
