Routing

Routing is the splitting of output to separate files based on the data values. This is a common operation in many HCL Integration Platform mapping procedures. This documentation discusses differences between the PUT() and RUN() functions when used to route data. The behavior of each is broader than simply routing, and neither function is an exact replacement for the other.

The various functions available to the map developer to do data routing are:

  • PUT()
  • RUN()

For both the PUT() and RUN() functions, the best performance for routing style maps is generally obtained by mapping the largest available group object.

The following table contains the two functions available to the map developer to do data routing.

Function Use Advantage Disadvantage
PUT()

Routes an output item to an adapter. Overhead is less than using RUN(). I/O and CPU overhead from repeated opening and closing of routing targets can be great for large maps.
RUN()

Allows a map that is currently running to execute another map. Is versatile.


Using a second map to process output allows for a great deal of flexibility in output generation.
Overhead is much greater than using PUT().

I/O and CPU overhead from repeated opening and closing of routing targets can be great for large maps.