Since Filespooler is an ordered queue processor by default, it normally insists on a tight mapping between the sequence numbers in job files and execution order in a queue. This poses challenges when you want to send data from multiple sources to a single destination. There are two main strategies for doing this: On the receiving side, maintain a separate queue for each origin. This is quite easy to do, since Filespooler queues are very lightweight.
