Categories
SAP Products

SAP CPI Disaster Recovery | IntegraDR

SAP Integration Suite (CPI) Disaster Recovery | IntegraDR
IntegraOps · Disaster Recovery for SAP Integration Suite (CPI)
IntegraDR

SAP Integration Suite (CPI)Disaster Recoverywith controlled Backup & Restore

With IntegraDR, packages and integration artifacts from SAP Integration Suite (CPI) can be backed up outside the source tenant to a configurable backup repository – GitHub is one example – and, when needed, restored in a controlled way to an empty target tenant of the same company.

Backup and recovery remain separate decisions — the restore plan is checked before writing and confirmed deliberately.

IntegraDR interface for SAP Integration Suite (CPI) backup configuration, backup status and backup runs
Backup configuration, status and runs in one interface.
Repository-based backupRetain version states with control
Automated backupsStart manually or schedule execution
Checked restoreReview plan, content and dependencies
History & APITrace execution and outcomes
Overview

What is IntegraDR?

IntegraDR is the IntegraOps disaster recovery component for SAP Integration Suite (CPI). It stores selected packages and integration artifacts in a configurable backup repository, with GitHub as one example, and supports controlled recovery.

Retain backup states independently of a platform

Backups include package metadata, design content, captured externalized parameters and information about the backed-up deployed state. They are retained in a configurable backup repository; GitHub is one possible example. A successful backup state can be selected specifically as the basis for a recovery.

How it works

Backup and recovery in clear steps

From backup through technical verification, IntegraDR guides you through a traceable workflow. Every recovery is based on a selected backup state and a plan checked in advance.

01

Define the backup target

Configure a backup repository and backup parameters for the source – GitHub is one example.

02

Run the backup

Start a backup on demand or run it regularly on a schedule.

03

Select a backup state

Choose a successful backup that fits the recovery objective.

04

Review the restore plan

Check target, content, checksums and detected dependencies before writing.

05

Confirm & verify

Confirm the plan deliberately, recover the content and verify the result technically.

Important clarification: A successful backup does not prove a successful recovery. Only a restore followed by functional acceptance shows whether recovered content can be used as expected in the target.

Capabilities

Everything for controlled recovery

IntegraDR capabilities combine backup, controlled recovery and traceable outcomes for SAP Integration Suite (CPI).

Backup to a repository

Store integration content outside the source tenant in a configurable repository – GitHub is one possible example.

Manual & scheduled backups

Start backups on demand or execute them automatically at configured times.

Design & deployed state

Back up edited and deployed content separately and consider both during recovery.

Externalized parameters

Back up captured configuration values with integration content and restore them during recovery.

Checked restore plan

Check target, content, checksums and detected dependencies before writing.

Manual plan confirmation

Confirm the prepared recovery scope deliberately before content is written to the target.

Optional deployment

Decide deliberately after recovery whether activation should take place and which state is used.

Technical verification

Check recovered content and configuration; with runtime monitoring selected, also check deployment results.

Notifications, history & API

Inform stakeholders about backup success or failure, and integrate runs, status checks and execution control.

Disaster recovery use cases

Backup and recovery for disaster recovery

IntegraDR supports traceable disaster recovery workflows for SAP Integration Suite (CPI) – from regular backup through tested recovery scenarios.

Establish regular backups

Define daily backup times and follow results through history and active notifications.

Recover integration content

Select a successful backup and recover supported content to an empty target tenant of the same company.

Rehearse recovery

Perform a restore in an empty test tenant and then verify functional behavior.

Preserve design and runtime states

Store the current design content and a potentially different deployed state separately.

Separate recovery and activation

Recover design and externalized parameters, then decide separately about subsequent deployment.

Integration with automation tools

Integrate backup and recovery workflows as well as status checks into external tools through the API.

Recovery

Recover backup states with purpose

A successful backup state is used as the basis for controlled recovery. IntegraDR checks the plan before writing and records the outcome transparently.

Select a successful backup specifically as the basis for recovery.
Check target, content, checksums and detected dependencies before writing.
Confirm the recovery scope manually and trace the technical outcome.
FAQ

Frequently asked questions about IntegraDR

Direct answers about disaster recovery, backup to configurable repositories – GitHub is one example – and controlled recovery in SAP Integration Suite (CPI).

Backup and backup states

What is IntegraDR?
IntegraDR is the IntegraOps disaster recovery component for SAP Integration Suite (CPI). It stores packages and integration artifacts in a configurable backup repository, with GitHub as one example, and supports controlled recovery to an empty target tenant of the same company.
Which content is backed up?
Backups include package metadata, design content, captured externalized parameters and information about the backed-up deployed state. Credentials, security materials, certificates, destinations and external services are not restored automatically.
Can backups run on a schedule?
Yes. Backups can be started manually when required or run on a schedule at configured times. Active notifications inform stakeholders about backup success and backup failures.

Recovery, deployment and verification

What is checked before recovery?
Before writing, the target, content, checksums and detected dependencies are checked. The prepared recovery scope must then be confirmed deliberately.
What are the requirements for the target tenant?
The target tenant must belong to the same company and must not contain design or runtime artifacts. Empty packages are permitted. Supported artifact types and recovery paths are checked before writing.
Is deployment automatic after recovery?
No. Deployment is optional. After recovery, you can deliberately decide whether activation should take place and whether to use the recovered design state or a supported backed-up deployment state.
What does technical verification confirm?
Technical verification checks recovered content and configuration. With runtime monitoring selected, deployment results can also be checked. Successful API acceptance or a started artifact does not yet prove correct functional processing.

Traceability and integration

How do history, reports and the API help?
History and reports document backup scope, decisions, warnings and actual task outcomes. The API can integrate backups, recoveries, status checks and execution control into existing automation.
Next step

Would you like to back up SAP Integration Suite (CPI) content with control?

Discuss your disaster recovery and backup strategy, integration of a repository such as GitHub, and requirements for recovery, deployment and technical verification with KaTe.

Categories
SAP Products

SAP CPI Transport Management | IntegraTM

SAP Cloud Integration Transport Management | IntegraTM
IntegraOps · Transport Management
IntegraTM

Control SAP Cloud Integration transports

With IntegraTM, packages and integration artifacts can be transferred reliably from source to target tenants. Targeted selection, parameters, dependency checks, approvals and technical verification combine into a controlled workflow.

Deployment remains a deliberate decision — transfer, verification and activation can be controlled independently.

IntegraTM transport lane: SAP Cloud Integration artifacts are transferred between development, test and production tenants
Transport routes, runs, progress and outcomes in one interface.
Configured transport routesStructure source and target
Controlled releasesEmail, approval & rejection
Technical verificationRead back and validate imported content
History & reportsTrack scope, decisions and outcomes
Overview

What is IntegraTM?

As IntegraOps’ transport management component for SAP Cloud Integration, IntegraTM brings the steps of a controlled artifact transport together. This keeps scope, decisions and technical outcomes connected in one traceable workflow.

From package to verified target state

Select packages or integration artifacts. Externalized parameters are detected, proposed with values and can be adjusted. After dependencies are reviewed and approval is granted, the transfer to the target system is completed with subsequent technical verification.

How it works

A transport run with clear decisions

From artifact selection to technical verification, IntegraTM guides you through a clear transport workflow. Reusable templates reduce preparation effort so recurring transports can be prepared consistently.

01

Choose a transport route

Define source and target for the planned run.

02

Define the scope

Select packages or supported individual artifacts precisely.

03

Review the configuration

Decide on parameters and resolve identified dependencies.

04

Approve & import

Include required approvals and execute the import.

05

Verify & document

Read back design content and configuration in the target technically.

Important clarification: Technical verification confirms imported design content and configuration. Functional behavior in the target is then tested separately. A deployment request alone therefore proves neither a completed deployment nor successful message processing.

Capabilities

Everything a controlled transport needs

IntegraTM capabilities support technical preparation, controlled execution and traceable outcomes for SAP Cloud Integration.

Configured transport routes

Defined source-to-target connections structure transfers between SAP Cloud Integration tenants. This makes every transport route clearly traceable.

Targeted artifact selection

Choose complete packages or supported individual artifacts to match the objective. This keeps the transport scope intentionally focused.

Externalized parameters

Target-specific configuration values can be adopted from the source, retained in the target or adjusted. This keeps target configuration under control.

Dependency check

Identified missing dependencies can be resolved before import. This reduces the risk of incomplete transports.

Templates & approvals

Reusable templates simplify recurring transports while required approvals are documented as part of the workflow.

Email & approval workflow

Whenever approval requests, rejections, errors or relevant transport events occur, stakeholders are informed by email. Authorized people can also approve or reject transports at the approval step.

Technical verification

After import, design content and configuration can be read back and verified technically. This makes the target state transparent.

History, reports & API

Scope, decisions and outcomes remain traceable; transports can also be integrated with other automation tools through the API.

Multiple environments in one tenant

Use one SAP Integration Suite tenant to host more than one logically separated environment. Virtual transports establish separate environments within the same physical tenant.

Use Cases

Handle transport tasks systematically

To organize cloud integration across development, test and production stages in a controlled way, IntegraTM provides clear transport workflows. This allows recurring tasks to be prepared, approved and checked transparently.

Transfer a new version to the test tenant

Select the affected iFlows, check dependencies and define externalized parameters for the target. This prepares the test state precisely.

Release to production

First prepare the transport scope, then request approval by email and approve or reject the run at the approval step.

Control transfer and activation separately

Import and verify content, then make a deliberate decision about a subsequent deployment.

Streamline recurring transports

Use saved templates while still running each new transport with its own decisions and checks. This retains control.

Integration with automation tools

Integrate transports into existing tools through the API and actively inform stakeholders about approvals or errors.

Create virtual environments in one tenant

Use virtual transports to establish two logically separated environments in one SAP Integration Suite tenant. A dedicated prefix keeps virtual copies clearly distinguishable.

Virtual environments

Run more than one environment in a single tenant

With IntegraTM, one SAP Integration Suite tenant can host more than one logically separated environment. This can support a three-tier system landscape with only two physical tenants, for example for development, test and production. Virtual transports establish distinct environments within the same tenant.

Virtual transports establish distinct logical environments within one shared physical tenant.
Dedicated prefixes identify virtual copies clearly in transport routes and history.
A three-tier development, test and production landscape can be organized with two physical tenants.
FAQ

Frequently asked questions about IntegraTM

Direct answers on controlled SAP Cloud Integration transports, approvals and target configurations.

Transport scope and target configuration

What is IntegraTM?
As IntegraOps’ transport management component, IntegraTM enables transparent transfers of packages and integration artifacts in SAP Cloud Integration. It connects selection and parameter decisions with approvals, import and technical verification.
Which content can be transported with IntegraTM?
Depending on the objective, complete packages or supported individual artifacts can be selected. The scope is defined for each run and then documented in the history.
How are externalized parameters handled?
For target-specific configuration values, you can decide whether they are adopted from the source, retained in the target or adjusted. This deliberately incorporates target configuration into the workflow.

Approvals, deployment and technical verification

How do email notifications and approvals work?
When approval requests, rejections, errors or relevant transport events occur, stakeholders are informed by email. Authorized people can approve or reject a transport at the approval step; the decision is also documented in the transport run.
Is deployment automatic after transport?
No. Deployment is optional. After import and technical verification, it can be decided whether transferred content should be activated. A deployment request alone proves neither a completed deployment nor successful message processing.
What does technical verification confirm?
Technical verification reads back and checks imported design content and configuration in the target. Functional behavior is then tested in the relevant test process.

Virtual environments in SAP Integration Suite

How can a three-tier landscape be implemented with only two SAP Integration Suite tenants?
IntegraTM uses virtual transports to establish more than one logically separated environment within a single SAP Integration Suite tenant. This can support a three-tier system landscape with two physical tenants, for example for development, test and production. A dedicated prefix distinguishes virtual copies inside the shared tenant. Returning a transport requires a suitable saved mapping from a successfully verified entry run; Virtual → Virtual is not currently supported.
Can IntegraTM be integrated into existing automation?
Yes. The API can integrate transports with other automation tools and broader workflows. History and reports also help trace the scope, decisions and technical outcomes of each run.
Next step

Would you like to structure your SAP Cloud Integration transports?

Discuss your tenant setup, release organization and requirements for approvals, parameters and technical verification with KaTe.

Categories
SAP Products

Kafka Adapter for ABAP

SAP ABAP

Kafka Adapter for ABAP

Native, bidirectional connectivity between your ABAP applications and Apache Kafka — over TCP/TLS, without a separate Kafka REST proxy.

Integration architecture

ABAP applications
Publish / Consume
KaTe GmbHKaTe Kafka Adapter for ABAPNative TCP/TLS
Kafka records
Apache Kafka
TCP/TLSConnectionAvroSchema RegistryJSONData formats
Technical building blocks
IDocs
Custom ABAP types
JSON
Avro
Schema Registry

Architecture overview

ABAP applications, KaTe Kafka Adapter for ABAP and Apache Kafka

ABAP applications
KaTe GmbHKaTe Kafka Adapter for ABAPNative ABAP integration
Apache Kafka
Publish / ConsumeNative TCP/TLS
Direct connection between ABAP and Kafka

Features

All features at a glance

Bring native Kafka connectivity into your ABAP applications with native producer and consumer APIs, configurable data binding and central administration.

Core functions: publish and consume

Publish application data as Kafka records and consume incoming records directly in standard S/4HANA and ECC functions and ABAP.

  • Flexible publishing: publish Kafka records from IDocs, RAP Events (TBA) or custom ABAP programs, using blocking sends or non-blocking outbox enqueueing with Kafka broker acknowledgements (acks).
  • Controlled consumption: read Kafka records and submit them to SAP integration objects, such as IDocs and ABAP calls, through managed consumer channels with consumer groups. Consumers process partitions in parallel and commit Kafka offsets only after successful SAP receiver processing, with retries for failed records within their partition.
  • Configurable setup: use one or more topics, control offsets and work with Kafka keys, values and headers.

Security and connection management

Secure your Kafka connections with TLS encryption, protected credentials and centrally managed connection profiles.

  • Native TCP/TLS connectivity with SASL/PLAIN authentication.
  • Encrypted credentials for Kafka brokers and Schema Registry.

Advanced features: SAP integration, data formats and error handling

SAP integration, data formats and error handling

SAP integration and data formats

Integrate SAP objects with Kafka

  • IDocs: exchange complete IDocs as Kafka records, with SAP acting as sender or receiver.
  • Custom ABAP data types and tables: bind application data to explicitly configured or generic ABAP types, structures and internal tables.
  • RAP Events (TBA): integration with events and powerful reference data lookup from the ABAP RESTful Application Programming Model.

Supported serializers and deserializers

  • Standard Kafka formats: String, Boolean, Short, Integer, Long, Float, Double, UUID, Void and binary formats (ByteArray, ByteBuffer and Bytes).
  • Confluent Avro: native binary encoding and decoding, Schema Registry integration and supported schema evolution.
  • Confluent JSON Schema: serialization and validation with Schema Registry integration within a documented Draft 7 subset.

Key and Value formats can be freely configured with respective serializers/deserializers and binding to data structures.

Configurable error handling and retries

Keep processing failures visible and control how failed records are retried.

  • Configure retry limits and delays.
  • Review retry status and failure details in monitoring.
  • Retry failed records within their partition while other partitions continue.
  • Review uncertain producer delivery outcomes before deciding on recovery.

Advantages

Why connect to Kafka directly from ABAP?

1 · Connect directly to Kafka brokers

Use Kafka’s binary protocol from ABAP. A separate Kafka REST proxy is unnecessary for broker communication; Schema Registry uses its own HTTPS API.

2 · Work with your application’s data

Integrate IDocs and RAP Events (TBA), or use generic and typed interfaces for custom ABAP data. Select the serialization format independently for keys and values.

3 · Keep configuration and diagnostics together

Manage connection profiles and channels in one user-friendly web console, and investigate operational failures through correlated runtime diagnostics.

Comparison

Choose the integration approach that fits your scenario

Kafka Adapter for ABAP

Direct ABAP APIs and SAP data binding

Application-controlled table extraction

Integration logic within your SAP application

Kafka Adapter for SAP Integration Suite

Integration through Cloud Integration iFlows

Orchestration of data exposed by SAP interfaces

Central transformation and routing across systems

Setup

Set up your Kafka integration in three steps

1

1 · Discuss your scenario

Identify your SAP environment, Kafka topics, data formats and processing requirements with our team.

2

2 · Configure the adapter

Prepare the SAP prerequisites, configure protected connection profiles and define producer or consumer channels with the required data bindings.

3

3 · Validate and start processing

Check connectivity, test your application integration and use the administration console to control and monitor processing.

Compatibility

Find the right setup for your SAP environment

Contact us to discuss your SAP release, Kafka environment and installation prerequisites. Avro, Schema Registry and JSON Schema support follow documented mapping, schema and resource limits.

Administration console

More control during setup and operations

Operations and monitoring

Manage Kafka channels centrally and investigate processing issues with runtime status, application logs and targeted diagnostics.

  • Start, stop, pause and resume managed channels from the administration console, with consumer startup from the beginning or latest position of the stream.
  • Inspect consumer group offsets, processing progress and partition status.
  • Monitor producer outbox entries and review uncertain delivery outcomes.
  • Investigate failures through correlated application logs and temporary Kafka protocol traces.

FAQ

Frequently asked questions

Answers to common questions about the Kafka Adapter for ABAP.

What is the Kafka Adapter for ABAP?

The adapter connects SAP applications directly to Kafka using native ABAP producer and consumer APIs. It brings IDocs and custom ABAP data into Kafka integration, with configurable serialization and a web console for administration. RAP Events integration is TBA.

How are Kafka connections secured?

Broker communication uses TCP/TLS with SASL/PLAIN authentication. Broker and Schema Registry credentials are stored under separate encrypted aliases, keeping connection configuration separate from secrets.

How does the adapter preserve processing order?

Records are processed in order within each assigned partition. A failed record is retried before later records in that partition proceed, while other partitions can continue. Ordering across different partitions is determined by your application design.

Can consumers process records in parallel?

Managed consumer groups distribute partitions across configured consumers. This allows parallel processing across partitions while retaining ordered processing within each partition. Capacity depends on partition count, SAP resources and receiver workload.

Can I choose where consumption starts?

You can configure consumption from the beginning or latest position of the stream. Explicit-offset read APIs also support selected stream positions. Existing consumer-group offsets affect where an established group resumes.

How can I monitor and troubleshoot my integration?

The web console brings channel controls, processing progress, consumer offsets and producer outbox inspection together. Application logs show error and retry details; temporary Kafka protocol traces support targeted troubleshooting. Retry limits and delays are configurable.

When should I use the ABAP adapter instead of a Kafka adapter on middleware?

Use the ABAP adapter when integration logic belongs in SAP — for example, application data integration or custom ABAP extraction of table data to Kafka. Publish and consume Kafka records directly within your ABAP applications, with control over data binding and processing, without routing each exchange through a middleware layer. Use the KaTe Kafka Adapter for SAP Integration Suite when you need central orchestration, transformations or routing across multiple systems. The two adapters complement each other within your integration landscape.

Do I need a Kafka REST proxy?

Unlike other solutions, no separate Kafka REST proxy is needed for broker communication. The adapter speaks Kafka’s binary protocol directly over TCP/TLS from ABAP. Schema Registry integration uses HTTPS separately.

Can I replicate tables to Kafka?

Yes. Publish table data to Kafka using generic or explicitly typed ABAP serialization and a simple custom ABAP program that reads and sends data through a Kafka channel. This enables straightforward data integration tailored to your requirements.

Can I exchange IDocs through Kafka?

Yes. Send and receive complete IDocs as Kafka records using standard SAP IDoc integration. Outbound IDocs are confirmed after Kafka acknowledges the record.

Which Confluent serializers are supported?

The adapter provides serializers and deserializers compatible with Confluent Avro and Confluent JSON Schema, including Schema Registry integration. Avro supports schema evolution; JSON Schema supports validation within a documented Draft 7 subset.

How does the adapter support reliable delivery?

The adapter commits Kafka consumer offsets only after successful receiver processing. Failed records are retried before processing continues within their partition, helping ensure records are not skipped when processing fails.

Contact

Planning Kafka integration from ABAP?

Tell us about your SAP environment, data formats and processing requirements. We can discuss the integration approach and supported configuration with you.

Categories
SAP Products

Kafka Adapter for SAP Integration Suite

Kafka Adapter for SAP Integration Suite (CPI) – KaTe GmbH
SAP Integration Suite (CPI)

Kafka Adapter for
SAP Integration Suite

Bidirectional connection between SAP Cloud Integration Iflows and Apache Kafka – the logical successor to the proven KaTe Kafka Adapter for SAP PO.

Verified SAP Partner Free 30-Day Trial
Architecture Overview
SAP Cloud
Integration
Iflow
bidirektional
KaTe
Kafka Adapter
CPI
Publish / Subscribe
Apache Kafka
On-Premise / BTP
Avro Protocol Buffers OAuth2 SASL_SSL Schema-Registry Batch Processing CSFLE / CSPE
Verified SAP Partner
Free 30-Day Trial
SAP Roadmap Compatible

All Features of the Kafka Adapter at a Glance

The KaTe Kafka Adapter for SAP Integration Suite offers much more than the SAP standard adapter – from Avro support to Field-Level Encryption.

Core Functions: Publish & Subscribe
Publish SAP Cloud Integration Iflow messages as Kafka records and subscribe to Kafka records as Iflow messages. Kafka Key, Header, and Data are translated into Iflow messages and vice versa.
  • Topics and partitions flexibly configurable
  • Ack mode and consumer commits customizable
  • Fully integrated into SAP Cloud Integration
  • Observable at channel and message log level
Enterprise-Grade Security
All common Kafka security standards are supported – including advanced encryption at the field and payload level for regulated environments.
  • PLAIN, PLAIN_SASL, SASL_SSL
  • SASL-Plain / SASL-SCRAM
  • OAuth2 & Client Certificate Authentication
  • Field-Level Encryption (CSFLE) & Payload Encryption (CSPE)
  • SOC 2, GDPR, ISO 27001 compliant
High Performance & Flow Control
Full control over message throughput, filtering, and batch processing – for optimal performance with high data volumes.
  • Filtering by headers, keys, and data content
  • Batch processing: n Kafka records as one Iflow message
  • Polling and record count/time unit configurable
  • Processing from the beginning, end, or any stream position

Advanced Features: Error Handling, Formats & Migration

Automated & Manual Error Handling
In "in order" streaming systems, errors can stop the entire processing. To prevent this, our adapter offers both manual and fully automated error handling.
  • Error routing to an error destination
  • Documentation and ignoring of specific cases
  • Error handling even for deserialization errors
  • Deduplication via offset or record header
Avro, Protocol Buffers & Schema Registries
Binary data formats like Avro and Protocol Buffers are standard in Kafka environments. Therefore, our adapter fully supports them – including automatic schema generation via schema registries.
  • Avro and Protocol Buffers ↔ XML conversion
  • JSON ↔ XML transformation
  • Schema Registry integration
  • Integrated schema generation tool
SAP Roadmap Compatible
Because the adapter is available for both SAP Process Orchestration and the SAP Integration Suite, existing SAP PO integrations can be transferred with minimal effort.
  • Available for SAP PO and SAP Integration Suite
  • Import existing interfaces without refactoring
  • Determine your own migration plan and schedule
  • Investments in SAP PO integrations are preserved

Why the KaTe Adapter
Can Do More

The KaTe Kafka Adapter offers crucial features that the SAP standard Kafka adapter in SAP Cloud Integration does not provide.

1
Arbitrary Stream Positions & Group Names
While the SAP standard connector does not support arbitrary positions or group names in the stream, our Kafka connector fully provides this feature, which is crucial in daily operations.
2
All Data Formats incl. Schema Registry
Avro, Protocol Buffers, JSON, and schema registries with automatic schema generation are fully supported – although the SAP standard connector has significant gaps here.
3
Batch Processing in One Iflow Execution
Multiple Kafka records can be bundled as a single Iflow message, significantly increasing throughput. Since the SAP standard connector does not offer this function, this is a decisive advantage.
4
Advanced Error Handling & Encryption
Both manual and automated error handling – including deserialization errors – as well as Field-Level and Payload Encryption (CSFLE/CSPE) are integrated, whereas the SAP standard connector does not provide these features.
5
Private and Public Network Access
The adapter runs equally on SAP Cloud Integration and SAP Edge Integration Cell (EIC). It also supports hybrid scenarios, including access to on-premises Kafka brokers, schema registries, and OAuth 2.0 identity providers through SAP Cloud Connector.

Kafka Adapter Comparison:
KaTe vs. SAP Standard

Feature KaTe Adapter SAP Standard
Arbitrary Stream Positions
✓ Yes
✗ No
Avro / Protocol Buffers
✓ Yes
✗ No
Schema-Registry
✓ Yes
✗ No
Batch Processing
✓ Yes
✗ No
Field-Level Encryption
✓ Yes
✗ No
Advanced Error Handling
✓ Yes
Limited
Filtering & Deduplication
✓ Yes
✗ No
OAuth2 & CSFLE/CSPE
✓ Yes
✗ No
SAP Cloud Connector Support
✓ Yes
✗ No

Set Up Kafka Adapter – Start in 3 Steps

1
Request Free Trial

Contact us – within 48 hours you will receive access to the adapter for your test environment.

2
Install Adapter

Installation in your SAP Integration Suite is completed in just a few steps, as our team guides you through the onboarding process.

3
Go Live

Initial productive scenarios start quickly, allowing you to scale as needed – without upfront investments.

Compatibility: Supported Kafka Platforms & Protocols

Whether on-premise, cloud, or hybrid – the KaTe Kafka Adapter for SAP Integration Suite is compatible with all common Kafka deployments and SAP platforms.

SAP Integration Suite
SAP Cloud Integration (CPI) – fully integrated. SAP Docs ↗
Supported
SAP BTP
SAP Business Technology Platform – Cloud-native
Supported
Apache Kafka
On-premise Kafka clusters of all common versions. Apache Kafka ↗
Supported
Confluent Platform
Confluent Cloud and Confluent Platform on-premise. Confluent ↗
Supported
Azure Event Hubs
Kafka-compatible Azure Event Hubs endpoint
Supported
AWS MSK
Amazon Managed Streaming for Apache Kafka
Supported
SAP Edge Integration Cell
Hybrid on-premise scenarios with EIC
Supported
SAP Cloud Connector
Access on-premises Kafka brokers and schema registries through SAP Cloud Connector (SCC).
Supported

KaTe Launchpad – More Control During Setup and Operations

The KaTe Launchpad extends the Kafka Adapter with an integrated toolbox for developers and operations teams, so that all key functions are accessible directly from the SAP Integration Suite.

Generator

Kafka configurations, topic structures, and SAP Integration Suite Iflow channel definitions are automatically generated, significantly reducing configuration effort and error sources.

Service List Display & Tester

The Service List Display provides an overview of all configured Kafka topics, consumer groups, and broker connections, while the integrated tester enables sending and receiving Kafka messages directly from the SAP Integration Suite.

SAP Technology & Migration Consulting –
Future-Proof Integration

KaTe GmbH is your expert partner for SAP technology and migration projects. Our focus is on the secure and seamless transformation of existing SAP PO landscapes to the modern SAP Integration Suite – including the SAP Edge Integration Cell for hybrid integration scenarios.

  • Migration from SAP PO to SAP Integration Suiteincluding analysis, architecture design, and technical implementation
  • Implementation and Optimization of the SAP Edge Integration Cellfor flexible and secure hybrid integration
  • SAP BTP (Business Technology Platform) ConsultingLeveraging modern services and tools for innovation and process automation
  • Technology-Based Strategy Consultingfrom cloud integration to API management
SAP PO → Integration Suite Migration
Structured Migration Without Downtime

We analyze your existing interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite, so the transition succeeds without operational disruption.

Learn More
SAP PO Adapter – Free 30-Day Trial
All SAP PO Adapters – No Upfront Payment

Try our SAP PO Adapters for Kafka, MQTT, AMQP, AWS, Azure, GCP, GraphQL, gRPC, and RESTful – free for 30 days.

View All SAP PO Adapters
IntegraMon – SAP Monitoring
Central Dashboard for All SAP CPI Tenants & EIC Instances

IntegraMon unifies all SAP CPI tenants and Edge Integration Cells in a single dashboard – with proactive alerting, AI support, and automated KPI reports.

Discover IntegraMon

Frequently Asked Questions

Answers to the most important questions about the KaTe Kafka Adapter for SAP Integration Suite.

What is the Kafka Adapter for SAP Integration Suite?

As a powerful middleware component, the Kafka Adapter for SAP Integration Suite connects SAP systems bidirectionally with Apache Kafka – both cloud-native and in hybrid scenarios. Since it reliably processes event-driven data streams and enables message exchange between SAP Cloud Integration Iflows and Kafka topics, it is the ideal integration layer for modern SAP landscapes. As the successor to the KaTe Adapter for SAP Process Orchestration (SAP PO), it also offers state-of-the-art features for seamless SAP integration.

What core features does the Kafka Adapter for SAP Integration Suite offer?

With the adapter, SAP Cloud Integration Iflow messages can be published as Kafka records, and Kafka records can be subscribed to as Iflow messages. Kafka keys, headers, and payloads are automatically translated into Iflow messages – and vice versa. In addition, the following core features are available:

  • Full support for Avro, Protocol Buffers, and JSON, including schema registry and automatic schema generation
  • Topics, partitions, and reliability settings (ack mode, consumer commits) are flexibly configurable
  • Batch processing: n Kafka records as one Iflow message
  • Filtering by headers, keys, and data content
  • Fully integrated into SAP Cloud Integration, observable and debuggable
What security standards are supported?

Because regulated environments have special requirements, the Kafka Adapter for SAP Integration Suite meets the highest security standards. Specifically, the following protocols and methods are supported:

  • Kafka Security Standards: PLAIN, PLAIN_SASL, SASL_SSL, SASL-Plain/SASL-SCRAM
  • OAuth2 and client certificate authentication for broker and service registry connections
  • Field-Level Encryption (CSFLE) and Payload Encryption (CSPE) for sensitive data
  • Compliance-ready for SOC 2, GDPR, and ISO 27001

Technical Details & Comparison

How does the adapter support high performance and error handling?

Thanks to integrated batch processing, filtering, and flow control, the adapter delivers high-performance streaming even at high data volumes, so that even large amounts of data are reliably processed. Messages can be filtered by headers, keys, or data content and bundled into optimized batches.

For stable data processing, both automated and manual error handling are available. Serialization errors, data transformation errors, or Iflow errors can be forwarded to an error destination or deduplicated, so that continuous operation is always guaranteed.

How does the KaTe Adapter differ from the SAP standard Kafka adapter?

While the SAP standard Kafka adapter covers only basic functions, the KaTe Kafka Adapter offers significantly more flexibility and depth. Specifically, these include:

  • Support for arbitrary stream positions and freely definable group names
  • Compatibility with Avro, Protocol Buffers, JSON, and schema registries with automatic schema generation
  • Batch processing in a single Iflow execution
  • Advanced error handling – both manual and automated – including for deserialization errors
  • Filtering and deduplication for higher data quality and optimized data throughput
  • Field-Level and Payload Encryption (CSFLE/CSPE)
  • Flexible private network access to Kafka brokers, schema registries, and OAuth 2.0 identity providers through SAP Cloud Connector.
How does SAP Cloud Connector support hybrid Kafka integration?

The KaTe Kafka Adapter supports SAP Cloud Connector for hybrid integration scenarios. It enables SAP Cloud Integration and SAP Edge Integration Cell to reach on-premises Kafka brokers, schema registries, and OAuth 2.0 identity providers without exposing them directly to the public internet.

Is the KaTe Kafka Adapter SAP Roadmap Compatible?

Yes, the KaTe Kafka Adapter is available for both SAP Process Orchestration and the SAP Integration Suite. Existing SAP PO integrations can therefore be transferred to the Integration Suite without significant migration effort, adjustments, or refactoring.

You determine your own timeline and roadmap. Because your investments in SAP PO integrations are fully preserved, neither unforeseen risks nor commercial follow-up questions arise.

Get Started Now

Ready for Kafka in the SAP Integration Suite?

Contact us for a free 30-day trial or an individual consultation. We set up your trial within 48 hours.

Categories
SAP Products

AMQP Adapter for SAP Cloud Integration

AMQP Adapter for SAP Integration Suite (CPI) – KaTe GmbH
SAP Integration Suite (CPI)

AMQP Adapter for
SAP Integration Suite

Connect SAP Cloud Integration bidirectionally with AMQP brokers such as RabbitMQ, Azure Service Bus, and Apache Qpid – on-premise and in SAP BTP. The logical successor to the proven KaTe AMQP Adapter for SAP PO.

Verified SAP Partner Test 30 days for free
Architecture Overview
SAP Cloud
Integration
Iflow
bidirectional
KaTe
AMQP Adapter
CPI
Publish / Subscribe
AMQP Broker
RabbitMQ / Azure SB
AMQP 0-9-1 AMQP 1.0 SSL/TLS OAuth2 RabbitMQ Azure Service Bus Apache Qpid
Verified SAP Partner
Test 30 days for free
AMQP 0-9-1 & 1.0
RabbitMQ, Azure SB, Apache Qpid

All Features at a Glance

The KaTe AMQP Adapter for SAP Integration Suite provides complete AMQP support for cloud and on-premise scenarios.

Consuming & Producing AMQP Messages
Use SAP Cloud Integration as a fully-featured AMQP consumer or producer – for cloud brokers and on-premise installations.
  • AMQP 0-8-0, 0-9-0 and 1.0 Standard
  • Compatible with RabbitMQ, Azure Service Bus, Apache Qpid
  • Compatible with CloudAMQP and other cloud brokers
  • Fully integrated into SAP Cloud Integration
Enterprise-Grade Security
All SSL variants and common AMQP authentication mechanisms are supported – for maximum security in regulated environments.
  • SSL transport encryption
  • Client certificate authentication
  • OAuth2 and custom authentication
  • All common AMQP security mechanisms
Flexible Payload Support
XML, JSON, and all other payloads are supported without restrictions – for maximum flexibility in heterogeneous system landscapes.
  • XML, JSON, and binary payloads
  • Automatic transformation into SAP formats
  • Configurable message formats
  • Support for AMQP message properties
Cloud & On-Premise Connectivity
Connect SAP Cloud Integration with AMQP brokers directly, via a SOCKS proxy, or through the SAP Cloud Connector into your own data center.
  • Direct connection to cloud brokers
  • SOCKS Proxy Support
  • SAP Cloud Connector for on-premise scenarios
  • Hybrid integration scenarios with SAP EIC
Reliable Message Processing
Stable message processing with configurable acknowledgment modes and error handling for production environments.
  • Configurable acknowledgment modes (ACK)
  • Automatic reconnection on connection loss
  • Error forwarding and dead-letter handling
  • Observable at channel and message protocol level
Easy Migration from SAP PO
Because the adapter is available for both SAP Process Orchestration and the SAP Integration Suite, existing SAP PO integrations can be transferred with minimal effort.
  • 1:1 migration from SAP PO in approx. 1–2 minutes per Iflow
  • Import existing interfaces without refactoring
  • Determine your own migration plan and schedule
  • Investments in SAP PO integrations are preserved

Why the KaTe Adapter
Can Do More

The KaTe AMQP Adapter offers crucial features for reliable and secure AMQP integration in the SAP Integration Suite.

1
Complete AMQP Standard Support
While the SAP standard connector only supports AMQP 1.0, the KaTe Adapter provides AMQP 0-8-0, 0-9-0, and 1.0 – making it compatible with all common brokers, from RabbitMQ to Azure Service Bus.
2
Easy Migration from SAP PO
Existing AMQP interfaces from SAP Process Orchestration can be transferred to the SAP Integration Suite in approx. 1–2 minutes per Iflow, so no refactoring is necessary.
3
Flexible Connectivity
Since the adapter supports direct connections, SOCKS proxy, and SAP Cloud Connector, maximum flexibility in hybrid scenarios is guaranteed.
4
Enterprise Security
SSL, client certificates, OAuth2, and all common AMQP authentication mechanisms are integrated, so compliance requirements in regulated environments are met.

KaTe vs. SAP Standard

Feature KaTe Adapter SAP Standard
AMQP 0-9-1 Support
✓ Yes
Limited
AMQP 1.0 Support
✓ Yes
✓ Yes
RabbitMQ Compatibility
✓ Yes
✗ No
SOCKS Proxy Support
✓ Yes
✗ No
OAuth2 Authentication
✓ Yes
Limited
Migration from SAP PO (1:1)
✓ Yes
✗ No
All Payload Types
✓ Yes
Limited
SAP Cloud Connector
✓ Yes
✗ No

Getting Started – Scale Flexibly

1
Request Free Trial

Contact us – within 48 hours you will receive access to the adapter for your test environment.

2
Install Adapter

Installation in your SAP Integration Suite is completed in just a few steps, as our team supports you during onboarding.

3
Go Live

Initial productive scenarios start quickly, so you can scale as needed – without upfront investments.

Supported Platforms & Brokers

Whether on-premise, cloud, or hybrid – the KaTe AMQP Adapter for SAP Integration Suite is compatible with all common AMQP brokers and SAP platforms.

SAP Integration Suite
SAP Cloud Integration (CPI) – fully integrated
Supported
SAP BTP
SAP Business Technology Platform – cloud-native
Supported
RabbitMQ
On-premise and cloud – AMQP 0-9-1 standard
Supported
Azure Service Bus
Microsoft Azure Service Bus – AMQP 1.0
Supported
Apache Qpid
Apache Qpid Broker – AMQP 0-9-1 and 1.0
Supported
CloudAMQP
Cloud-based AMQP service based on RabbitMQ
Supported
SAP Edge Integration Cell
Hybrid on-premise scenarios with EIC
Supported
SAP Cloud Connector
Secure connection to on-premise AMQP brokers
Supported

KaTe Launchpad – More Control During Setup and Operations

The KaTe Launchpad extends the AMQP Adapter with an integrated toolbox for developers and operations teams, so that all key functions are accessible directly from the SAP Integration Suite.

Generator

AMQP-Konfigurationen, Queue-Definitionen und SAP Integration Suite Iflow-Channel-Definitionen werden automatisch generiert, sodass Konfigurationsaufwand und Fehlerquellen erheblich sinken.

Service List Display & Tester

The Service List Display provides an overview of all configured AMQP queues, exchanges, and broker connections, while the integrated tester enables sending and receiving AMQP messages directly from the SAP Integration Suite.

SAP Technology and Migration Advisory –
Future-Proof Integration

The KaTe GmbH is your expert partner for SAP technology and migration projects. Our focus is on the secure and smooth transformation of existing SAP PO landscapes to the modern SAP Integration Suite – including the SAP Edge Integration Cell for hybrid integration scenarios.

  • Migration from SAP PO to SAP Integration Suite – including analysis, architecture design, and technical implementation
  • Implementation and Optimization of SAP Edge Integration Cell – for flexible and secure hybrid integration
  • SAP BTP (Business Technology Platform) Advisory – leveraging modern services and tools for innovation and process automation
  • Technology-Based Strategy Consulting – from cloud integration to API management
SAP PO → Integration Suite Migration
Structured Migration Without Business Interruption

We analyze your existing AMQP interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite, so that the transition is completed without business interruption.

Learn more
SAP PO Adapter – Test 30 days for free
All SAP PO Adapters Without Upfront Payment

Try our SAP PO Adapters for Kafka, MQTT, AMQP, AWS, Azure, GCP, GraphQL, gRPC, and RESTful – 30 days for free.

View all SAP PO Adapters
IntegraMon – SAP Monitoring
Central Dashboard for all SAP CPI Tenants & EIC Instances

IntegraMon unifies all SAP CPI tenants and Edge Integration Cells in a single dashboard – with proactive alerting, AI support, and automated KPI reports.

Discover IntegraMon

Common Questions

Answers to the most important questions about the KaTe AMQP Adapter for SAP Integration Suite.

What is the KaTe AMQP Adapter for SAP Integration Suite?

As a powerful middleware component, the KaTe AMQP Adapter for SAP Integration Suite enables the use of SAP Cloud Integration as a consumer or producer of AMQP messages – in the cloud (e.g., Azure Service Bus, CloudAMQP) or with on-premise brokers such as RabbitMQ or Apache Qpid. Because it is the successor to the proven AMQP Adapter for SAP Process Orchestration, all existing interfaces can be seamlessly transferred.

Which AMQP standards and brokers are supported?

The adapter supports AMQP 0-8-0, 0-9-0, and 1.0 – making it compatible with:

  • RabbitMQ (on-premise and cloud)
  • Azure Service Bus (AMQP 1.0)
  • Apache Qpid
  • CloudAMQP and other AMQP-compliant brokers

XML, JSON, and all other payload types are also supported.

Which security standards does the AMQP Adapter support?

Because regulated environments have special requirements, the adapter supports all SSL variants and common AMQP authentication mechanisms:

  • SSL transport encryption
  • Client certificate authentication
  • OAuth2 and custom authentication methods
  • All common AMQP security mechanisms
How easy is the migration from SAP PO to SAP Integration Suite?

Existing AMQP interfaces developed with the KaTe AMQP Adapter for SAP Process Orchestration can be transferred to the SAP Integration Suite with minimal effort – approx. 1–2 minutes per Iflow. Your investments are fully preserved, so you can determine your own migration plan.

Is the adapter compatible with SAP BTP and the SAP Edge Integration Cell?

Yes. The KaTe AMQP Adapter is fully compatible with:

  • SAP BTP – for cloud-native integration scenarios
  • SAP Edge Integration Cell (EIC) – for hybrid on-premise/cloud scenarios
  • SAP Cloud Connector – for secure connections to on-premise brokers
How is the connection to on-premise AMQP brokers established?

The adapter supports three connection methods for on-premise scenarios, so the right option is available for every infrastructure:

  • Direct Connection – for cloud brokers or publicly accessible brokers
  • SOCKS proxy – for connections via a proxy server
  • SAP Cloud Connector – for secure connections into your own data center
Get Started Now

Ready for AMQP in the SAP Integration Suite?

Contact us for a free 30-day trial or a personal advisory call. We set up your test environment within 48 hours.

Categories
SAP Products

AWS Adapter for SAP Integration Suite

AWS Adapter for SAP Integration Suite (CPI) – KaTe GmbH
SAP Integration Suite (CPI)

AWS Adapter for
SAP Integration Suite

Verbinden Sie SAP Cloud Integration mit den wichtigsten AWS-Diensten: Lambda, SQS, SNS, S3, EventBridge, Kinesis und DynamoDB – inklusive Cross-Account Access, XML/JSON Transformation und Deduplication.

Verified SAP Partner 30 Tage kostenlos testen On-Premise & SAP BTP Listed on SAP App Center
Architecture Overview
SAP Cloud
Integration
Iflow
bidirectional
KaTe
AWS Adapter
SAP CPI
AWS API
Amazon
Web Services
Lambda · SQS · SNS · S3
Lambda SQS SNS S3 EventBridge Kinesis DynamoDB Cross-Account

Alle wichtigen AWS-Dienste –
direkt in SAP Cloud Integration

Der KaTe AWS Adapter for SAP Integration Suite deckt die gesamte AWS-Servicelandschaft ab – sodass Messaging, Storage, Serverless und Streaming nahtlos aus SAP heraus nutzbar sind.

Call AWS Lambda functions synchronously and asynchronously from SAP Cloud Integration – as the complex authentication logic is fully handled.
  • Synchronous and asynchronous Lambda calls
  • Automatic AWS Signature V4 authentication
  • IAM Role Assume and cross-account access
  • XML/JSON Transformation Included
Send and receive SQS messages with cost-efficient long polling, FIFO support, and claim-check, so that even large payloads are transmitted without issues.
  • Long polling for cost-efficient receiving
  • FIFO-Queues und Message Properties
  • Payloads larger than 256 KB via S3 claim-check
  • Dead-letter queue support
Publish/subscribe AWS SNS messages to a variety of recipients – whether Lambda, HTTP(S), email, SMS, or smartphones.
  • RAW and receiver-optimized SNS messages
  • All recipient types: Lambda, HTTP, email, SMS
  • XML, JSON, and arbitrary payloads
  • Deduplication of events
Store, read, list, and delete S3 objects – including event notifications, so that new, modified, or deleted objects can be reacted to automatically.
  • All storage and encryption variants
  • S3 event notifications (new, modified, deleted objects)
  • Lifecycle options and versioning
  • Multipart upload for large files
Subscribe and publish events to AWS EventBridge, Kinesis Data Streams, Kinesis Firehose, and CloudWatch Events – while all event types and custom event buses are supported.
  • All supported and custom EventBridge event types
  • Kinesis Data Streams and Firehose as XML or JSON
  • CloudWatch Events and custom event buses
  • SaaS third-party event buses
Write, read, delete, and search in DynamoDB tables as well as react to DynamoDB Streams, so event-driven scenarios are fully covered.
  • Create / Read / Update / Delete / Scan / Query
  • DynamoDB Streams for event-driven processing
  • Cross-account access via Role Assume
  • Deduplication of stream events

Why the KaTe Adapter
Can Do More

Because the KaTe AWS Adapter fully handles the complex AWS authentication, all AWS APIs are available as easily configurable Iflow channels – without programming effort.

1
Complete AWS Service Coverage
Lambda, SQS, SNS, S3, EventBridge, Kinesis, and DynamoDB – while all important AWS services are bundled in a single adapter, separate implementations are eliminated.
2
Automatic Authentication
AWS Signature V4, IAM Role Assume, and cross-account access are managed automatically – so manual signing of requests is no longer necessary.
3
XML/JSON Transformation Included
So that SAP-native payloads can be exchanged directly with AWS APIs, the adapter includes automatic XML-to-JSON and JSON-to-XML transformation as well as deduplication – without additional mapping steps.
4
Easy Migration from SAP PO
Existing AWS interfaces from SAP Process Orchestration can be transferred to the SAP Integration Suite with minimal effort, as the adapter offers a 1:1 compatible channel structure.

KaTe vs. SAP Standard

Feature KaTe Adapter SAP Standard
AWS Lambda Calls
✓ Yes
Limited
SQS Payloads >256 KB
✓ Yes
✗ No
IAM Role Assume
✓ Yes
✗ No
Cross-Account Access
✓ Yes
✗ No
DynamoDB Streams
✓ Yes
✗ No
XML/JSON Transformation
✓ Yes
Manual
Deduplication
✓ Yes
✗ No
Migration from SAP PO (1:1)
✓ Yes
✗ No

Start Easily – Scale Flexibly

1
Request Free Trial

Contact us – within 48 hours you will receive access to the adapter for your test environment.

2
Install Adapter

Since the installation is completed in just a few steps, our team supports you during onboarding in your SAP Integration Suite.

3
Go Live

Initial productive scenarios start quickly, so you can scale as needed – without upfront investments.

Supported AWS Services & Platforms

Whether SAP BTP, on-premise, or Edge Integration Cell – the KaTe AWS Adapter is compatible with all important AWS services and SAP platforms.

SAP Integration Suite
SAP Cloud Integration (CPI) – fully integrated
Supported
SAP Edge Integration Cell
Hybrid on-premise/cloud scenarios
Supported
SAP BTP
SAP Business Technology Platform – cloud-native
Supported
AWS Lambda
Serverless-Featureen – synchron und asynchron
Supported
AWS SQS
Simple Queue Service – Standard and FIFO
Supported
AWS SNS
Simple Notification Service – Pub/Sub
Supported
AWS S3
Object Storage – all storage classes and encryption
Supported
AWS EventBridge & Kinesis
Event streaming and data streams
Supported
AWS DynamoDB
NoSQL database – CRUD, scan, query, streams
Supported

KaTe Launchpad – More Control During Setup and Operations

Das KaTe Launchpad extends the AWS Adapter with an integrated toolbox for developers and operations teams – so that all configurations can be managed directly from the SAP Integration Suite.

Generator

Automatic generation of AWS configurations, IAM policies, and SAP Integration Suite Iflow channel definitions for all supported AWS services – as configuration effort and error sources are significantly reduced.

Service List Display & Tester

Overview of all configured AWS connections (SQS queues, SNS topics, S3 buckets, Lambda functions) with an integrated tester, so that messages can be sent and received directly from the SAP Integration Suite.

SAP Technology and Migration Consulting –
Future-Proof Integration

KaTe GmbH is your competent partner for SAP technology and migration projects. Our focus is on the secure and smooth transformation of existing SAP PO landscapes to the modern SAP Integration Suite – including the SAP Edge Integration Cell for hybrid integration scenarios.

  • Migration from SAP PO to SAP Integration Suite – including analysis, architecture design, and technical implementation
  • Implementation and optimization of the SAP Edge Integration Cell – for flexible and secure hybrid integration
  • SAP BTP (Business Technology Platform) consulting – use of modern services and tools for innovation and process automation
  • Technology-based strategy consulting – from cloud integration to API management
SAP PO → Integration Suite Migration
Structured migration without business interruption

We analyze your existing AWS interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite – so that ongoing operations are not interrupted.

Learn more
SAP PO Adapter – 30 Tage kostenlos testen
Alle SAP PO Adapter ohne Vorauszahlung

Test our SAP PO Adapters for Kafka, MQTT, AMQP, AWS, Azure, GCP, GraphQL, gRPC und RESTful – 30 Tage kostenlos.

View all SAP PO Adapters
IntegraMon – SAP Monitoring
Central Dashboard for all SAP CPI Tenants & EIC Instancesnzen

IntegraMon unites all SAP CPI tenants and Edge Integration Cells in a single dashboard – with proactive alerting, AI support, and automated KPI reports.

IntegraMon entdecken

Common Questions

Antworten auf die wichtigsten Fragen zum KaTe AWS Adapter for SAP Integration Suite.

What is the KaTe AWS Adapter for SAP Integration Suite?

Als leistungsstarke Middleware-Komponente verbindet der KaTe AWS Adapter for SAP Integration Suite SAP Cloud Integration with the most important AWS services: Lambda, SQS, SNS, S3, EventBridge, Kinesis Data Streams, and DynamoDB. Because the complex AWS authentication is fully handled, all AWS APIs are available as easily configurable Iflow channels – without programming effort.

Which AWS services are supported?

The adapter allows the use of the following AWS services:

How does AWS authentication work in the adapter?

Because AWS authentication is complex, the adapter handles AWS Signature Version 4, IAM Role Assume (within an account and as cross-account access) as well as all common AWS authentication mechanisms automatically. Configuration is done directly in the SAP Cloud Integration Iflow channel – no manual signing of requests necessary.

Is the adapter compatible with SAP BTP and the SAP Edge Integration Cell?

Yes. The KaTe AWS Adapter is fully compatible with:

  • SAP BTP – for cloud-native integration scenarios
  • SAP Edge Integration Cell (EIC) – for hybrid on-premise/cloud scenarios
  • SAP Cloud Integration – fully integrated as an Iflow channel
How is SQS supported with payloads over 256 KB?

The adapter supports the claim-check pattern for SQS: Large messages are automatically offloaded to S3 and transferred as a reference in SQS. Upon receipt, the message is automatically loaded from S3, so the behavior remains completely transparent to the Iflow and no manual implementation is necessary.

Which cross-sectional features does the adapter offer?

So that SAP-native payloads can be exchanged directly with AWS APIs, the adapter includes the following cross-sectional features:

  • XML-to-JSON and JSON-to-XML transformation – for seamless SAP/AWS integration
  • Deduplication von Objekten, Messages und Events
  • Support for all payload types – XML, JSON, and arbitrary binary data
On which SAP platforms does the AWS Adapter run?

The KaTe AWS Adapter is compatible with all current SAP integration platforms:

  • SAP Integration Suite (CPI) – fully integrated as an Iflow channel
  • SAP Edge Integration Cell – for hybrid on-premise/cloud scenarios
  • SAP BTP – for cloud-native integration scenarios
Wie funktioniert der Cross-Account Access auf AWS?

Because many companies operate multiple AWS accounts, the adapter supports the IAM Role Assume mechanism both within a single account and cross-account. This allows AWS resources in different accounts to be accessed from a single SAP Integration Suite Iflow – without separate configurations per account.

How does the installation and commissioning work?

Since the installation is completed in just a few steps, the adapter is quickly ready for use:

  • Schritt 1 – Request Free Trial: Innerhalb von 48 Stunden erhalten Sie Zugang zum Adapter
  • Step 2 – Installation in the SAP Integration Suite with the support of our team
  • Step 3 – Configure initial productive scenarios and go live
What licensing models are available for the AWS Adapter?

The KaTe AWS Adapter can be tested for 30 days for free – without upfront payment and without a credit card. After the trial, flexible licensing models are available that are tailored to your actual usage requirements. Because every company has different requirements, we are happy to advise you individually on the appropriate licensing options.

Get Started Now

Ready for AWS in the SAP Integration Suite?

Contact us for a free 30-day trial or a personal advisory call. We set up your test environment within 48 hours.

Categories
SAP Products

Salesforce Adapter for SAP Cloud Integration

Salesforce Adapter for SAP Integration Suite (CPI) – KaTe GmbH
SAP Integration Suite (CPI)

Salesforce Adapter for
SAP Integration Suite

360-degree customer view through bidirectional synchronization of Salesforce CRM with SAP systems. REST API, Bulk API, Streaming API, OAuth2, SSL – and integrated developer tools for rapid deployment.

Verified SAP Partner 30-Day Free Trial OAuth2 & SSL
Architecture Overview
SAP Cloud
Integration
Iflow / EIC
REST / Bulk / Streaming
KaTe Salesforce
Adapter
SAP CPI
OAuth2 / SSL
Salesforce CRM
& SAP BTP
Cloud · On-Premise
REST API Bulk API Streaming API OAuth2 SOAP Session SSL XML Schema / WSDL

Salesforce CRM integration with SAP –
360-Degree Customer View in Real Time

The KaTe Salesforce Adapter for SAP Integration Suite synchronizes customer data, orders, and prices bidirectionally between Salesforce and SAP – quickly, efficiently, and securely.

Salesforce REST API
Full support of the Salesforce REST API for standard CRUD operations – this allows Salesforce objects to be read, created, updated, and deleted directly from SAP Cloud Integration.
  • CRUD operations on all Salesforce objects
  • SOQL queries from within Iflows
  • Batch processing of datasets
  • Complete error handling
Salesforce Bulk API
Efficient processing of large data volumes with the Salesforce Bulk API – ideal for mass imports, data migration, and regular synchronizations, so that even high data volumes are processed reliably.
  • Mass processing of datasets
  • Asynchrone Job-Verarbeitung
  • Optimized for large data volumes
  • Data migration and synchronization
Salesforce Streaming API
Real-time events and push notifications from Salesforce – the adapter subscribes to Salesforce events and forwards them directly into SAP Cloud Integration Iflows, so that processes can react immediately.
  • Real-time push notifications
  • PushTopic and Generic Streaming
  • Platform Events support
  • Change Data Capture (CDC)
Authentication & Security
Because security is a top priority in enterprise environments, all Salesforce API authentication mechanisms are supported – OAuth2, SOAP Session, and SSL for maximum flexibility.
  • OAuth2 (recommended)
  • SOAP session-based authentication
  • SSL / client certificates
  • All Salesforce authentication flows
Developer Tools
Since the adapter includes fully integrated tools in the SAP Cloud Integration Eclipse IDE, Salesforce messages can be generated as XML Schema/WSDL and tested directly – this significantly accelerates development.
  • XML Schema / WSDL generation
  • Integrated Salesforce message tester
  • Automatic type detection
  • Eclipse IDE integration
SAP BTP & On-Premise
Existing SAP Cloud Integration functions for transformation and connectivity to SAP BTP and on-premise applications are used, so that no additional middleware is required.
  • SAP BTP Integration
  • On-premise SAP systems
  • SAP Edge Integration Cell
  • No additional middleware

Why the KaTe Salesforce Adapter
is the Right Choice

Fast and efficient Salesforce-SAP integration with full API support, integrated developer tools, and flexible authentication.

1
360-Degree Customer View
Customer information, orders, and prices are kept synchronized between Salesforce and SAP, so that a complete 360-degree view of all customer data is created.
2
All Three Salesforce APIs
REST API for standard operations, Bulk API for large data volumes, and Streaming API for real-time events – all three Salesforce APIs are combined in a single adapter.
3
Integrated Developer Tools
Since XML Schema/WSDL generation and an integrated tester are available directly in the SAP Cloud Integration Eclipse IDE, development effort is significantly reduced and deployment is accelerated.
4
Ready to Use
Because the adapter can be tested free of charge for 30 days and requires no upfront investment, it can be used productively immediately – without lengthy development effort.

KaTe vs. Custom Development

Feature KaTe Adapter Custom Development
REST + Bulk + Streaming API
✓ All three
High effort
OAuth2 / SOAP / SSL
✓ All
Manual
XML Schema / WSDL Generator
✓ Integrated
✗ No
Integrated tester
✓ Yes
✗ No
Maintenance effort
✓ Minimal
High
30-day free trial
✓ Yes
Upfront investment

Get Started Easily – Scale Flexibly

1
Request Free Trial

Contact us – within 48 hours you will receive access to the adapter for your test environment.

2
Install Adapter

Installation in your SAP Integration Suite is completed in just a few steps, as our team supports you during onboarding.

3
Go Live

Initial productive scenarios start quickly, so that you can scale as needed – without upfront investments.

Supported Platforms & Salesforce Editions

The KaTe Salesforce Adapter runs natively on SAP Integration Suite and SAP Edge Integration Cell. It is also compatible with SAP Process Orchestration (PO) and SAP BTP, and supports all common Salesforce editions.

SAP Integration Suite
Runs natively on SAP Cloud Integration (CPI) – primary target platform
Supported
SAP Edge Integration Cell
Runs on Edge Integration Cell – hybrid on-premise/cloud scenarios fully supported
Supported
SAP Process Orchestration (PO)
Compatible with SAP PO – ideal for migration projects to Integration Suite
Supported
SAP BTP
SAP Business Technology Platform – cloud-native integration scenarios
Supported
Salesforce Sales Cloud
CRM for sales teams – bidirectional data synchronization with SAP
Supported
Salesforce Service Cloud
Customer support and service management – fully supported
Supported
Salesforce Marketing Cloud
Marketing automation and campaign management
Supported
SAP ERP / S/4HANA
On-premise SAP systems via SAP Cloud Connector
Supported

KaTe Launchpad – More Control During Setup and Operations

The KaTe Launchpad extends the Salesforce Adapter with an integrated toolbox for developers and operations teams, so that all key functions are accessible directly from the SAP Integration Suite.

Generator

Salesforce configurations, XML Schema/WSDL definitions, and SAP Integration Suite Iflow channel definitions are generated automatically, so that the configuration effort for new Salesforce integration scenarios is significantly reduced.

Service List Display & Tester

The Service List Display provides an overview of all configured Salesforce connections, objects, and API endpoints, while the integrated tester enables sending and receiving Salesforce messages directly from the SAP Integration Suite.

SAP Technology and Migration Consulting –
Future-Proof Integration

The KaTe GmbH is your competent partner for SAP technology and migration projects. Our focus is on the secure and smooth transformation of existing SAP PO landscapes to the modern SAP Integration Suite, so that your Salesforce integrations remain future-proof in the long term.

  • Migration from SAP PO to SAP Integration Suite – including analysis, architecture design, and technical implementation
  • Implementation and optimization of the SAP Edge Integration Cell – for flexible and secure hybrid integration
  • SAP BTP Consulting – use of modern services and tools for innovation and process automation
  • Technology-based strategy consulting – from cloud integration to API management
SAP PO → Integration Suite Migration
Structured migration without business interruption

We analyze your existing Salesforce interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite, so that the transition succeeds without business interruption.

Learn more
Weitere CPI Adapter – 30-Day Free Trial
All SAP Integration Suite Adapters

Test our other CPI adapters for Kafka, MQTT, AMQP, AWS and more – 30 days free of charge.

View all CPI adapters
IntegraMon – SAP Monitoring
Central dashboard for all SAP CPI tenants & EIC instances

IntegraMon combines all SAP CPI tenants and Edge Integration Cells in a single dashboard – with proactive alerting, AI support, and automated KPI reports.

Discover IntegraMon

Frequently Asked Questions

Answers to the most important questions about the KaTe Salesforce Adapter for SAP Integration Suite.

What is the KaTe Salesforce Adapter for SAP Integration Suite?

As a powerful integration component, the KaTe Salesforce Adapter for SAP Integration Suite enables bidirectional synchronization of Salesforce CRM data with SAP systems. Since it supports Salesforce REST API, Bulk API, and Streaming API as well as all Salesforce authentication mechanisms (OAuth2, SOAP Session, SSL), complete 360-degree customer views can be built. Integrated tools for testing and generating Salesforce messages as XML Schema/WSDL are also included.

Which Salesforce APIs are supported?

With the adapter, all three Salesforce APIs are supported:

  • REST API – Standard CRUD operations, SOQL-Abfragen
  • Bulk API – Mass processing of large data volumes, data migration
  • Streaming API – Real-time events, Platform Events, Change Data Capture
Which authentication mechanisms are supported?

Because security is a top priority in enterprise environments, the adapter supports all Salesforce API authentication mechanisms: OAuth2 (recommended), SOAP session-based authentication, and SSL/client certificates, so that all common Salesforce authentication flows are fully covered.

How does the adapter enable a 360-degree customer view?

Through bidirectional synchronization of Salesforce with SAP systems, customer information, orders, and prices are kept consistent across all applications, so that a complete 360-degree customer view is created. The SAP Cloud Integration platform handles transformation and connectivity to SAP BTP and on-premise applications.

What tools does the adapter offer for developers?

Since the adapter includes fully integrated tools in the SAP Cloud Integration Eclipse IDE, the following functions are directly available:

  • XML Schema / WSDL generation for Salesforce messages
  • Integrated tester for Salesforce API calls
  • Automatic type detection for Salesforce objects

This significantly accelerates the development and deployment of Salesforce integration scenarios.

Get Started Now

Ready for Salesforce Integration with SAP?

Contact us for a free 30-day trial or a personal advisory call. We set up your test environment within 48 hours.

Categories
Restful Adapter SAP Products

RESTful Adapter for SAP Integration Suite

RESTful Adapter for SAP Integration Suite (CPI) – KaTe GmbH
SAP Integration Suite (CPI)

RESTful Adapter for
SAP Integration Suite

Efficient integration and development of REST APIs with SAP Integration Suite and the Open API standard. OpenAPI 3.x, Swagger 2.0, OAuth2, JWT – development times drastically reduced.

Verified SAP Partner 30-Day Free Trial OpenAPI 3.x & Swagger 2.0 OAuth2 & JWT
Architecture Overview
SAP Cloud
Integration
Iflow
REST/HTTP
KaTe RESTful
Adapter
SAP CPI
OpenAPI
REST APIs
Cloud · On-Premise
EIC
OpenAPI 3.x Swagger 2.0 OAuth2 / JWT ABAP Proxy XCSRF-Token NTLM

REST APIs according to Open API Standard –
Development Times Drastically Reduced

The KaTe RESTful Adapter for SAP Integration Suite contains all necessary functions so that REST APIs according to the Open API standard can be implemented quickly, securely, and with low maintenance.

OpenAPI & Swagger
Since OpenAPI 3.x and Swagger 2.0 are fully supported, REST APIs according to the Open API standard can be integrated into SAP Integration Suite without time-consuming custom development.
  • OpenAPI 3.x fully supported
  • Swagger 2.0 kompatibel
  • Automatische API-Beschreibung
  • Automatic JSON/XML translation
Sicherheit & Authentifizierung
Because enterprise environments have the highest security requirements, all common authentication methods are supported – for both cloud and on-premise scenarios.
  • OpenID / JWT Authentifizierung
  • OAuth2 (Cloud & On-Premise via Cloud Connector)
  • NTLM-Authentifizierung
  • Blocking of non-compliant API calls
ABAP Proxy Generation
Existing ESR objects can be used as Open APIs with just a few clicks, so ABAP Proxies are generated directly from Open API definitions – without time-consuming new development.
  • ABAP Proxies from Open API definitions
  • Reuse ESR objects as Open APIs
  • API-First development supported
  • Etablierte ABAP-Frameworks nutzbar
Monitoring & Debugging
All API operations and statuses are searchable and visible without overhead through automatic indexing of key/values in the SAP Integration Suite Monitor.
  • Automatisches API-Operationen-Indexing
  • HTTP status codes in the monitor
  • OAuth2 calls fully traceable
  • Integrated testing and generation
OData & SAP-Spezifika
Automatic XCSRF token management and link rewriting to frontend URLs – OData clients can use SAP APIs without SAP specifics.
  • Automatisches XCSRF-Token-Handling
  • Link rewriting to frontend URLs
  • OData in API management solutions
  • SAP specifics transparent for clients
Simple Migration from SAP PO
Open APIs from SAP Process Orchestration can be transferred 1:1 to the SAP Integration Suite – approx. 1–2 minutes per Iflow, so existing investments are fully preserved.
  • 1:1 migration from SAP PO
  • Reuse ESR content as Open APIs
  • No time-consuming new development
  • Custom migration plan possible

Typical Use Scenarios

The KaTe RESTful Adapter for SAP Integration Suite solves the most common challenges in REST API integration with SAP – whether in the cloud, on-premise, or in hybrid environments.

API-First Development
Bridge between old and new world

Software development is increasingly shifting to mobile platforms, hyperscalers, or container environments. These rely on the Open API standard for API management, security (JWT, OAuth2), and automation.

Our adapter facilitates the integration of SAP into API-first strategies of the non-SAP world – whether in SAP BTP, with hyperscalers like AWS, Azure, or GCP, or in containerized development environments.

Regulated Industries
Open APIs in Telecommunications, Banking & Energy

Regulated industries such as telecommunications (TMF), banking (Open Banking), or utilities (market data exchange) rely on standardized Open APIs. Our approach significantly reduces the development and operating costs of such APIs – while utilizing existing developer skills and requiring minimal investments.

With the KaTe RESTful Adapter, you maximize the efficiency and security of your API integrations, protect existing investments, and build seamless bridges between SAP and modern API standards – to meet the increasing demands for integrating modern technologies and drive your digital transformation forward.

OData Integration
OData in Hybrid Enterprise Architectures

SAP has strongly committed to OData over the years, which can be described via Open API definitions. However, the following challenges often arise in hybrid environments or API management solutions:

  • › SAP Specifics: Clients have to deal with XCSRF token management or SAP-specific attributes.
  • › Internal Links: API management solutions deliver responses with internal links, which poses security risks and makes use by OData clients difficult.

The KaTe RESTful Adapter solves these problems efficiently: Links are automatically rewritten to frontend URLs, and XCSRF tokens are processed automatically.

Why the KaTe RESTful Adapter
is the right choice

REST APIs according to the Open API standard with SAP Integration Suite – without time-consuming custom development, without maintenance costs, with complete security and visibility.

1
Drastically Reduced Development Times
JSON/XML translation, HTTP status routing, and API description in minutes instead of hours. Existing ESR objects become Open APIs with just a few clicks, so teams can work productively right away.
2
Complete Security & Transparency
OAuth2 calls are fully traceable – no black box. Because non-compliant API calls are automatically blocked, OpenID/JWT, custom OAuth2, and NTLM are seamlessly secured.
3
Simple Migration from SAP PO
Existing Open APIs from SAP Process Orchestration can be transferred 1:1 to the SAP Integration Suite – approx. 1–2 minutes per Iflow. This fully preserves investments.
4
Economic Advantages
Reduction of development costs through shortened development times and use of existing skills. Since ESR content is reused as Open APIs, costly new development is eliminated.

KaTe vs. SAP Standard

Feature KaTe Adapter SAP Standard
OpenAPI 3.x & Swagger 2.0
✓ Yes
Limited
ABAP Proxy Generation
✓ Yes
✗ No
OAuth2 via Cloud Connector
✓ Yes
Limited
Automatic XCSRF Token Handling
✓ Yes
✗ No
API Operations Indexing
✓ Yes
✗ No
Migration from SAP PO (1:1)
✓ Yes
✗ No
OAuth2 fully traceable
✓ Yes
✗ No

Get started easily – scale flexibly

1
Request Free Trial

Contact us – within 48 hours you will receive access to the adapter for your test environment.

2
Install Adapter

Since the installation in your SAP Integration Suite only requires a few steps, our team will support you during onboarding – so you can be productive quickly.

3
Go Live

Initial productive scenarios run quickly. Scale as needed – without upfront investments.

Supported Platforms & Standards

Whether SAP BTP, Edge Integration Cell, or hyperscalers – the KaTe RESTful Adapter is compatible with all common API standards and SAP platforms.

SAP Integration Suite
SAP Cloud Integration (CPI) – fully integrated
Supported
SAP BTP
SAP Business Technology Platform – cloud-native
Supported
SAP Edge Integration Cell
Hybride On-Premise/Cloud-Szenarien
Supported
OpenAPI 3.x
Current Open API standard for REST APIs
Supported
Swagger 2.0
Weit verbreiteter API-Beschreibungsstandard
Supported
AWS / Azure / GCP
Hyperscaler REST APIs and API management
Supported
OData
SAP OData services with automatic XCSRF handling
Supported
ABAP / SAP ERP
ABAP Proxy generation from Open API definitions
Supported

KaTe Launchpad – more control during setup and operation

The KaTe Launchpad extends the RESTful Adapter with an integrated toolbox for developers and operations teams – directly usable from within the SAP Integration Suite.

Generator

Automatic generation of OpenAPI definitions, ABAP Proxy structures, and SAP Integration Suite Iflow channel configurations from existing ESR objects – significantly reducing configuration effort.

Service List Display & Tester

Overview of all configured REST API endpoints, HTTP methods, and authentication configurations. While the tester sends REST requests directly from the SAP Integration Suite, all results are immediately visible.

SAP Technology and Migration Consulting –
Future-Proof Integration

The KaTe GmbH is your competent partner for SAP technology and migration projects. Our focus is on the secure and smooth transformation of existing SAP PO landscapes to the modern SAP Integration Suite.

  • Migration from SAP PO to SAP Integration Suite – including analysis, architecture design, and technical implementation
  • Implementation and optimization of the SAP Edge Integration Cell – for flexible and secure hybrid integration
  • SAP BTP Consulting – use of modern services and tools for innovation and process automation
  • Technology-based Strategy Consulting – from cloud integration to API management
SAP PO → Integration Suite Migration
Structured Migration Without Operational Disruption

We analyze your existing RESTful interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite – ensuring continuous operation.

Learn more
SAP PO Adapter – 30-Day Free Trial
All SAP PO Adapters Without Upfront Payment

Test our SAP PO adapters for Kafka, MQTT, AMQP, AWS, RESTful and more – 30 days free of charge.

View all SAP PO Adapters
IntegraMon – SAP Monitoring
Central dashboard for all SAP CPI tenants & EIC instances

IntegraMon unites all SAP CPI tenants and Edge Integration Cells in a single dashboard – with proactive alerting, AI support, and automated KPI reports.

Discover IntegraMon

Frequently Asked Questions

Answers to the most important questions about the KaTe RESTful Adapter for SAP Integration Suite.

What is the KaTe RESTful Adapter for SAP CPI?

As a powerful middleware component, the KaTe RESTful Adapter for SAP Integration Suite connects SAP systems with REST APIs according to the Open API standard. It supports OpenAPI 3.x and Swagger 2.0 and enables 1:1 migration of existing interfaces from SAP Process Orchestration – drastically reducing development times.

What advantages does the adapter offer in API development?

The adapter offers the following development advantages:

  • Drastically reduced time required for JSON/XML translation and HTTP status routing
  • Existing ESR objects become Open APIs with just a few clicks
  • ABAP Proxies can be generated from Open API definitions (API First)
  • Established frameworks like ABAP Proxy generation and monitoring can continue to be used
Is the adapter compatible with SAP BTP and hybrid landscapes?

Yes. The adapter supports OAuth2 endpoints on the public internet as well as on-premise via SAP Cloud Connector. It is fully compatible with SAP BTP, SAP Cloud Integration, and the SAP Edge Integration Cell. Hyperscalers like AWS, Azure, and GCP are directly supported.

How does security work in the RESTful Adapter?

Because security is a top priority in enterprise environments, the adapter blocks non-compliant API calls and supports:

  • OpenID / JWT Authentifizierung
  • Custom OAuth2 (cloud and on-premise via Cloud Connector)
  • NTLM-Authentifizierung

This makes OAuth2 calls fully traceable – no black box. All authentication flows are visible in the SAP Integration Suite Monitor.

How are monitoring and debugging implemented?

All API operations and statuses are searchable and visible without overhead through automatic indexing of key/values of API operations in the SAP Integration Suite Monitor. HTTP status codes, OAuth2 flows, and API endpoints can be viewed directly in the monitor – without additional configuration.

Which SAP platforms are supported?

The KaTe RESTful Adapter runs on all current SAP platforms:

  • SAP Integration Suite (Cloud Integration / CPI)
  • SAP Business Technology Platform (BTP)
  • SAP Edge Integration Cell (EIC) – for hybrid on-premise/cloud scenarios
  • SAP Process Orchestration (PO) – via the separate SAP PO version of the adapter
How does ABAP Proxy generation work?

With the KaTe Launchpad Generator, ABAP Proxy structures can be generated directly from Open API definitions. Existing ESR objects from SAP PO can be used as a basis, so no new development is required. The generated proxies are fully compatible with SAP ABAP development environments.

How does automatic XCSRF token handling work?

SAP OData services require XCSRF tokens for write operations. The KaTe RESTful Adapter handles token management fully automatically, so OData clients can use SAP APIs without SAP-specific knowledge. Internal links are rewritten to frontend URLs in the process.

How does the installation and commissioning work?

Installation takes place in just a few steps directly in your SAP Integration Suite. After requesting the 30-day trial, you will receive access to the adapter within 48 hours. Our team will support you during onboarding, so initial productive scenarios run quickly.

What licensing models are available for the RESTful Adapter?

The KaTe RESTful Adapter is available with a 30-day free trial – after that, flexible licensing models are available. Because every corporate environment has different requirements, we would be happy to advise you individually on licensing options and prices. Contact us at info@kate-group.com.

Get Started Now

Ready for REST APIs in the SAP Integration Suite?

Contact us for a free 30-day trial or an individual consultation. We will set up your test run within 48 hours.

Categories
SAP Products

MQTT Adapter for SAP Integration Suite (CPI)

MQTT Adapter for SAP Integration Suite (CPI) – KaTe GmbH
SAP Integration Suite (CPI)

MQTT Adapter for
SAP Integration Suite

Connect SAP Cloud Integration with IoT devices, sensors, and MQTT brokers. Publish/Subscribe with wildcards, durable subscriptions, and Last Retained Messages – according to MQTT v3.1 and MQTT 5.

Verified SAP Partner 30-Day Free Trial IoT & MQTT 5 On-Premise & SAP BTP
Architecture Overview
SAP Cloud
Integration
Iflow
MQTT
KaTe MQTT
Adapter
SAP CPI
Broker
MQTT Broker
IoT · Cloud
On-Premise
MQTT v3.1 MQTT 5 Wildcards SSL/TLS Durable Sub QoS 0/1/2
Verified SAP Partner
30-Day Free Trial
MQTT v3.1 & MQTT 5
SAP Integration Suite & EIC
Listed on SAP App Center

MQTT for SAP Integration Suite –
IoT Integration Without Custom Development

The KaTe MQTT Adapter for SAP Integration Suite contains all necessary functions so that IoT scenarios can be integrated into SAP Cloud Integration quickly, securely, and with low maintenance.

MQTT v3.1 & MQTT 5
Since both MQTT standards are fully supported, both existing and new IoT scenarios can be realized without restrictions – including all MQTT 5 extensions.
  • MQTT v3.1 fully supported
  • MQTT 5 according to OASIS standard
  • User Properties & Message Expiry
  • Content Type & Response Topic
Publish / Subscribe
Because IoT scenarios require flexible topic structures, the adapter supports wildcards (+ and #) for topics as well as durable subscriptions and Last Retained Messages.
  • Topic wildcards + and #
  • Durable Subscriptions
  • Last Retained Messages
  • QoS 0, 1, and 2
Security & Authentication
Because security is particularly critical in IoT environments, the adapter supports SSL/TLS, username/password, and client certificates – ensuring all connections are secured.
  • SSL/TLS encryption
  • Username/Password authentication
  • Client certificates
  • Connection via SAP Cloud Connector
Flexible Payload Support
Whether XML, JSON, or binary payloads – the adapter processes all common data formats, so no additional conversion logic is needed in the Iflows.
  • XML and JSON natively
  • Arbitrary binary payloads
  • Automatic conversion
  • Flexible message structure
IoT & Mobile Scenarios
MQTT is the standard for IoT communication – optimized for networks with low bandwidth and high latency. Ideal for sensors, devices, and mobile applications.
  • Sensors and IoT devices
  • Mobile applications
  • Edge computing scenarios
  • SAP Edge Integration Cell (EIC)
Simple Migration from SAP PO
Existing MQTT interfaces from SAP Process Orchestration can be transferred 1:1 to the SAP Integration Suite – approx. 1–2 minutes per Iflow, preserving investments.
  • 1:1 migration from SAP PO
  • Minimal migration effort
  • Existing investments preserved
  • Custom migration plan possible

Why the KaTe MQTT Adapter
is the right choice

MQTT is the standard for IoT communication. The KaTe MQTT Adapter connects SAP Cloud Integration directly with your IoT infrastructure – without custom development and without maintenance effort.

1
MQTT v3.1 and MQTT 5
Since both MQTT standards are fully supported, all MQTT 5 extensions such as User Properties, Message Expiry, and Content Type are immediately usable – without restrictions.
2
Seamless IoT Integration
SAP Cloud Integration becomes part of your IoT infrastructure – so sensor data, device status, and control commands flow directly into your SAP processes, eliminating external intermediate layers.
3
Simple Migration from SAP PO
Existing MQTT interfaces from SAP Process Orchestration can be transferred with minimal effort – approx. 1–2 minutes per Iflow. This fully preserves your investments.
4
Flexible Connection Options
Whether directly, via SOCKS proxy, or via SAP Cloud Connector – the adapter connects to any MQTT broker in the cloud and on-premise, easily covering hybrid scenarios.

Get started easily – scale flexibly

1
Request Free Trial

Contact us – within 48 hours you will receive access to the adapter for your test environment.

2
Install Adapter

Since the installation in your SAP Integration Suite only requires a few steps, our team will support you during onboarding – so you can be productive quickly.

3
Go Live

Initial productive IoT scenarios run quickly. Scale as needed – without upfront investments.

Supported Brokers & Platforms

Whether Eclipse Mosquitto, HiveMQ, or AWS IoT Core – the KaTe MQTT Adapter is compatible with all common MQTT brokers and SAP platforms.

SAP Integration Suite
SAP Cloud Integration (CPI) – fully integrated
Supported
SAP BTP
SAP Business Technology Platform – cloud-native
Supported
SAP Edge Integration Cell
Hybrid on-premise/cloud scenarios
Supported
Eclipse Mosquitto
Open-source MQTT broker – widely used
Supported
HiveMQ
Enterprise MQTT broker for IoT
Supported
AWS IoT Core
Managed MQTT broker on AWS
Supported
Azure IoT Hub
Managed IoT platform on Azure
Supported
All MQTT-compliant Brokers
MQTT v3.1 and MQTT 5 compatible
Supported

KaTe Launchpad – more control during setup and operation

The KaTe Launchpad extends the MQTT Adapter with an integrated toolbox for developers and operations teams – directly usable from within the SAP Integration Suite.

Generator

Automatic generation of MQTT configurations, topic structures, and SAP Integration Suite Iflow channel definitions – significantly reducing configuration effort and sources of error.

Service List Display & Tester

Clear overview of all MQTT topics and subscriptions with an integrated tester – enabling developers to check connections and messages directly in the SAP Integration Suite.

SAP Technology and Migration Consulting –
Future-Proof Integration

The KaTe GmbH is your competent partner for SAP technology and migration projects. Our focus is on the secure and smooth transformation of existing SAP PO landscapes to the modern SAP Integration Suite.

  • Migration from SAP PO to SAP Integration Suite – including analysis, architecture design, and technical implementation
  • Implementation and optimization of the SAP Edge Integration Cell – for flexible and secure hybrid integration
  • SAP BTP Consulting – use of modern services and tools for innovation and process automation
  • Technology-based Strategy Consulting – from cloud integration to API management
SAP PO → Integration Suite Migration
Structured Migration Without Operational Disruption

We analyze your existing MQTT interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite – ensuring continuous operation.

Learn more
SAP PO Adapter – 30-Day Free Trial
All SAP PO Adapters Without Upfront Payment

Test our SAP PO adapters for Kafka, MQTT, AMQP, AWS, Azure, GCP and more – 30 days free of charge.

View all SAP PO Adapters
IntegraMon – SAP Monitoring
Central dashboard for all SAP CPI tenants & EIC instances

IntegraMon unites all SAP CPI tenants and Edge Integration Cells in a single dashboard – with proactive alerting, AI support, and automated KPI reports.

Discover IntegraMon

Frequently Asked Questions

Answers to the most important questions about the KaTe MQTT Adapter for SAP Integration Suite.

What is the KaTe MQTT Adapter for SAP Integration Suite?

As a powerful middleware component, the KaTe MQTT Adapter for SAP Integration Suite connects SAP Cloud Integration with IoT devices, sensors, and MQTT brokers – in the cloud and on-premise. It supports MQTT v3.1 and MQTT 5 according to the OASIS standard and allows the use of SAP Cloud Integration as part of IoT or mobile scenarios. As the successor to the MQTT Adapter for SAP Process Orchestration all existing interfaces can be seamlessly adopted.

Which MQTT features does the adapter offer?

With the adapter, the following MQTT features can be used:

  • Publish/Subscribe to MQTT topics with wildcards (+ and #)
  • Durable subscriptions and Last Retained Messages
  • MQTT 5 extensions: User Properties, Message Expiry, Content Type
  • XML, JSON, and arbitrary payloads
Is the adapter compatible with cloud and on-premise SAP environments?

Yes. Because hybrid scenarios are standard today,

  • Directly – for cloud brokers or publicly accessible brokers
  • Via SOCKS proxy – for connections via a proxy server
  • Via SAP Cloud Connector – for secure connections to your own data center
  • It is fully compatible with SAP BTP, SAP Cloud Integration, and the SAP Edge Integration Cell.

    How does the adapter support IoT and device integration with SAP?

    MQTT is the standard for IoT communication – lightweight, optimized for networks with low bandwidth and high latency. Thus, the KaTe MQTT Adapter connects SAP Cloud Integration directly with IoT devices, sensors, and MQTT brokers like Mosquitto, HiveMQ, AWS IoT Core, or Azure IoT Hub – so that sensor data flows directly into SAP processes.

    Why choose the KaTe MQTT Adapter instead of custom development?

    Since existing MQTT interfaces from SAP Process Orchestration can be transferred 1:1 to the SAP Integration Suite – approx. 1–2 minutes per Iflow – any custom development is eliminated. No maintenance costs, ready for immediate use, flexible licensing without upfront investments.

    Which MQTT brokers are supported?

    The adapter is compatible with all MQTT-compliant brokers – whether Eclipse Mosquitto, HiveMQ, AWS IoT Core, Azure IoT Hub, or your own on-premise brokers. Both MQTT v3.1 and MQTT 5 are fully supported, so there are no restrictions when choosing a broker.

    What security mechanisms does the MQTT Adapter offer?

    Because security is particularly critical in IoT environments, the adapte

    • SSL/TLS encryption for all connections
    • Username/Password authentication
    • Client certificates
    • li>Connection via SAP Cloud Connector for secure on-premise connection
    How does the migration from SAP PO to the SAP Integration Suite work?

    Existing MQTT configurations from SAP Process Orchestration can be adopted 1:1 – reducing the migration effort to approx. 1–2 minutes per Iflow. This means all existing investments are fully preserved while simultaneously utilizing the modern features of the SAP Integration Suite.

    On which SAP platforms does the MQTT Adapter run?

    The adapt

    • SAP Integration Suite (Cloud Integration / CPI) – fully integrated
    • SAP BTP – cloud-native scenarios
    • SAP Edge Integration Cell (EIC) – hybrid on-premise/cloud scenarios
    p>Since all three platforms are supported, the adapter is suitable for any SAP landscape.

    How does the installation and commissioning work?

    After requesting a free 30-day trial, you will receive access within 48 hours. Since the installation in the SAP Integration Suite only requires a few steps, our team will support you during onboarding – so you can be productive quickly. Initial productive IoT scenarios usually run within a few hours.

    Get Started Now

    Ready for MQTT in the SAP Integration Suite?

    Contact us for a free 30-day trial or a personal advisory call. We set up your test environment within 48 hours.

    Categories
    SAP Products

    Confluent Parallel Consumer Adapter for SAP Integration Suite

    Confluent Parallel Consumer Adapter for SAP Integration Suite – KaTe GmbH
    SAP Integration Suite (CPI)

    Confluent Parallel Consumer Adapter for
    SAP Integration Suite

    Achieve 10–500x higher throughput than the SAP standard adapter. By leveraging parallelization at the record-key level, Avro, Protocol Buffers, Schema Registry, and automated error handling, you ensure maximum performance in SAP Integration Suite and Edge Integration Cell.

    Verified SAP Partner Request a Demo 10–500x Higher Throughput Avro & Protocol Buffers
    Architecture Overview
    SAP Cloud
    Integration
    Iflow / EIC
    parallel
    KaTe Confluent
    Parallel Consumer
    SAP CPI
    Kafka Protocol
    Confluent /
    Apache Kafka
    Cloud · On-Premise · EIC
    10–500x Throughput Avro / Protobuf Schema Registry Batch Processing SASL_SSL OAuth2 Error Handling

    High-Throughput Kafka Integration –
    10–500x More Throughput Than SAP Standard

    The KaTe Confluent Parallel Consumer Adapter includes all functions of the Kafka Adapter. Additionally, it supplements these with parallelizable processing capabilities for maximum throughput.

    Publish & Subscribe
    SAP Cloud Integration Iflow messages are published as Kafka records, while Kafka records are subscribed to as Iflow messages. During this process, Kafka Key, Header, and Data are fully translated into Iflow Messages.
    • Configurable topics, partitions, and ack mode
    • Customizable consumer commits
    • Wildcards and durable subscriptions
    • Processing from beginning, end, or any position
    Parallelization & Throughput
    Because parallelization occurs at the record-key level instead of the partition level, a 10–500x higher throughput is achieved for single and batched records. Consequently, this happens without losing the functional order of related records.
    • 10–500x Higher Throughput
    • Parallelization at record-key level
    • Configurable thread pool
    • Batch processing (n records per Iflow)
    Security
    Since enterprise environments demand the highest security standards, all common Kafka security protocols for broker and ServiceRegistry connections are supported. This includes both OAuth2 and Client Certificate Authentication.
    • PLAIN, PLAIN_SASL, SASL_SSL
    • SASL-Plain / SASL-SCRAM
    • OAuth2 Authentication
    • Client Certificate Authentication
    Filtering & Flow Control
    Gain full control over throughput and processing order. Kafka records can be filtered before triggering an integration, ensuring that only relevant messages are processed.
    • Filtering by headers, keys, and data contents
    • Deduplication via offset or record header
    • Freely definable group names
    • Unordered and ordered scenarios
    Automated Error Handling
    Errors during deserialization, data transformation, or downstream processing can be handled automatically. Therefore, non-blocking and asynchronous processing is guaranteed even with faulty records.
    • Error forwarding to Error Topic / Dead Letter Topic
    • Deserialization errors automatically handleable
    • Non-blocking and asynchronous processing
    • Fine-grained error strategies configurable
    Avro, Protocol Buffers & Schema Registry
    Typical binary data formats are supported with Kafka-specific optimizations. As a result, Avro and Protocol Buffers are directly translated into XML – and vice versa.
    • Avro and Protocol Buffers support
    • Schema Registry integration
    • Integrated schema generation tool
    • JSON to XML transformation

    Processing Models Compared –
    Standard vs. Parallel Consumer

    The KaTe Confluent Parallel Consumer Adapter offers three processing models: Partition-Based Processing (SAP Standard), Key-Ordered Processing, and Unordered Processing. Thus, it provides maximum flexibility for different requirements.

    Verarbeitungsmodelle: Partition-Based Processing (1 Partition = 1 Thread), Key-Ordered Processing (Ordered per Message Key), Unordered Processing (Concurrent & Unordered)

    Why the Confluent Parallel Consumer Adapter
    is the Right Choice

    High-throughput Kafka integration with SAP Integration Suite – without increasing the partition count, with complete error handling and Avro/Protobuf support.

    1
    10–500x Higher Throughput
    Because parallelization occurs at the record-key level instead of the partition level, a drastically higher throughput is achieved – without increasing the partition count and with only a single consumer.
    2
    Automated Error Handling
    Errors during deserialization, data transformation, or downstream processing are automatically forwarded to an error topic or dead letter topic – non-blocking and without any operational disruption.
    3
    Avro, Protocol Buffers & Schema Registry
    Typical binary data formats are fully supported, so integrated schema generation tools can be used directly without third-party tools.
    4
    Easy Migration from SAP PO
    Existing interfaces can be easily imported because the adapter is fully compatible with the SAP Integration Suite – investments in SAP PO integrations can be easily transferred.

    KaTe vs. SAP Standard

    Feature KaTe Adapter SAP Standard
    Parallelism Model
    Record-Key-Level
    Partition-Level
    Throughput Scaling
    10–500x higher
    Partition increase required
    Automated Error Handling
    ✓ Yes
    ✗ No
    Avro / Protocol Buffers
    ✓ Yes
    ✗ No
    Batch Processing
    ✓ Yes
    ✗ No
    Filtering & Deduplication
    ✓ Yes
    ✗ No
    Freely Definable Group Names
    ✓ Yes
    ✗ No
    Advanced Monitoring
    Consumer Lag, 1:1 Record-Tracking
    ✗ Not supported

    Summary

    FeatureSAP Standard Kafka AdapterConfluent Parallel Consumer Adapter
    Parallelism modelLimited by number of Kafka partitionsConfigurable thread pool enables high parallelism with a single consumer
    Ordering guaranteesOrdering guaranteed only per partitionOrdering guaranteed at message key level (optional), with parallel execution across different keys
    Throughput scalingRequires increasing partition count for scalingScales without increasing partitions; up to 10–500x higher throughput possible.
    Iflow executionBlocked calls partially or completely stop message processingNon-blocking and asynchronous processing without message processing being blocked by errors or individual "slow" records.
    Automated Error handlingNot supported, some errors are not directly visible (deserialization)Error handling for deserialization / data transformation or iflow execution errors can be set automatically. Errors are then logged (as error messages) and ignored or forwarded to an error topic/dead letter topic.
    Offset /Group Name controlNot supportedAny type of start possible (start, end) of the offset or reprocessing of arbitrary offsets. Group names freely definable.
    Message acknowledgmentOffset commits at partition levelFine-grained, message-level acknowledgment and processing control
    Advanced MonitoringNot supportedRich monitoring user experience (consumer lag, 1:1 recognition of which Kafka record generated which Iflow execution at a glance and out of the box)
    FilteringNot supported, nur manuel in jedem einzelnen iflow implementierbarFiltering with headers or data contents to avoid unnecessary message load
    Avro/Protobuf and JSON with schema registryNot supportedSupported, including data transformation and schema generation to XML

    Getting Started – flexibel skalieren

    1
    Request Free Trial

    Contact us – within 48 hours you will receive access to the adapter for your test environment.

    2
    Install Adapter

    Installation in your SAP Integration Suite is completed in just a few steps. Furthermore, our team will support you during onboarding.

    3
    Go Live

    Initial productive scenarios start quickly. Consequently, you can scale as needed – without upfront investments.

    Supported Platforms & Kafka Distributions

    Whether Confluent Cloud, Apache Kafka, or Azure Event Hubs – the KaTe Confluent Parallel Consumer Adapter is compatible with all common Kafka distributions and SAP platforms.

    SAP Integration Suite
    SAP Cloud Integration (CPI) – fully integrated
    Supported
    SAP Edge Integration Cell
    Hybrid on-premise/cloud scenarios (EIC)
    Supported
    Confluent Platform
    Confluent Cloud and on-premise with Schema Registry
    Supported
    Apache Kafka
    Open Source Apache Kafka – all versions
    Supported
    Azure Event Hubs
    Azure Event Hubs with Kafka protocol
    Supported
    AWS MSK
    Amazon Managed Streaming for Apache Kafka
    Supported
    SAP BTP
    SAP Business Technology Platform – Cloud-native
    Supported
    Avro / Protocol Buffers
    Binary data formats with Schema Registry
    Supported

    KaTe Launchpad – more control during setup and operations

    The KaTe Launchpad extends the Confluent Parallel Consumer Adapter with an integrated toolbox for developers and operations teams. As a result, all key functions are accessible directly from the SAP Integration Suite.

    Generator

    Kafka configurations, topic structures, schema definitions, and SAP Integration Suite Iflow channel definitions are generated automatically. Therefore, the configuration effort for new Kafka integration scenarios is significantly reduced, accelerating deployment.

    Service List Display & Tester

    The Service List Display provides an overview of all configured Kafka topics, consumer groups, broker connections, and Schema Registry entries. Meanwhile, the integrated tester enables sending and receiving Kafka records directly from the SAP Integration Suite.

    SAP Technology and Migration Consulting –
    Future-Proof Integration

    KaTe GmbH is your competent partner for SAP technology and migration projects. Our focus lies on the secure and smooth transformation of existing SAP PO landscapes to the modern SAP Integration Suite.

    • Migration from SAP PO to SAP Integration Suite – including analysis, architecture design, and technical implementation
    • Implementation and optimization of the SAP Edge Integration Cell – for flexible and secure hybrid integration
    • SAP BTP Consulting – use of modern services and tools for innovation and process automation
    • Technology-based Strategy Consulting – from cloud integration to API management
    SAP PO → Integration Suite Migration
    Structured Migration Without Operational Disruption

    We analyze your existing Kafka interfaces in SAP PO and develop a structured migration plan for the SAP Integration Suite. Consequently, your Kafka integrations are migrated without operational disruption.

    Learn more
    Kafka Adapter for SAP PO – Request a Demo
    All SAP PO Adapters Without Upfront Payment

    Test our SAP PO Adapters for Kafka, MQTT, AMQP, AWS and more – 30 days for free.

    View all SAP PO Adapters
    IntegraMon – SAP Monitoring
    Central Dashboard for all SAP CPI Tenants & EIC Instances

    IntegraMon unites all SAP CPI tenants and Edge Integration Cells in a single dashboard. It features proactive alerting, AI support, and automated KPI reports.

    Discover IntegraMon

    Frequently Asked Questions

    Answers to the most important questions about the KaTe Confluent Parallel Consumer Adapter for SAP Integration Suite.

    What is the Confluent Parallel Consumer Adapter for SAP Integration Suite?

    As a specialized high-throughput extension of the KaTe Kafka Adapter, the KaTe Confluent Parallel Consumer Adapter optimizes processing on SAP Integration Suite or Edge Integration Cell (EIC). It contains all functionalities of the KaTe Kafka Adapter and supplements them with parallelizable processing functions for high throughput – up to 10–500x more than the SAP standard adapter.

    What core features does the Confluent Parallel Consumer Adapter offer?

    The adapter provides the following core features:

    • Parallelization at record-key level (instead of partition level)
    • Batch processing (n records as a single Iflow message)
    • Filtering by headers, keys, and data contents
    • Deduplication via offset or record header
    • Automated Error Handling (Error Topic / Dead Letter Topic)
    • Avro/Protocol Buffers with Schema Registry and automatic schema generation
    Which security standards are supported?

    Because enterprise environments demand the highest security standards, the adapter supports all common Kafka security protocols: PLAIN, PLAIN_SASL, SASL_SSL, SASL-Plain/SASL-SCRAM, OAuth2, as well as Client Certificate Authentication for broker and ServiceRegistry connections.

    How does the adapter support high performance and error handling?

    Since parallelization occurs at the record-key level, the adapter enables 10–500x higher throughput for single and batched records without losing the functional order of related records. Furthermore, errors during deserialization, data transformation, or downstream processing can be automatically forwarded to an error destination or documented and ignored – non-blocking and asynchronous.

    How does the adapter differ from standard SAP Cloud Integration adapters?

    While the SAP standard adapter parallelizes at the partition level, the KaTe Confluent Parallel Consumer Adapter offers compared to the SAP standard:

    • 10–500x higher throughput without increasing the partition count
    • Parallelization without blocking by individual "slow" records
    • Automated error handling even for deserialization errors
    • Avro/Protobuf support with Schema Registry
    • Batch processing in a single Iflow execution
    • Filtering and deduplication at high data throughput
    • Freely definable group names and arbitrary stream positions
    On which SAP platforms does the Confluent Parallel Consumer Adapter run?

    The adapter is compatible with SAP Cloud Integration (CPI) and SAP Edge Integration Cell (EIC). Thus, both pure cloud scenarios and hybrid on-premise/cloud environments are covered. Furthermore, it is listed in the SAP App Center and therefore officially available as an SAP partner solution.

    Which Kafka distributions are supported?

    Whether Confluent Cloud, Apache Kafka (all versions), Azure Event Hubs with Kafka protocol, or AWS MSK – the adapter is compatible with all common Kafka distributions, as it uses the standardized Kafka protocol. Additionally, Confluent Platform on-premise with Schema Registry is fully supported.

    How does Avro and Protocol Buffers support work?

    The adapter supports Avro and Protocol Buffers natively, so binary data formats are directly translated into XML – and vice versa. Thanks to the integrated Schema Registry integration and the included schema generation tool, manual schema maintenance is eliminated. Meanwhile, JSON-to-XML transformation is also available out of the box.

    How does installation and deployment work?

    After starting the 30-day trial, you will receive access to the adapter within 48 hours. Installation in your SAP Integration Suite is completed in just a few steps, as the KaTe team supports you during onboarding. Initial productive scenarios typically start within a few days – without upfront investments or lengthy project phases.

    What licensing models are available for the Confluent Parallel Consumer Adapter?

    The KaTe Confluent Parallel Consumer Adapter is available as a flexible license based on your actual usage volume. After the free 30-day trial, you can choose between different licensing options. Contact us for an individual offer so we can find the right model for your requirements together.

    Get Started Now

    Ready for High-Throughput Kafka Integration?

    Contact us for a free 30-day trial or a personal advisory call. We set up your test environment within 48 hours.