BizTalk 2013 is currently in CTP and you can easily get access to it by setting up a BizTalk server on
Azure. This Article is created to inform you about the new adapters in BizTalk 2013. As BizTalk also moves towards support for the cloud a few handy adapters have emerged, they are intended for Windows Azure Service
Bus entities like Relays, Topics and Queues. Including a brand new adapter to communicate with RESTful services. One of the important adapters the SFTP (both for send and receive). I would also mention that the SharePoint adapter have been updated to provide
the option to use client-side or server-side object models to interface with SharePoint.
The SB-Messaging adapter to send and receive messages from Service Bus entities like Queues, Topics, and Relays. You can use the
SB-Messaging adapters to bridge the connectivity between Windows Azure and on-premises BizTalk Server, thereby enabling users to create a typical hybrid application. The topics in this section provide instructions on how to configure an
SB-Messaging receive location and a send port to receive and send messages from the Service Bus entities.
BizTalk Server 2013 introduces the SFTP adapter to send and receive messages from a secure FTP server using the SSH file transfer protocol. The topics in this section provide instructions on how to configure an
SFTP receive location and a send port to receive and send messages from a secure FTP server.
Microsoft BizTalk Server uses the WCF-BasicHttpRelay adapter when receiving and sending WCF service requests through the
BasicHttpRelayBinding. The WCF-BasicHttpRelay adapter enables you to send and receive messages from the Service Bus relay endpoints using the
Microsoft BizTalk Server uses the WCF-NetTcpRelay adapter when receiving and sending WCF service requests through the
The send adapter sends HTTP messages to a service from a BizTalk message. The receive location receives messages from a RESTful service. For GET and DELETE request, the adapter does not use any payload. For POST and PUT request, the adapter uses the BizTalk
message body part to the HTTP content/payload.
The SharePoint adapter in BizTalk Server 2013 is updated to either use the SharePoint Server Side Object Model (SSOM) or the Client Side Object Model (CSOM). The SharePoint Adapter available with previous versions of BizTalk Server always used SSOM. The SharePoint
adapter with BizTalk Server 2013 adds the option of using CSOM.
Other suggested article to read:
Thank you Howard!