Description

Application-to-application integration

With the help of application-to-application (A2A) integration you can exchange transactional data along internal company processes by connecting involved business applications in a (near-) real-time fashion. Messages are used for exchanging transactional data which trigger the execution of the next process step in a connected business solution. Transactional data refers to data about ......

API managed integration

Application Programming Interfaces (APIs) enable integration, interoperability and data sharing between software systems. With the help of an API management solution like the API Management capability within SAP Integration Suite you can provide omni-channel and secure access to solutions. Furthermore, it allows you to enforce usage policies for APIs, controlling API access, analyzing API consumption and more. This reference architecture is based ........

Characteristics



Flow by Integration Domains 

Flow (Case by Case flow ie Cloud2OnPrem)

Services and Components

Flow (Case by Case flow ie Cloud2Cloud)

Services and Components





Full blueprint




Flow (Complete flow)

In the following the message flow for application-to-application integration is outlined:


  1. Direct exchange of messages is possible whenever the outbound API of the sending solution and the inbound API of the receiving solution are aligned with regards to the API definition   You can also use the direct integration option for custom-build or partner solutions if these are also based on aligned APIs.

  2. In case of unaligned APIs between a sending and one or more receiving solutions (Cloud2Cloud, Cloud2OnPremise) the Cloud Integration capability within SAP Integration Suite is used. It applies required mediations (such as receiver determinations, filtering, aggregations) and

  1. An SAP or third-party cloud solution issues transactional data as messages.
    1. The transactional data is sent out as a message which is a package of data comprising out of a header and a payload. Typically, the message header contains information such as the logical or physical receiver of the message and the payload contains the actual business data.
  2. Direct exchange of messages between one sending and one receiving solution is possible in case of aligned APIs (such as schema, transport protocol) and agreed exceptions.This option is available for selected integration scenarios and is suited for simple landscapes only.
  3. In case of unaligned APIs between a sending and receiving solution (Cloud2Cloud, Cloud2OnPremise) the Cloud Integration capability within SAP Integration Suite enables interoperability with the help of integration flows.
  4. SAP Business Accelerator Hub provides predefined integration flows and APIs, adapters and more to build custom integration flows deployed on Cloud Integration.
  5. Whenever the integration scenario involves an on-premise solution (Cloud2OnPremise) it is recommended to use the SAP Connectivity service with cloud connector and SAP Destination service to establish a secure connection from SAP BTP to the on premise landscape.
  6. In case data has to be processed locally (e.g. to meet data compliance and governance requirements) it is recommended to use the edge integration cell runtime (OnPremise2OnPremise).
  7. In case the integration scenario involves SAP S/4HANA or SAP ECC the SAP Application Interface Framework can enable integration monitoring and error handling by business users.


Related Blueprints

API managed integration

DATA Streaming


LeanIX Template

Link to LEANIX Diagram