Developing BizTalk Applications

Developing BizTalk applications involves creating a BizTalk project in Visual Studio 2005 and using the Consume Adapter Service BizTalk Project Add-in to generate XML schema. Once you have generated the schema, you can either use Content-Based Routing (CBR) or create BizTalk orchestrations to send and receive messages that conform to the generated schema.

CBR can be used in scenarios where the messages being sent to the SAP system do not require any intensive processing. For example, if you know that the receive port will be receiving messages only of a certain type, you can add a filter to the send port to route the messages matching the filter expression to the send port. For more information about CBR, see "Content-Based Routing in BizTalk Explorer" at http://go.microsoft.com/fwlink/?LinkId=102492.

In BizTalk orchestrations, you create send and receive ports to send and receive messages to and from the WCF-Custom adapter, which in turn sends the messages to BizTalk Server. This section provides information about using BizTalk orchestrations to perform operations on the SAP system using the SAP adapter. The SAP adapter in turn uses the WCF-Custom adapter, which can interact with a WCF binding. For more information about BizTalk orchestrations, see "Orchestration Management in BizTalk Explorer" at http://go.microsoft.com/fwlink/?LinkId=102493.

Cc185312.Important(en-US,BTS.10).gifImportant
To use the SAP adapter with Microsoft BizTalk Server 2006 R2, you must always set the EnableBizTalkCompatibilityMode binding property to True. For information about how to set binding properties, see Specifying Binding Properties.

Cc185312.Important(en-US,BTS.10).gifImportant
Unlike the earlier version of the adapters shipped with BizTalk Server, the SAP adapter shipped with BizTalk Adapter Pack does not show up in the list of adapters in the BizTalk Server Administration console. This is because the latest SAP adapter is a WCF custom binding. So, while the BizTalk Server Administration console displays the WCF-Custom adapter, it does not display the WCF custom bindings and hence, does not display the WCF-based SAP adapter.
Also, to generate metadata you must use the Consume Adapter Service BizTalk Project Add-in and not the Add Adapter Metadata Wizard, as used for the previous version of the adapter. For instructions on using the Consume Adapter Service Add-in, see Retrieving Metadata for SAP Operations in Visual Studio. For more such differences between the adapter versions, see Migrating BizTalk Projects Created Using the Previous Version of the SAP Adapter.

Other Resources

Development

Show: