Passing parameter from an Orchestration to the BizTalk Rules engine
In my BizTalk 06 project, the intention was to create a set of rules. These rules would be based on a Schema. From my orchestration, I wanted to pass this schema to my Rules engine that would perform some mapping on it and return me back [...]
Archive for May, 2008
Passing parameter from an Orchestration to the BizTalk Rules engine
Posted in BizTalk 2006 R2, tagged BizTalk Rules Engine, Integration, Passing parameter from an Orchestration to the BizTalk, Zeeshan Shah on May 11, 2008 | 7 Comments »
BizTalk 2006 Adapter Pack
Posted in BizTalk 2006 R2, tagged BizTalk 2006 Adapter Pack, Integration, Zeeshan Shah on May 8, 2008 | Leave a Comment »
BizTalk Adapter Pack
This is an intresting read from Richard. He talks about the newly released BizTalk Adapter Pack and highlights a standard data query use case. Click here
An error occurred when parsing the incoming document…
Posted in BizTalk 2006 R2, tagged An error occurred when parsing the incoming document, BizTalk, The column where the error occured is 51.". ", Unexpected data found while looking for: '\r\n', Zeeshan Shah on May 8, 2008 | Leave a Comment »
Error: “An error occurred when parsing the incoming document: “Unexpected data found while looking for: ‘\r\n’ The current definition being parsed is Root. The stream offset where the error occured is 100065. The line number where the error occured is 41. The column where the error occured is 51.”. “
Solution: In the schema set allow_early_termination= [...]
Visual studio shuts down when a Map assembly tries to reference the Schema assembly
Posted in BizTalk 2006 R2, tagged BizTalk, IDE, Visual Studio, Visual studio shuts down when a Map assembly tries to r, Zeeshan Shah on May 8, 2008 | Leave a Comment »
This would purely happen due to the assembly length. In my case, the map assembly was named as COMPANY.DIVISION.TECHNOLOGY.FUNCTION.Maps and the Schema was named as COMPANY.DIVISION.TECHNOLOGY.FUNCTION.Schemas.
When the maps assembly references the schema project – BizTalk, behind the scene creates a type reference as [COMPANY.DIVISION.TECHNOLOGY.FUNCTION.Maps> + + COMPANY.DIVISION.TECHNOLOGY.FUNCTION.Schemas].This in turn becomes lengthy for the BizTalk [...]