Subflow mediation primitive properties
You can specify values for mediation primitive properties either by using the property fields in the IBM® Integration Designer user interface or by using an XML format. The property field names displayed in IBM Integration Designer are generally different from the property names used when building a mediation flow using XML code. In the following information, icons are used to identify each property name used in IBM Integration Designer and the corresponding XML name. (Where applicable, XML names that are required, but not shown in IBM Integration Designer, are also described.)
Subflow file
The name of the file containing the subflow implementation. For example, TestSubflow.subflow.
Field detail | Value and notes |
---|---|
Required | No |
Valid values | String Note:
|
Subflow name
The qualified name specified in the subflow implementation of the format {namespace}localpart. For example, {http://TestModule}TestSubflow
Field detail | Value and notes |
---|---|
Required | No |
Valid values | String Note:
|
Subflow properties
These properties correspond to the properties promoted from primitives within the subflow implementation.
Field detail | Value and notes |
---|---|
|
Subflow references
This represents the mapping between a reference defined on the subflow implementation and a reference defined on the parent flow.
Field detail | Value and notes |
---|---|
|
Considerations
Limitations of mediation subflows:- You cannot use a Policy Resolution primitive in a subflow.
- You cannot specify a context element within a subflow. Context elements that are available in the parent flow are also available to mediation primitives in the subflow.
Sample XML code
<node name="mySubflow" type="Subflow" >
<property name="subflowFile" value="mySubflow.subflow"/>
<property name="subflowName" value="{http://TestMod}mySubflow"/>
<inputTerminal description="The In node is the starting point for the subflow."/>
<outputTerminal description="The Out node is the end point for the subflow.">
<wire targetNode="Fail1"/>
</outputTerminal>
<failTerminal/>
</node>