How do you self route inbound documents in BTS 2004 1

[fheinema]

We are currently setting up our BizTalk 2004 environment. We have one trading partner dropping 4 different types of XML documents to the same location. The file names do not differentiate what type of document it is. Each document type has different processing requirements. One needs a service window another needs mail notifications sent and all have separate maps. We had this working in BizTalk 2002 using self-routing. I cannot figure out how to mimic this in BizTalk 2004. Any help is appreciated.

Fred Heinemann

 

[SgtPeppa]

Well, I dont know about your solution but BTS 2004 is working with subscriptions! So you could set up on Receive-Port and a ReceiveLocation to pick up all the Files! Then have a custom Pipeline validate against a group of schemas! (IN total 4 in your solution)

All Messages will then be placed in the BTS Message Box. From there all you need to do is work with the BTS2004 Subscriptions to route your Document to the correct Orchestration / Send Ports.

Does that help?

Stephan

 

[fheinema]

Stephan,

I built this and it worked but I encountered one glitch that I cannot figure out. Some sort of endless loop has started and the files keep writing out. I have the receive port and location, the pipeline which writes it outo the message box, then I use filters to have the orchestrations pick up the files. The orchestration uses a plain old file adapter to write the file to a directory. Do you have any idea what would cause an endless loop? The initial file is being removed from the directory so it is happening internally.

Fred

 

[SgtPeppa]

Hard to tell from your description! Sounds to me like a mistake in the Subscriptions.

Did you use any further subscriptions in your Orchestration? Or did you just bind it to your receive location? That should actually be enough! Just create your four Orchestrations, and then bind their logical Ports to your phisical ports! That should be enough!

If that does not help, can you upload your solution somewhere for me to have a look at?

Stephan

 

[fheinema]

Thanks for the response. I figured out what was happening. I am using a direct port to pick up the message from the message box. Then translating it but spitting out a message that uses the same XML format. Since the outbound messages end up routing through the message box before writing out they are getting picked up again. Back the drawing board. Thanks for your assistance.