Routing files

When the Distribution engine releases a transmission, it also creates a routing file. The routing file contains the outbound transmission ID and the name of the channel definition that should be used to route the transmission to its final receiver.

If the channel was configured for handshaking, more handshaking elements are included in the routing file.

This example routing file is without handshaking:

<destinations>
   <destRouting routingNum="061000052">
      <icpcsRouting>
         <outgoing>
            <channelDefName>FwdChannel03</channelDefName>
            <outPresGrpId>1</outPresGrpId>
         </outgoing>
      </icpcsRouting>
   </destRouting>
</destinations>

This example routing file is with handshaking configured in the channel definition:

<destinations>
   <destRouting routingNum="061000052">
      <icpcsRouting>
         <outgoing>
            <channelDefName>FwdChannel03</channelDefName>
            <outPresGrpId>1</outPresGrpId>
            <handshake>
               <unitOfWork>PRES_OPG1</unitOfWork>
               <fileDetails>
                  <fileDetail type="data" byteCount="140609" recordCount="50"
                              itemCount="4" itemAmount="8008104">
                              ICL-FD3.T.R0610.N0005.D100805.T100934.dat
                  </fileDetail>
                  <fileDetail type="eof">
                              ICL-FD3.T.R0610.N0005.D100805.T100934.eof
                  </fileDetail>
                  <fileDetail type="trigger">
                              ICL-FD3.T.R0610.N0005.D100805.T100934.rte
                  </fileDetail>
               </fileDetails>
            </handshake>
         </outgoing>
      </icpcsRouting>
   </destRouting>
</destinations>