For example, an Invoke nonterminal node in a flow file can be implemented either by means of a LINK command with the COMMAREA option, or by means of a LINK command with the CHANNEL option, or by means of an WebSphere® MQ invocation. The generation properties for this Invoke nonterminal node would consist of the type of invocation (one of the three types listed in the preceding sentence) and the related information needed to implement that type of invocation.
A generation properties file is a collection of the generation properties for all the invocations contained in a particular flow file, called the associated flow file.
The generation properties editor allows you to edit a generation properties file. The editor displays in the left pane of the editor area a hierarchical tree in which each node corresponds to a particular invocation in the associated flow file. Each node in the tree contains the generation properties for the corresponding invocation in the flow file. When you select a node in the tree, then the editor displays in the right pane of the editor area the generation properties stored in that node. You can then modify the generation properties.
There are two types of nodes in the hierarchical tree: the flow node and the invoke nodes. The flow node is the topmost node of the tree, has the same name as the associated flow, and contains the generation properties for the invocation of the flow itself. The primary generation property for a flow node is the flow type. The choice of a flow type determines which other generation properties are available for the flow node.
All the other nodes in the tree are invoke nodes. An invoke node has the same name as the corresponding Invoke node in the associated flow and contains the generation properties for that Invoke node. The primary generation property for an invoke node is the invoke type. The choice of an invoke type determines which other generation properties are available for the invoke node.
If an invalid generation property is set for an invoke
node or for a flow node, then the generation properties editor displays an error symbol
on the icon for the node
in the hierarchical tree and also displays an error message in
the blank area above the first generation property in the editor area.
The generation property provides a default value for almost all the different types of generation properties in the flow node and the invoke nodes.
Your objective in the generation properties editor is to make sure that the generation properties for each node specify the type and manner of invocation that you want the Generate Runtime Code editor to generate for the corresponding node in the flow file.