BizTalk : Defining multiple database ReceiveLocation with same db connection string

BizTalk : Defining multiple database ReceiveLocation with same db connection string

BizTalk does not allow us to create the multiple receive location with Same URI, At design time it validate the URI and if it matches with any receive location then it throw Validation error.

But there may be some requirement where we might need multiple receive location with same URI like multiple database receive location with same database URI and each polling to different set of data (different stored procedure/package.)

So for this requirement, we can implement the multiple receive location with different pollingid. So at design/run time it won’t throw any validation error as the URI is different. The connectionstring with PollingID really doesn’t make any difference and it won’t create any issue while connecting database.

Ex . If I have two receive location polling database

ReceiveLocation1 -> URI -> oracledb://goDEV1/?PolllingID=1111

ReceiveLocation2 -> URI -> oracledb://goDEV1/?PolllingID=2222

ReceiveLocation3 -> URI -> oracledb://goDEV1/?PolllingID=3333

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