|
Home > Archive > BizTalk Server General > June 2004 > HTTP Receive Location, multiple documents
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
HTTP Receive Location, multiple documents
|
|
|
| Hi,
I am going to be receiving a few different XML documents using the HTTP
Receive Adapter in BTS 2004. Each of these document types (obviously) have
their own schema in my VS.Net project. The end goal of the receipt of these
documents is to transform them into EDI and then use the FTP adapter to send
them to a remote server. I have a few questions about the best way to
receive and process these documents.
1) Is it possible to receive all the documents using one receive URL, or
does each document need its own unique receive URL?
2) If they can all be sent to the same URL, should I be using one
orchestration for all the incoming documents, or should each document have
its own orchestration?
a) If I should use one orchestration, how do I break out the document
processing based on the type of document received?
b) If I should be using multiple orchestrations, how do I set up BTS
to call the correct orchestration for each document type?
Any other suggestions for this scenario are welcome and appreciated.
Thanks,
Paul
| |
| Kartik Paramasivam 2004-06-29, 8:44 pm |
| 1) Is it possible to receive all the documents using one receive URL, or
does each document need its own unique receive URL?
messages of different types.
you can even add multiple disassemblers in the disassemble stage of
the pipeline.
2) If they can all be sent to the same URL, should I be using one
orchestration for all the incoming documents, or should each document have
its own orchestration?
[vbcol=seagreen]
orchestration simple then maybe messages of every unique MessageType should
activate a different orchestration. (but it depends on what you want to do)
a) If I should use one orchestration, how do I break out the document
processing based on the type of document received?
[vbcol=seagreen]
> You can access the BTS.MessageType property of the message that is
received in your orchestration.
Based on the value of the MessageType you can do different things.
b) If I should be using multiple orchestrations, how do I set up BTS
to call the correct orchestration for each document type?
[vbcol=seagreen]
type (more exactly BTS.MessageType)
Any other suggestions for this scenario are welcome and appreciated.
Thanks,
Paul
|
|
|
|
|