Message Routing Woes

#12995

Hi all…

I have a scenario where an application publishes XML messages to my Biztalk environment and although the messages contain different details, the structure, including the root name are the same. The messages are name/value pair based and each message has a ‘Subject’ node that tells me what to do with the message, i.e.:

<rootnode>
<header>
<details name=\”Subject\” value=\”Order\” />
….
</header>
</rootnode>

In order to use promoted fields within my orchestrations, I have a pipeline component that transforms the incoming message to a tag based document, so the result of the pipeline is such:

<rootnode>
<header>
<Subject>\”Order\”</Subject>
….
</header>
</rootnode>

Now, I’m new to message based routing, so I need to make sure the incoming document, after transformation, goes to my order processing orchestration, and not a different orchestration as the message root names are all the same.

I’ve read a bit on filters, but the appear to be at the send port level…so hopefully, if I’ve shared enough, what do I need to do to make sure my solutions work?

Thanks!
-Rich