Feeds:
Posts
Comments

Archive for May, 2008

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 [...]

Read Full Post »

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

Read Full Post »

Steps to validate:
1) Check if the SQL Server Agent is running

2) Ensure the TrackedMessages_Copy_BizTalkMsgBoxDb job is running

3) Enable tracking on the port
a) E.g: I would like to enable message tracking on one of my Receive ports. In this case it is SQL Adapter

(i) RcvCashTransactions_SqlPort: Name of the SQL port
(ii) Request message before port processing: [...]

Read Full Post »

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= [...]

Read Full Post »

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 [...]

Read Full Post »