OneConnect General Architecture
The following representation shows a general architecture diagram for OneConnect, considering SAP ECC or S4HANA as the producer and destinations such as Clickhouse, Snowflake, and Databricks as subscribers.
The OneConnect structure consists of 3 main components:
One Connect ABAP: A module installed within SAP, responsible for data modeling and executing information delivery in batch or real-time.
One Connect SaaS: Includes all the essential components required for seamless data flow through Kafka, along with informational metrics that provide visibility into service usage.
One Connect Web: Section dedicated to user administration along with workspaces.
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 ...