| Shawn K 2006-06-14, 1:18 pm |
| All,
I have inherited a BizTalk 2006 system where we receive EDI
transactions in a single application. The design is such that this will
validate that this is an existing customer and that we accept this
particular transaction from them.
The EDI orchestration will then pass the message along to a custom
application for that partner which has some custom business rules for
that partner and then passes the message on to a standard application
which pushes to our ERP system.
The logic behind this design is that if we add a new customer, we just
update our parties, and add a new custom orchestration for the partner.
No recompile/redeployment of the 2 standard applications or existing
bindings is required.
All applications work fine individually. My problem is that there is
not yet any logic for the first orchestration to communicate with the
appropriate second orchestration. From playing around in VS it appears
that in direct port binding, not only do you have to declare which port
that your receive port is subscribed to, but you have to declare the
receiver in the send port configuration as well. I am seeking to send a
message to multiple receive ports. It appears that the way BizTalk is
designed to handle this scenario is by using Send Port Groups (and then
having the receive locations be smart enough to terminate if the
message is not relevant to them). However, Send Port Groups are
designed to handle External not internal send ports.
The only solution I have so far come up with is to do a file drop to
C:\whatever\%PartnerID%\%MessageID%.xml and have the receive locations
listen to the appropriate locations. This bugs me as I don't think I
should have to have my message leave BizTalk in order to accomplish
this. Is there a way to dump this to the message box and have the
receive locations check the message box and filter on a promoted
property (all filtering seems to be on the send side)?
Also, I am new to the whole BizTalk world except 3 days of training
last December, if you have any websites that you found particularly
helpful, please feel free to share them.
Thanks for your help.
Shawn
|