OneConnect General Architecture
The diagram below illustrates the high-level architecture of the OneConnect solution. It depicts SAP ECC or S/4HANA as the data producer, with multiple downstream systems—such as ClickHouse, Snowflake, and Databricks—acting as subscribers. Other destinations can also be supported.
1. SAP Data Modeler
Responsible for modeling SAP entities based on SAP tables, CDS views, or ABAP programs.
Replication Methods:
-
Table Format: Each SAP table or CDS view is transformed into a Kafka topic, preserving primary keys—similar to Change Data Capture (CDC).
-
Document Format: Each SAP document is converted into a Kafka topic with a nested, hierarchical structure. This structure resembles an IDOC, but instead of segments, it contains SAP tables or CDS views.
-
-
Data Delivery:
Pushes both data and metadata to the Smart Gateway, either in batch mode or via real-time SAP event triggers (e.g., BOR Events, RAP Events).
2. Smart Gateway
A Kubernetes-based component that ingests data and metadata from SAP.
-
Translates the incoming content into Confluent-compatible schemas and Kafka topics.
-
Serializes messages into Avro format for efficient transport and schema enforcement.
3. Onibex Premium Connectors
Enterprise-grade connectors designed to streamline Kafka integrations with modern analytics platforms.
-
Supported Targets: Databricks, Snowflake, ClickHouse, and Apache Iceberg.
Key Features:
-
Rapid deployment of streaming pipelines
-
Automated schema evolution
-
Idempotent writes for consistent data ingestion
-
Secure, high-performance data transfers
-
These connectors enable accelerated data modernization and deliver measurable business value—often within hours of deployment.
Related Articles
Establishment of the Database and Requirements
One Connect Manual in Azure Establishment of the Database and Requirements Prerequisites For the SQL database, the following are recommended: MariaDB MySQL Download the following sql.zip file - Database Deployment Minimum Resource Requirements ...OneConnect Deployment and Configuration
One Connect Platform: Kubernetes Azure Deployment Manual for Private Network This manual outlines the steps required to deploy the One Connect system on a Kubernetes cluster within a Private Network (meaning the OneConnect Platform will not be ...One Connect Cloud Deployment
Prerequisites Download the required .zip folders attached at the end of the document: sql.zip one-connect.zip kafka-compose.zip Requirements for the Virtual Machine System: Linux Architecture: 64-bit processors (x86_64) support Instance ...One Connect Platform - Functionalities
Introduction The table below outlines key features of the OneConnect platform, showcasing out of the box functionalities that support user management, system monitoring, SAP connectivity, and real-time data operations. No Function Description 1 ...Optional Configurations - Configuring the Producer Ingress Cluster & Internal Load Balance Creation
Configuring the Producer Ingress Cluster (OPTIONAL) Note: This step is only required if, during the deployment creation, the environment variable "KUBERNETES_ISINGRESSACTIVE" in the builder-deployment.yaml manifest was set to true. Navigate to the ...