Using XmlSerializer in the BizTalk Web Service Proxy.

This is something that most people will be aware of but might be helpful for newbies. The BizTalk Web Services Publishing Wizard, creates new datatypes for input and output messages during creation of the Web Service that exposes Orch/Schemas. Adding a web reference to this web service will generate the same datatypes, whose definitions can be found in the Reference.cs file. If the external system already generates XML, creating the input message object can be a drag.
A quick way of creating the input message objects from XML and converting the output message objects to XML, is by using the XML Serializer class. Here's the sample code.

//creating a new RequestMsg
objectRequestMsg objRequestMsg = new RequestMsg();

//Create an XML Serializer for RequestMsg document
XmlSerializer serRequestMsg = new XmlSerializer(objRequestMsg.GetType(), "http://schemas.devdutt.com/XMLSchema/v1/InputMsg.xsd");

//Deserializing XML into RequestMsg class
//strRequestMsgXml is the XML String
objRequestMsg = (RequestMsg)(serRequestMsg.Deserialize(new XmlTextReader(new StringReader(strRequestMsgXml))));

//Call RequestMsg Web Service and send the Request
//orchInvoker is the Web Service Proxy Object
//Submit is the Web Method
object obj = (orchInvoker.Submit(objRequestMsg));

//Create an XML Serializer for OutputMsg document
XmlSerializer serResponseMsg = new XmlSerializer(obj.GetType(), "http://schemas.devdutt.com/XMLSchema/v1/OutputMsg.xsd");

//Create a temporary memory object for storing xml stream
MemoryStream ms = new MemoryStream();

//Serialize the output document
serResponseMsg.Serialize(ms, obj);

//Convert the memory stream into the string buffer
string strResponseMsgXml = System.Text.Encoding.ASCII.GetString(ms.GetBuffer());

Any questions, post a comment.


Comments

Post a Comment

Popular posts from this blog

Sending Messages as FORM Variables with the HTTP Adapter

Image
Here's a quickie. If you want to send a message, as a FORM Variable in a HTTP request, this is what you do: 1) Set the Content Type property of the HTTP send port, to application/x-www-form-urlencoded . 2) Create a custom pipeline and plug-in a Custom Pipeline Component, that pre-pends Variable-Name = in front of the message, and url encode it. e.g: ClaimPacket= 3) Use this pipeline with your HTTP send port, and you are done! Post a comment for a sample. Update : Screen shot of the Content Type property:
Read more

Using recursion in the In-line XSLT Template type Scripting Functoid

People using In-Line XSLT Templates in their scripting functoids often run into the need for looping, WITHOUT using an <xsl:for-each> . An example in the BizTalk context would be, if you had a comma separated string in the source schema and wanted to tokenize it into multiple destination schema elements. The following XSLT template does that for you. <xsl:template name="TokenizeCommaSepString"> <xsl:param name="stringToTokenize" /> <xsl:param name="destinationElementName" /> <xsl:if test="$stringToTokenize != ''"> <xsl:choose> <xsl:when test="contains($stringToTokenize, ',')=0"> <xsl:element name="{$destinationElementName}"> <xsl:value-of select="$stringToTokenize" /> </xsl:element> </xsl:when> <xsl:otherwise> <xsl:element name="{$destinationElementName}"> <xsl:value-of select="substring-be
Read more

Uniform Sequential Convoys in BTS 2004 using Correlation

This orchestration is a small primer if you want to implement a "Sequential Convoy " with BizTalk 2004. You would want to do this if: a) You have to force messages coming in at a particular port to correlate together and get processed by the same orchestration instance. (Correlation with multiple ports is a topic of a subsequent post) b) You want your output messages to be delivered in the same order that the orchestration got them. c) Some pipeline components you use, take one message but give out multiple messages, but you want to process these multiple messages together. For eg: the HIPAA and HL7 disassembler components. ...and probably some more scenarios that I can't think of right now. The attached orchestration correlates messages w.r.t ReceivedFileName (think about the HIPAA 835 scenario mentioned above). You can use whatever correlation parameters you desire. TIP: Whatever properties you choose to correlate the incoming messages with, make sure tha
Read more