IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Renaming a message flow node

You can change the name of any type of node (a built-in node, user-defined node, or subflow node) to reflect its purpose.

Before you start:
Complete the following tasks:

When you first add a node to the canvas, the editor automatically assigns a name to the node; the name is highlighted, and you can change it by entering a name of your choice. If you do not change the default name at this time, you can change it later, as described in this topic. For example, you might include a Compute node to calculate the price of a specific part in an order; you could change the name of the node to Calculate_Price.

When you rename a node, use only the supported characters for this entity. The editor prevents you from entering unsupported characters.

To rename a node:

  1. Switch to the Integration Development perspective.
  2. Open the message flow with which you want to work.
  3. You can rename a node in three ways:
    • Right-click the node and click Rename. The name is highlighted; enter a name of your choice and press Enter.
    • Click the node to select it, then click the name of the node so that it is highlighted; enter a name of your choice and press Enter.
    • Click the node to select it, then on the Description tab of the Properties view, enter a name of your choice in the Node name field.
    The name that you enter must be unique in the message flow.

If you generate ESQL code for a Compute, Database, or Filter node, the code is contained in a module that is associated with the node. The name of the module in the ESQL file must match the name specified for the module in the ESQL Module property of the corresponding node. You can modify the module name, and change it from its default value (which is the name of the message flow, concatenated with the name of the node with which the module is associated). However, ensure that the module in the ESQL file matches the node property.


ac02235_.htm | Last updated Friday, 21 July 2017