ASAPIO offers connectivity for SAP® systems to Apache Kafka® brokers
- Supports a wide range of SAP NetWeaver based systems on Premise or in private cloud, including SAP ERP, S/4HANA, BW, HCM and many more
- REST-based outbound communication via e.g. Confluent or other REST proxy
- Choose between event-driven real time mode (single events) or batch mode (multiple events)
- Supported communication direction: Outbound, Inbound
- Batch mode allows multi-threading with multiple SAP work processes for initial data loads
Considered to use Confluent® instead of native Kafka®?
Please check out our dedicated and certified connector for Confluent Cloud and Platform here.
How does it work?
ASAPIO Connector for Kafka is based on ASAPIO Integration Add-on, a proven SAP-certified solution and robust framework for many integration use-cases (such as real time analytics, stream processing or creating a consistent data layer for modern cloud native apps).
The Connector communicates with a REST proxy, in a push mode for outbound messages and a pull mode for inbound messages. The REST proxy directly communicates the Kafka broker then.
REST Proxy:
Confluent REST Proxy for Kafka is mandatory for the connectivity and subject to a separate license.
Please see https://github.com/confluentinc/kafka-rest for more details.
We also see customers using Apache NiFi as a REST proxy. Please contact us for details.
ASAPIO is certified for Confluent® Platform and Cloud
Since April 2021, the Connector is certified as Source and Sink for Confluent Platform and Cloud
– please visit Confluent Hub website for details.
Out-of-the-box connectivity, with just a few configuration steps
- Enter connection data to the REST proxy end-point
- Configure the required authorization data on Connector side
- Configure your message type and payload
- Choose the applicable SAP business object event and link it to your just created message type
- Choose between real-time / single-event mode or batch driven mode
- Activate the connection
Delivery and deployment
Subscribers will receive an installation package, including SAP transport requests for the respective SAP system.
After import of the transports with SAP Transport Management System (transaction code STMS), the Add-on configuration settings will appear in the SAP systems’s built-in SAP Implementation and Configuration Guide.
Now apply the basic configuration and connectivity settings, including authorizations setup, SM59 endpoint configuration etc., which is all explained in detail in the supplied configuration guide.
Once the connector is set-up, you can start right away into configuring data events, message payload and triggers to integrate your core business data into your cloud services.
Delivered content
- SAP Transport Packages with requires software components
- Installation Guide
- ASAPIO Support Portal account data
Software components
The following ASAPIO Integration Add-on components will be installed in the SAP systems:
- Framework
- Connector for Confluent®
Martin Schöffler
Product Manager
ASAPIO Integration Add-on