Home Page › Forums › BizTalk 2004 – BizTalk 2010 › using orchestration as webservice in .net code
- This topic has 4 replies, 1 voice, and was last updated 9 years, 2 months ago by
community-content.
-
AuthorPosts
-
-
February 11, 2009 at 12:51 PM #21703
Hi.
I read about exporting orchestrations as web servies. I thought it sounded like a good idea. Now I’m not so sure. I thought I could just send a file type to the web service call, and it would handle it like when I put the file on the receive path. How is the easiest way to build up the input message and post it, and what about big files and memory issues? Does anyone know any good samples showing realistic solutions?
Thanks for any help 🙂
-
February 12, 2009 at 12:25 AM #21710
You can push the file data from the you .net application as a stream. On the orchestration use untyped messages and build an XmlDocument assign it to you message
-
February 12, 2009 at 1:08 PM #21719
Thanks for the answer. I try to avoid using untyped messages.
I use both flat file and XML messages and it will be much work. Does anyone know
how I can use XML serialization to load XML from a file and “convert” it to the messagetype I have from the webservice and then call the webservice?-
February 16, 2009 at 1:29 AM #21741
Hi,
to do the xml serialization you need to create two applications
1) one web application without user Interface means, if you run it will show the target xml file. (with have URL / Port / own channel )
2) create one window base application to host, we can create window service or simple console application which run 24/7 mode…it will always check the any request has come on the particular URL / Port / channel …then this host application take the input xml file and do the pocess and return the new xml file which will match with your type message
-
-
-
February 16, 2009 at 1:39 AM #21742
you can publish your orchestartion as webservice using viward…but remenber some ponts
1) virtual directives must be highly isolated. if you do this OS will automatically create one component service.
2) receive port use as RAR because if you publish orchestration as web service ..receive and send will be mane port
3) Disable the retry method inside orchestration send port ow application performance will goes down
4) use Delivery notification = trasmited
Regards – suman kalyan betal
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.