Issues: The type or namespace name does not exist in the namespace in orchestration. Reason: When we have start building solution and add orchestration. And after
Category: Orchestration
Calling a .net component from BizTalk orchestration
This blog is to explain how to call C# components from BizTalk. I am going to explain this scenario by taking simple example like Addition
BizTalk Sequential Convoy
This blog is to explain about BizTalk Sequential Convoy. What is Sequential Convoy? Sequential Convoy is one type of BizTalk design pattern to achieve particular
BizTalk Parallel Convoy
This blog is to explain about BizTalk Parallel Convoy. What is Parallel Convoy? Parallel Convoy is one type of BizTalk design pattern to achieve particular
BizTalk Correlations
This blog is to explain about BizTalk Correlations. What is Correlation? Correlations can be defined as binding incoming messages with the appropriate instance of an
BizTalk Logical Ports & Port Bindings
This blog is to explain various ports and port Bindings in Orchestration. There are two types of ports in BizTalk. Logical Ports: Ports which are
BizTalk Orchestration Shapes
This blog is to describe briefly on various Orchestration shapes. Receive: Receive shape is used to receive the incoming xml message from message box using
Create First BizTalk Orchestration
Requirement: I need to drop a sample Xml message in a folder location. Sample Input Xml message: <ns0:AppraisalInput xmlns:ns0=”http://SampleBTApp.AppraisalInputSchema”> <EmpNo>EmpNo_0</EmpNo> <EmpName>EmpName_0</EmpName>
