BizTalk : Accessing context/Promoted properties within maps.

BizTalk does not provide any asset or control using which we can use Context/Promoted property in maps. It say instead of using specific field of message use entire message as source input to map.

Promoted Property : This property are used for content based routing, If we want to use any schema field outside the Orchestration then we can promote that field. Once the property is promoted It will be accessible outside the Orchestration like in send port filter. Based on this promoted property we can make required routing decision.

Now, If some specific design/development require a Context/Promoted property value in the map then for this case we need to implement a custom functoid to read a Context/Promoted property value. We can use the following link dll and refer to this project, This link exactly explain how to do this. Instead of developing custom functoid we can use the dll shared on CodePlex and blog.

http://contextaccessor.codeplex.com/SourceControl/changeset/view/69709#37096

- download dll

http://blogdoc.biztalk247.com/article.aspx?page=ed7266cf-73de-46c4-8017-c2d162b57d01 - project explained here

Thanks to BizTalk247 and Codeplex.com

Comments

WCF MaxReceivedMessageSize max value in .config

MaxReceivedMessageSize parameter in binding config file: For max file size in WCF, we need to set following parameter in binding files. <binding name="MyService" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" transferMode="Streamed" > <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/>  </binding> Max possible size: MaxReceivedMessageSize to 2147483647 (i.e. Int32.MaxValue), which is 2GB For our case, as we are using WsHttpBinding. <wsHttpBinding> <binding name="wsHttpBindingSettings" maxReceivedMessageSize="2147483647"> <readerQuotas maxDepth="2147483647" maxStringContentLength

Object Oriented Programming Concepts

OOP Basics Visual Basic was Object-Based, Visual Basic .NET is Object-Oriented , which means that it's a true Object-Oriented Programming Language . Visual Basic .NET supports all the key OOP features like Polymorphism , Inheritance , Abstraction and Encapsulation. It's worth having a brief overview of OOP before starting OOP with VB. Why Object Oriented approach? A major factor in the invention of Object-Oriented approach is to remove some of the flaws encountered with the procedural approach. In OOP, data is treated as a critical element and does not allow it to flow freely. It bounds data closely to the functions that operate on it and protects it from accidental modification from outside functions. OOP allows decomposition of a problem into a number of entities called objects and then builds data and functions around these objects. A major advantage of OOP is code reusability. Some important features of Object Oriented programming are as follows: Emphasis on

biztalk schema remove ns0 prefix

We can remove ns0 prefix simply by set the schema elements property or both elements and attributes properties to be qualified. To do that follow my steps: 1- Open your schema 2- Right Click <Schema> and select properties 3- Use schema property editior and Set [Element FromDefult] to Unqualified , and then set [Attribute FromDefault] to Unqualified if you are using attributes in your schema. After applying the steps above, both XML instances below will be valid: Instance 1 (with ns0) < ns0:Root xmlns:ns0 = " http://RandomBizTalkProject.Schema1 " > < Field1 > Field1_0 </ Field1 > < Field2 > Field2_0 </ Field2 > </ ns0:Root > Instance 2 (without ns0) < Root xmlns = " http://RandomBizTalkProject.Schema1 " > < Field1 > Field1_0 </ Field1 > < Field2 > Field2_0 </ Field2 > </ Root >

Learn, Troubleshoot BizTalk with Ashok Rajpurohit

Search This Blog