Orchestration exposed as a web service and envelope schema



Hi everyone!
I have the following scenario: I have an orchestration wich receives a
message through a custom pipeline with an envelope and document schema
dissasembler. Now I want to expose this orchestration as a web service. The
behaviour I'm looking for is sending the envelope throug the Web Service
call and expecting the pipeline to split the envelope into several messages
and route each one to the corresponding orchestration.
Is it possible to achieve this behaviour through an exposed orchestration?
How?

Thanks in advance!


.



Relevant Pages

  • RE: Biztalk 2006 & POP3
    ... The subject line can be taken directly from the message context properties ... You can receive the entire message within the orchestration as a multipart ( ... iam getting an error if i use custom pipeline as the link provided ... So i went for custom pipeline approach, wherein i should set mime type to ...
    (microsoft.public.biztalk.general)
  • Re: Custom Pipeline Subscription Issue
    ... When you have a receive shape in your orchestration with Activate=true, ... Enlisting the orchestration will automatically create a subscription ... "Name=Saravana".(You promote this property in your custom pipeline). ... >> specified the Message type. ...
    (microsoft.public.biztalk.general)
  • Orchestration exposed as web service and envelope schema
    ... message through a custom pipeline with an envelope and document schema ... Now I want to expose this orchestration as a web service. ... Is it possible to achieve this behaviour through an exposed orchestration? ...
    (microsoft.public.biztalk.general)
  • Re: Best Practices for receiving large files
    ... Just to make sure your message pass through BizTalk without any issues in first place try sending the message to a send port directly without any orchestrations in between. ... I won't go down the custom pipeline component route for your situation, since you need to be very precise on handling the streams inside the component especially on large message situation. ... The reason why XmlReceive is used is to promote MessageType context property to which the orchestration will be subscribed, you can get the message into orchestration by some other filtering. ... would the custom pipeline extraction of the ...
    (microsoft.public.biztalk.general)
  • RE: Orchestrations not starting
    ... We are using a custom pipeline with the BizTalk Framework Disassembler. ... The receipt piece is working but the orchestration is not kicking off. ... message context to be subscribed to by an orchestration (usually by the ... You're not getting an subscription errors in the event log? ...
    (microsoft.public.biztalk.general)

Loading