BizTalk Document Mapping – Organizing Maps
If you are dealing with large maps, they can become very complex and therefore very difficult to maintain and read To minimize this problem, BizTalk Server
Introduction BizTalk Document Schemas – Part II
Schema Namespaces Has posted before (link), BizTalk Server uses a combination of Namespace + Root Node name to identify and resolve schemas
Basics of BizTalk Runtime Architecture
BizTalk runtime architecture primarily has four major components: Receive Handler;Message Box;Orchestration;Send Handler Receive handler Receive
How To import Add Reference from WSDL file
WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented
Introduction BizTalk Document Schemas
The XML Schema Definition (XSD) language natively defines message structure in BizTalk Server XML Schemas are the foundation of all scenarios and document
How to schedule an orchestration (BizTalk 2004, 2006 or R2)
How can we schedule an orchestration to run at predetermined time intervals or to start in a predetermined hour You have 3 possible ways to do
BizTalk Dynamic Send Port – How to implement retries, delivery notification and backup tran...
If you are using dynamic ports inside an orchestration, you have to configure BTSRetryCount and BTSRetryInterval properties on the message you want to send to
Multi-Part message – “use of unconstructed message ” – Error message when...
Sometimes when we try to build or deploy BizTalk solution, you may get the following error message: “Use of Unconstructed Message 'MessageName'” I
‘System.String’ must be Xml serializable to be a message part type
Sometimes, when I try to build my project I get the following compile-time error: "'SystemString' must be Xml serializable to be a message part type --
There was a failure executing the receive pipeline: Microsoft.BizTalk.DefaultPipelines… failed to...
Sometimes, when we try to test our Visual Studio BizTalk Server solution that we deploy in the BizTalk Server environment, we get the following error