HTTP Receive Location, multiple documents
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > BizTalk Server > BizTalk Server General > HTTP Receive Location, multiple documents




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    HTTP Receive Location, multiple documents  
PBR


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-29-04 10:52 PM

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







[ Post a follow-up to this message ]



    RE: HTTP Receive Location, multiple documents  
Kartik Paramasivam


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
06-30-04 01:44 AM

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






[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 12:44 AM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register