Hi,
Here is a high level overview of what I need to do
[quote:74dfeb6fbb]I have an incoming message. Could be either a flat file or XML. I want to take this message (untouched) and call another orchestration which will disassemble/map/… this message.
The other orchestration is unknown at design time but is in fact looked up at runtime.
I also need to send additional information along with this message to that other orchestration.
I cannot touch (actually, I don’t know anything about the original message nor it’s schema) the original message’s schema in order to create distinguished fields or properties.
[/quote:74dfeb6fbb]
My thought is to create a seperate schema which will hold the additional information in distinguished fields and then pass that along with the original message. This newly created message will have unique information for the original message.
So…
How can I send two messages to a single orchestration? And how can I ensure that each incoming message has a unique generated message?
If I am unclear, please post and I will try to expand on my description.
Thanks
Scott