In IIB 9.0 Toolkit, it gives the error “Node name: Node name must be unique within flow” in properties view when we try to assign same name to any other node within the flow and in problem view, the error message is“Node name ‘<NodeName>’ is not unique within the flow”
In WMB 8 and its previous versions of toolkit, it is allowed to give same node name to multiple nodes.
But if we look at the InfoCenter…
WMB v7, WMB v8 and IIB v9.0
It talks the same…
The name that you enter must be unique in the message flow
Although it may work, there are several times when nodes with the same name will cause problematic ambiguity on the flow.
Below are the multiple reasons why the message flow node name should be unique in WMB 8 and its previous version.
1. The name must be unique to support overriding the properties of bar file at deployment time.
2. 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.
3. The node name must be unique to use getNodeByName() method in Message Broker API to access the node by name using JavaAPI to rename/add/remove/update the node in a flow.
Adding to the above reasons, IIB v9.0 toolkit won’t allow us to create bar file and the flow will be error out in IIB v9.0 toolkit.
So it is best practice to follow the message flow node name uniqueness in WMB8 and its previous versions so that we can smoothly migrate Message Flows from WMB to IIB v9.0.
No comments:
Post a Comment