I need to connect a legacy system with COM-capabilities to a BizTalk
2004. I need some kind of request-response pattern, otherwise I would
just write to a file...

Can you make a suggestion about how to implement this?

Sincerely,
Per F Pedersen

[ Post a follow-up to this message ]

Look at the submit direct sample in the SDK. Wrap the submit part for COM
interop.

"Per-Frode Pedersen" <perfp@hotmail.com> wrote in message
news:27c233fe.0403160247.3efa7dd3@posting.google.com...
> I need to connect a legacy system with COM-capabilities to a BizTalk
> 2004. I need some kind of request-response pattern, otherwise I would
> just write to a file...
>
> Can you make a suggestion about how to implement this?
>
> Sincerely,
> Per F Pedersen

[ Post a follow-up to this message ]

I suspect it's a bit late to answer, but just in case...
If your legacy system is on a separate box than BizTalk, then you anyway
will need some transport - HTTP, webservice, MSMQ, or, like you suggested,
file on the share. File is the simplest if you are ok with quality of
service that file transport can provide - share can be easily disconnected
on one of the ends so it's not very reliable transport over network.
Regards,
Eldar


--------------------[vbcol=seagreen] 
microsoft.public.biztalk.general,microsoft.public.biztalk.server[vbcol=seagreen] 
10:47:45 GMT)[vbcol=seagreen] 
cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onlin
e.de!newsfeed.gamma.ru!Gamma.RU!newsfeed.icl.net!newsfeed.fjserv.net!logbrid
ge.uoregon.edu!hammer.uoregon.edu!news.glorb.com!postnews2.google.com!not-fo
r-mail[vbcol=seagreen] 
microsoft.public.biztalk.general:13248[vbcol=seagreen] 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]