This project is read-only.
When raising an Issue, please ensure you attach the log file created by the adapter having set tracing to verbose in the BTSNTSvc.exe.config file

The TCP/IP Adapter for BizTalk Server 2006/2009

This adapter implements an in-process adapter for BizTalk Server that uses the raw TCP/IP socket library to pass messages between BizTalk Server and remote clients.

On top of supporting the basic BizTalk Server message exchange patterns, it also supports a mode called Duplex whereby a client can initiate a connection with the adapter where it then allows two way traffic down the one connection which can remain open for as long as is needed.

The adapter sends and receives raw data over TCP sockets and uses only a minimal protocol to determine message boundaries. This is known as message framing and is fully configurable.

In addition, the adapter supports sending and receiving data that has been encoded using practically any code page supported by Microsoft Windows and version 2.0 of the .NET Framework. On receiving data, the adapter converts the data using the configured encoding to UTF-8 and on sending, the adapter converts the data from UTF-8 to the appropriate configured encoding. The same applies to the message frames that bound the message, except where they are configured as a raw binary format.

The adapter supports the following message exchange patterns.
  • Request Only Messages are sent to BizTalk that can be routed by BizTalk to any orchestration or send port.
  • Request-Response Messages are sent to BizTalk and the appropriate response is returned to the adapter by BizTalk which is then sent back to the remote client.
  • Solicit Only Messages are sent from BizTalk to a remote client.
  • Solicit-Response Messages are sent from BizTalk to a remote client and that remote client returns a response to BizTalk which it can then route appropriately.
  • Dynamic Solicit A send port can be set to be a dynamic send port that receives its destination address at run-time rather than being statically configured on the port. The adapter supports the use of the tcp:// prefix with two different URI styles depending on whether the send port supports sending the data over a duplex connection or not.
  • Duplex Request A connection request to a duplex supported receive location allows message traffic from the remote client and to the remote client down the same initiated connection. The adapter sets the initiated connection address on a BizTalk Party that has an alias that matches the DNS name or IP address of the remote client.
  • Duplex Solicit Messages are transmitted to the initiated connection to be returned to the remote client. It resolves the initiated connection against a BizTalk Party that has been updated with the appropriate duplex listener address.

Last edited Jul 13, 2009 at 9:29 PM by jplummer, version 6