Policies and skills in BizTalk Adatper for Web Service

In the EAI solution using BizTalk Adapter for Web Service, different and separated components are integrated to complete unified business logic. In the solution, various components must work together well. There are two key principle principles to make your BizTalk solution more perfect:
KP1: each step of implementation is tested when a solution is built;
KP2: the front end of the cluster starts to push to the backend, or the end of the cluster starts to push to the front end, step by step for incremental development. Each step of incremental development must ensure that the post-incremental solution can be used.
The following describes the skills and provides guidance.

1. Back-to-Front Strategy
Policy from backend to front-end
When using the BizTalk Adapter for Web Service solution, it is a good strategy to start from backend development. Because this solution usually implements complex service programs by providing Web Method interfaces. At the beginning, the first thing is to check the backend process in an environment other than BizTalk Server ). If you can perform an independent test (stand-alone test), it is a good method.

1.1 Component Tactics
Component skills
In practice, you need to test the components before they are assembled into BizTalk. The following are some optimization suggestions and troubleshooting (troubleshot) suggestions:
If you use XLANG Schedule to connect to the backend process, you can use the COM component as a bridge. COM components can be third-party adapter components or custom components. In either case, perform test control, for example, use Visual Basic scripts for a unit test.
If you use the messaging port to connect to a third-party component or custom AIC at the backend, creating a test using the Message port and channel is much better than using Visual Basic script for testing. The following describes how to create a test Message Port and channel:
1) create a Message Port (Template) using AIC as the transmission port (transport );
2) The channel can use null documents as the source and target documents without the need for map definition.
3) Use BizTalk Editor to generate a legal implementation (instance) document;
4) rewrite the SubmitSync. vbs copy so that the document is submitted to the channel described above;