Hi Anon,
It would be possible to write each output message to an individual folder, however I would probably question why you want to do that – maybe there is a better design for your solution?
If you still need this functionality, I would recommend setting the SourceFileName context property of the message before it leaves an orchestration as follows:
outputMsg(FILE.SourceFileName) = "C:\OutputFolder\Somewhere\"+ System.Guid.NewGuid() +".xml";
and then using a custom encoding pipeline component on the send pipeline to read the SourceFileName property and create the directory structure if it doesn’t exist. If you then use a FILE adapter, the file should be delivered to the correct directory.
Hope that helps, Nick.