The Junction object joins two or more paths of execution into a single path. It does not join documents that travel along the path. For example, if you have five distinct paths that run to a certain point, and then all paths execute the same logic, use the Junction object to consolidate the flow at the point of common execution. You can think of the Junction object as a visual convenience in junction of the multiple threads going into the Junction object and enabling them to execute the same logic after the Junction. You will also notice a dotted-dashed line coming out of the Junction object showing that there are multiple threads of execution on the outbound end.
As a reference, the following two images of the process flow are identical in execution.
The Junction object is located in the iWay Integration Tools (iIT) Palette, under the Flow Control group, as shown in the following image.
When you add the Junction object to your process flow using iIT, configuration properties for this object are available in the Properties tab and grouped by subtabs.
The Debug subtab allows you to configure iterative tracing limits. When this object is part of an iterative loop, the maximum number of iterations that can be captured is 20. Tracing can be controlled by specifying the iteration that begins and ends the document capture.
Specify the iterations in which you want the tracing to begin and end.
The following tracing formats are available from the drop-down list:
- Standard tracing (default)
- Standard tracing displayed in hex format
- Just the output document
- None, under any circumstances