OneConnect General Architecture

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:

Data and metadata are pushed to the Smart Gateway either in batch mode or through real-time SAP event triggers (e.g., BOR Events, RAP Events). Communication is secured via HTTP Intranet or Private Connection, ensuring data integrity and protection during transport.


2. Smart Gateway

A Kubernetes-based component that ingests data and metadata from SAP.

  • Translates incoming content into Confluent-compatible schemas and Kafka topics
  • Serializes messages into Avro format for efficient transport and schema enforcement
  • Communicates securely over HTTP Intranet or Private Connection

Note: The Smart Gateway database only stores operational metrics and administrative metadata. No customer-sensitive or private information is stored.

​

3. Onibex Premium Connectors

Enterprise-grade connectors that streamline Kafka integrations with modern analytics platforms.

Supported Targets:

  • Databricks
  • Snowflake
  • ClickHouse
  • 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 accelerate data modernization and deliver measurable business value— often within hours of deployment.

    • Related Articles

    • 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 ...

    • 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 ...

    • Performance Between Snowflake Connector vs Onibex Connector

      Onibex Connector vs Snowflake Native Performance Analysis and Comparison Study Onibex Connector: Up to 35% Performance Improvement Optimized for high-throughput data ingestion into Snowflake Executive Summary This comprehensive performance analysis ...

    • EKS Deployment Manual with Terraform

      This manual provides step-by-step instructions for deploying an Amazon EKS (Elastic Kubernetes Service) cluster using Terraform. It includes the configuration of essential components such as AWS credentials, infrastructure provisioning, EBS CSI ...

    • 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 ...