| Author |
Message
|
| Simbu |
 Posted: Tue Aug 13, 2013 8:11 am Post subject: Why message flow Node name must be unique within flow |
 |
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
In IIB 9.0 Toolkit, It gives the error "Node name '<NodeName>' is not unique within the flow" when I try to assign same name to any other node within the flow.
In WMB 8 and its previous versions of toolkit, it is allowing to give same node name to multiple nodes.
Is there any specific reasons for this node naming restrictions in IIB 9.0 Toolkit? Please share your thoughts on this. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Aug 13, 2013 8:16 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Simbu |
| Posted: Tue Aug 13, 2013 8:28 am Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
Yes it is mentioned in infocenter but WMB 8 Toolkit allowing to give the same node name to another node and deploy the flow but IIB 9.0 doesn't. |
|
| Back to top |
|
|
| kash3338 |
| Posted: Tue Aug 13, 2013 8:37 am Post subject: |
|
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
| lancelotlinc wrote: |
The name must be unique to support overriding the properties at deployment time.
| Quote: |
| The name that you enter must be unique in the message flow. |
|
Though the tip says to use unique node names, in v7 and v8 it still allows to deploy a flow with same node names in it. But that check is taken care in IB v9 and there is a error message which states Node name must be unique within flow.
But the documentation all 3 (v7, v8 and v9) talks the same and just gives the tip. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 13, 2013 8:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What's the complaint?
Why would you *possibly* want to have two nodes with the same name? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Aug 13, 2013 8:48 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Simbu wrote: |
Yes it is mentioned in infocenter but WMB 8 Toolkit allowing to give the same node name to another node and deploy the flow but IIB 9.0 doesn't. |
All the better for V9. Just like WMB V6 lets you use ESQL arrays beginning with zero, doesn't mean you should.
| Simbu wrote: |
| Why message flow Node name must be unique within flow |
Because the documentation says so.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 13, 2013 9:09 am Post subject: Re: Why message flow Node name must be unique within flow |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Simbu wrote: |
| Is there any specific reasons for this node naming restrictions in IIB 9.0 Toolkit? |
They've fixed the bug in the previous versions that allowed it? It's taken this long because IBM didn't believe anyone would be daft enough to try and give 2 nodes the same name & didn't prioritise the fix?
| Simbu wrote: |
| Please share your thoughts on this. |
I think you should be glad IIBv9's tooling is saving you from yourself.
I think if you can demonstrate a good use case where you'd need 2 nodes to have the same name then raise an RFE and post the link.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Aug 13, 2013 11:43 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I agree that it was never a great idea to have two or more nodes with exactly the same name. However, since v6.1.0.2 there has been an added reason to avoid it. A monitoring event emitted from a terminal is identified by its 'event source name'. That name is used to identify the node that emitted the event. It is also used when enabling and disabling individual event sources using mqsichangeflowmonitoring ( yes, you can do that ). In recent versions of the product the monitoring facilities are central to the Record and Replay feature.
In other words, using non-unique node names is likely to stop you from using some very useful facilities.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| Simbu |
| Posted: Tue Aug 13, 2013 9:07 pm Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
| mqjeff wrote: |
What's the complaint?
Why would you *possibly* want to have two nodes with the same name? |
I've seen that some message flows are using the the same node name for multiple nodes in my current assignment. For an instance, the main flow is using the logging subflow in different places. In this case, we named the same name for all the subflow nodes in the main flow as the WMB 8 Toolkit allowed to do so.
I'm sure that at least few WMB users coded two or more nodes with the same name for various reason like i mentioned above and all such flow will need rework to fix it in IIB 9.0 at migration time.
| lancelotlinc wrote: |
| The name must be unique to support overriding the properties at deployment time. |
| kimbert wrote: |
A monitoring event emitted from a terminal is identified by its 'event source name'. That name is used to identify the node that emitted the event. It is also used when enabling and disabling individual event sources using mqsichangeflowmonitoring ( yes, you can do that ). In recent versions of the product the monitoring facilities are central to the Record and Replay feature.
In other words, using non-unique node names is likely to stop you from using some very useful facilities |
Thanks for the information.
Also I came across getNodeByName() method to access the node by using the existing name of the node using JavaAPI.The node name is used to identify the specific node and must be unique to get the node from the flow to rename/add/remove/update. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Aug 14, 2013 4:00 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Simbu wrote: |
| Also I came across getNodeByName() method to access the node by using the existing name of the node using JavaAPI.The node name is used to identify the specific node and must be unique to get the node from the flow to rename/add/remove/update. |
Does this mean you are going to rename your message flow nodes at runtime?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Simbu |
| Posted: Wed Aug 14, 2013 4:28 am Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
| lancelotlinc wrote: |
| Simbu wrote: |
| Also I came across getNodeByName() method to access the node by using the existing name of the node using JavaAPI.The node name is used to identify the specific node and must be unique to get the node from the flow to rename/add/remove/update. |
Does this mean you are going to rename your message flow nodes at runtime? |
No. I stated another reason for "why message flow Node name must be unique within flow" apart from bar override and flow monitoring. |
|
| Back to top |
|
|
| NealM |
| Posted: Thu Aug 15, 2013 12:30 pm Post subject: |
|
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
This is somewhat off-topic, but I do wish the developers hadn't shorthanded the identification of nodes in a User Trace. They don't include the subflow name as a prefix anymore, so it is quite possible to see the same node name for different purposes in a trace, since no one creating a subflow is concerned about node name uniqueness beyond the immediate.
Hmm, maybe time for another RFE.... |
|
| Back to top |
|
|
|
|
