Send port proliferation
- From: devMonkey <mitre7@xxxxxxxxxxx>
- Date: 26 Apr 2007 13:54:43 -0700
Hi,
I am confused regarding the term "Send port proliferation". I've been
told I will have this problem with the design I am attempting to
implement in 06 but I am unclear as to how it is a "problem".
In my current 2002 solution, we have >500 partners with up to 11
document types per partner, trading with up to (n) other partners,
with any of the three common document formats (EDI, FF, XML). To cut
down on the amount of channels/ports required for a many to many
scnario, we have set ourselves up as a middleman between inbound and
outbound processing. In a nutshell, all inbound documents, of any
format, get mapped to one of our 11 canonical doctype xml ( and
processed generically based on the inbound doctype) basically we have
a custom AIC process specific for each of these inbound types. We act
as the receipient for all inbound documents. Once the document has
had rules applied to it in it's process, the code determines the
original intended recipient, sets us as the source and the message is
submitted back to Biztalk where the appropriate destination specific,
document type specific channel is located for maps to be applied and
the correct transport for transmission.
As you can imagine, we have a ton of outbound channels to facilitate
the configurations of the different partners for their transports. So
partnerA may have channels for PO going to FTP, a channel for POAck
going to a file etc etc. I don't really see a way around this since
configurations will differ amongst different destination partners even
though they use the same transport mechanism.
In my 06 design, each current AIC process will be an orchestartion
with direct binding for send ports. I will undoubtably have allot of
send ports to support what we do today as I'll need to set a send port
for subscription for each trading partner/document type combination
and possibly other filters. I've looked at dynamic ports which would
cut down the number of send ports but it falls short in other areas,
namely ease of runtime configuration.
Is this a concrete problem in that I'll run into some sort of physical
limitation on send ports or that Biztalk will run dog slow at some
point? Is this just terminology used to describe a solution that has
many sendports? Again, we do not have any problems in our 02 solution
with well over 3,000 channels, each channel has transport
configuration information for that destination partner.
.
- Prev by Date: Send Port Proliferation
- Next by Date: Re: Missing content in file
- Previous by thread: Send Port Proliferation
- Index(es):
Relevant Pages
|
