Re: Custom pipeline in a Orchestration webservice

I would suggest you to just open up the source code of the webservice
generated by the orchestration publishing wizard and tweak it to accept the
other message and implement your transform functionality.

--
Regards
Benny Mathew
Seamless Integration Solutions
BizTalk Consulting, Development, Training
Bangalore, India
http://www.seamless.in
http://GeeksWithBlogs.net/benny
"BizTalk 2006 Guru" <someone@xxxxxxxxxxx> wrote in message
news:4EF1930D-E382-49E1-AC18-3E8EF7DF9AFF@xxxxxxxxxxxxxxxx
Hi all,

I have written a custom pipline which gets a transformation from the
database and makes a transformed message from request xml. pieline's
transformed measseg is of namespace "http://TestOR";.
In Orchestration my Receive shape receives the message type
"http://TestOR";.
What happens when i drop a message of namespace type "http://abc";. My
Custom
pipeline invokes and tranform this "http://abc"; message into
"http://TestOR";
before message recahes to Receive port.
In physical port i am setting my pipeline as receive piepline.
This scenario works fine when the case i hard coded file ports.

But when i publish this Orchestration as a webservice. the service exposes
"http://TestOR"; as a input message type. Publishing wizard exposes receive
shape mesaage type but i want to expose "http://abc";.

So my question is how to tackle this problem so that my custom pileine
invokes automatically in webservice case as well.

--
BTSGuru


.

Relevant Pages

  • Re: Custom pipeline in a Orchestration webservice
    ... This happens because the webservice is based on the message type received by the 'logical' orchestration port. ... Make sure the webmethod name in the webservices matches the operation name in the orchestration because that is used for the subscription. ...
    (microsoft.public.biztalk.general)
  • Re: Custom Pipeline Subscription Issue
    ... Open the Schema associated with that message type and see what's the value ... > a custom pipeline that strips off an email header with the disassembler. ... > back to the enginefor processing to and Orchestration. ... > message properties necessary for subscription evaluation have not been ...
    (microsoft.public.biztalk.general)
  • Re: Consuming BizTalk webservice
    ... The web service exposed by your orchestration is not different from any other webservice. ... In your orchestration case the parameter you pass will be the message, from a XSD schema which is equivalent to a complex type in ..NET. ... Say for example a webservice is expecting an object of type Employee, then the client application needs to construct that object and pass it as a parameter, which will eventually get serialized in the wire format and transmitted to the webservice. ... calls all want this object of "rootNodeName" type. ...
    (microsoft.public.biztalk.general)
  • Re: BizTalk reruns orchestration endlessly on throwing exception
    ... Its weird though isn't it how something as simple as a full event log can ... affect BizTalk in some pretty bizarre ways? ... > We solved it by checking message type to ensure it would only map if the ... >> I noticed that when my orchestration throws a SystemException BizTalk ...
    (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)
Loading