This scenario shows how SAP can be integrated using the Trivadis Integration Architecture Blueprint. We are making an exception in this case by considering a specific product as a candidate for integration, identifying the corresponding integration platforms, and including them in the scenario. By doing this, we can show how the Integration Architecture Blueprint is used in practice, using some vendor products for the building blocks.
The image below shows how an orchestration using Microsoft BizTalk and SAP can be combined. On the one hand, a simple SAP service is accessed using a Remote Function Call (RFC), and on the other hand, an SAP business process is implemented using the SAP Exchange Infrastructure (SAP XI) to access the SAP system. The SAP business process is callable as a service and is used from the BizTalk orchestration.
Trigger:
- The application sends an SOAP request.
Primary flow:
- The SOAP request initiates a new instance of a BizTalk process.
- The process either implements a call directly in SAP in the form of an SAP RFC call, or starts another business process which is made available by SAP XI through an SOAP call.
- The SAP XI business process is initiated and sends two calls to the SAP system. One takes the form of a SAP RFC call, and the other uses a web service interface made available by SAP.