SAP BTP - Infrastructure Requirements

SAP BTP - Infrastructure Requirements

Overview

This document defines the minimum infrastructure sizing required to execute the BVC on SAP Business Technology Platform (BTP) using Kyma runtime environments. Three independent environments must be provisioned:

  • One Connect Smart Gateway — real-time SAP data extraction and streaming
  • One Connect Agentic Semantic Knowledge (ASK) — AI-powered semantic querying over SAP Data Products
  • SAP HANA Cloud — in-memory persistence layer for Business Data Products

Additionally, the following SAP subscriptions are required to deploy the agent for the BVC:

  • SAP AI Launchpad
  • SAP AI Core
Idea
Note
Production environments will require larger allocations based on transaction volumes and SLA requirements. Sizing specifications below reflect minimum requirements for a Proof of Concept.

1. One Connect Smart Gateway on BTP Kyma

The One Connect Smart Gateway is deployed on Kubernetes within the Kyma runtime. It receives data and metadata from the SAP Data Modeler, translates them into Kafka Schemas and Topics, and serializes messages in Avro format. It is the only SAP-verified technology capable of extracting real-time data and metadata from SAP.

T-Shirt Size
vCPU per Node
RAM per Node (GB)
Virtual Machines
Standard Storage
/Cluster's Snapshots (GB)
Nodes Capacity Units (CU)
Storage Capacity Units (CU)
X-Small
2
8
3
128
777.60
115.20
Small41642561,382.40230.40
Medium83234162,073.60374.40
Large166435764,147.20518.40

The selection of the T-Shirt size will depend on the number of records that will be processed during the BVC. For the initial steps of the Proof of Concept we recommend selecting the X-Small or Small Size.

2. One Connect ASK on BTP Kyma

One Connect Agentic Semantic Knowledge (ASK) enables AI-powered, natural-language querying over governed SAP Data Products. ASK is deployed as a separate Kyma cluster and requires its own dedicated compute, memory, and storage resources.

Minimum Cluster Specifications (PoC)

ResourceMinimum Specification
Compute per Virtual Machine2 vCPU — 8 GB RAM
Number of Virtual Machines3 VMs
Cluster Standard Storage32 GB
Cluster Snapshot Storage32 GB

Capacity Unit (CU) Cost Estimate

Cost ComponentCapacity Units (CU)
Nodes777.60 CU
Storage28.80 CU

Idea
Notes
Note
CU figures are estimates based on the minimum PoC configuration. Actual billing depends on your BTP subscription plan and entitlement configuration. Contact your SAP Account Executive for accurate cost projections.

3. SAP HANA Cloud

SAP HANA Cloud provides the in-memory persistence layer for One Connect Business Data Products. For the Business Value Challenge Proof of Concept, the Minimum preset is sufficient to validate real-time data flows and business analytics across all four pre-packaged Business Data Products.

Minimum Preset — BVC / PoC

SpecificationValue
Monthly Capacity Units483 CU / month
Memory16 GB
Compute1 vCPU
Storage80 GB

Example Instance Configuration (SAP BTP Cockpit)

Below is an example of a running HANA Cloud instance provisioned under the Minimum preset, as visible in the SAP BTP Cockpit:

State / NameType / VersionRuntime EnvMemory / StorageCompute / Nodes
Running
STATE_NAME
SAP HANA Database
2025.40.15 (QRC 4/2025)
Cloud Foundry16 GB / 80 GB1 vCPU / 1 node

4. Required SAP Subscriptions

For the Business Value Challenge, the following SAP subscriptions are required in order to deploy the agent tailored to the specific business use case:

  • SAP AI Launchpad — a centralized interface that enables users to manage, monitor, and govern AI scenarios across the organization. It provides visibility into AI models, lifecycle management, and performance tracking, ensuring transparency and control over AI operations.
  • SAP AI Core — the execution layer for AI workloads. It allows developers to build, train, and deploy machine learning models at scale in a secure and scalable environment, supporting integration with SAP and non-SAP data sources.

Need Help with Sizing or Provisioning?

Once you have reviewed the specifications above, reach out to the Onibex Support Team to get assistance. Please have the following information ready:

  • SAP database size (GB/TB) and version (ECC or S/4HANA).
  • Estimated volume of records processed per second (event throughput).
  • Number of Data Products and SAP modules to be integrated.
  • Preferred BTP subaccount and Kyma plan already provisioned.
Contact our team at support@onibex.com and we will guide you through the provisioning process and prepare a tailored infrastructure plan for your organization.
    • Related Articles

    • How to Provision SAP BTP Services: AI Core · AI Launchpad · HANA · Kyma

      How to Provision SAP BTP Services: AI Core · AI Launchpad · HANA · Kyma This guide provides step-by-step instructions for provisioning the following SAP Business Technology Platform (SAP BTP) services: SAP AI Core – The runtime environment for AI ...
    • How to connect Kubectl to BTP Kyma environment using AWS EC2

      Overview This guide walks through the steps required to connect kubectl to a BTP Kyma environment using an AWS EC2 instance as the intermediary host. Prerequisites EC2 instance running Amazon Linux. pem key file for the EC2 instance (e.g., ...
    • SmartGateway Configuration - Creating SAP Connectors

      SmartGateway Configuration Manual Creating SAP Connectors on the SmartGateway Platform Note Each account and user will have the ability to create SAP connectors in their designated environment. The following will show how a SAP Connector is created ...
    • Kyma OneConnect Platform — Complete Deployment Guide

      Overview This manual guides you through the fully private deployment of OneConnect on SAP BTP Kyma (AWS EKS). All access is routed through SAP Cloud Connector — no services are exposed to the public internet. Installation Flow Overview Follow the ...
    • SmartGateway Configuration - User Groups

      Requirements Administrator account credentials. The email address of the user who will receive access. Procedure Log in to your administrator account. In the User Dashboard, locate the user who created the SAP Link and click the corresponding arrow ...