EDI Applications

I'm in the process of designing my application structure and have many questions regarding BT 06 and application structure when there are many partners in general. I also have a question regarding EDI application as well.

In our existing 02 solution, we have one file receive location which is where all edi documents of all types(850, 867 etc) from all partners are dropped. Biztalk 2002 sweeps that location, applies some custom pre-processing via a custom AIC component to the inbound edi document and it is submitted. Biztalk internaly determines the channel based on sender/receiver information and the message is on the correct execution path in the system.

In 06, the concept of channel is gone so it seems I'd need to approach this one of two ways:

1. Create a an EDI application in BT administration that has one receive location, this receive location would have every schema and map for our EDI partners associated with it's receive port.

This would be problematic in my scnerio in that I have many partners that use EDI I could potentially have 1000's of maps associated with the port. Ther are too many issues to list here.

2. Use the recommended approach, application per partner, and have a specific receive location for EDI per partner. This would alleviate the problems in option 1 but I would need to figure out how to get documents to the right receive locations. Currently all of our external partners dump their EDI documents to one folder. Seems like I'd need a sweep preprocessor to rifle through the directory, determine who it came from and send it to the right receive location tied to a partner app. Or I could use BT itself with sendports to do this.

Just curious as to the recommended set up for EDI applications in a many partner scenario

Thanks,

C

[1856 byte] By [mitre] at [2008-2-7]
# 1

I would go with approach (2). Have 1 receive location for all the partners, and use the loopback mechanism to transport the incoming file to the right receive location tied to a partner app. This would require some custom logic as to determine which document belongs to which partner etc. Once you have determined the document/partner relationship, just use a pass through receive and send pipeline to transmit the document to the right folder (the loopback) and pick the document from that folder for processing.

Thanks

Mohsin

MohsinKalam–MSFT at 2007-9-26 > top of Msdn Tech,BizTalk Server,BizTalk EDI and AS2...
# 2

Thanks for the reply,

In regard to having all of the EDI documents dropped in one place, I was thinking I'd just have a service external to biztalk which opens these files, figures out where it needs to go by a quick inspection of the Sender segment then dispatches the document to the appropriate partner receive location. I am a bit worried that this will effect speed of processing if the EDI doc is large. Seems like I'll basically be introducing a bottleneck in having to do this.

Curious as to how this loopback mechanism would work? Where would I use custom code and wouldn't I still have an issue with large documents?

mitre at 2007-9-26 > top of Msdn Tech,BizTalk Server,BizTalk EDI and AS2...
# 3
If your sender parties are different only by ISA06 and GS02 elements (It's not always happened), the EDI system give you all context parameters to separate the sender parties.
The EDI system could parse all input messages to the message box where your one or many apps take the messages routing them by ISA06 and GS02.
LeonidGaneline at 2007-9-26 > top of Msdn Tech,BizTalk Server,BizTalk EDI and AS2...