ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
Cloud Integration
Builds and runs integration flows that process, route and map messages between cloud and on-premise systems, SAP and non-SAP, through prebuilt adapters; available only under an SAP Integration Suite plan.
Cloud Integration builds and runs integration flows: each describes how a message sent by one system is processed, routed to its receivers and mapped from the sender's data structure to the receiver's. Systems connect through prebuilt adapters, and an adapter SDK is there for a protocol those leave out. SAP publishes prepackaged integration content whose predefined flows can be extended, and OData APIs on the SAP Business Accelerator Hub reach a tenant's resources from outside. It is not available separately, only under a service plan of SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp.
Where it sits
Lives in
Provides
Integration flowsBTPIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is [destinations](capability:destinations), and brokering events between systems is [Event Mesh](capability:event-mesh).
Part of
SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.
Designs
Designing Event-Driven ApplicationsDesigning Event-Driven Applicationsevent mediation and bridge
Who is behind it
SAPSAPMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
For integration flows
- Protocols
- HTTPSFTPSMTPOData V2OData V4SOAPRFCAMQPKafkaTCPWebSocketGraphQLSQL
Connections
Group by10 of 10 connections
NodeRelationBasis
Functional
Integration flowsIntegration flowsMoving and transforming messages between systems in middlewareSAP only
provides
stated
provides Integration flows
The integration flow is its unit of work: it says how a message from one participant is processed, which receivers it goes to depending on its content, and how the data structure is mapped between sender and receiver. Senders and receivers attach through prebuilt adapters or one built with the adapter SDK, and SAP's predefined flows can be extended in place of starting from an empty one.
“As one key part of integration content, integration flows describe how a message sent from one participant is processed by SAP Cloud Integration.”“Integration flows also specify mappings of the data structure between sender and receiver or the endpoints of sender and receiver participants.”“SAP Cloud Integration comes with a set of prebuilt adapters.”“Use the adapter SDK to build your own custom adapters for additional connectivity needs.”“You can extend predefined integration flows according to your requirements.”
Moving and transforming messages between systems in middleware
Technical
cap-bp-ragcap-bp-ragEvent-driven RAG app with CAP, Cloud Integration and SAP HANA Cloudindependent, cap
connected from
derived
connected from cap-bp-rag
the ingestion side calls in: Cloud Integration posts the Business Partner record with the embedding it created for it
“3. **Cloud Integration → CAP** — call the `insert` API with the embedding.”
Event-driven RAG app with CAP, Cloud Integration and SAP HANA Cloud
cloud-integration-pipeline-datastore-extension-uicloud-integration-pipeline-datastore-extension-uiCAP and Fiori elements app for managing Cloud Integration datastoressap official, btp
connected from
derived
connected from cloud-integration-pipeline-datastore-extension-ui
calls the Pipeline Extension's HTTP API integration flows to read datastore entries and to restart, move and delete them
“This application connects to the HTTP API Integration Flows of the Pipeline Extension package and provides a user-friendly interface to inspect, restart, move, and delete datastore entries — without requiring direct API calls or an API client like Postman.”
CAP and Fiori elements app for managing Cloud Integration datastores
connects to
stated
connects to Apache Kafka
An integration flow uses the Kafka sender or receiver adapter.
Fetching records from Kafka topics into an integration flow with the Kafka sender adapter, and sending messages to the Kafka broker with the Kafka receiver adapter.
“With the Kafka Adapter, SAP Cloud Integration allows you to connect to an external Kafka broker via Kafka protocol. With the help of the Kafka Sender adapter you can receive messages. Use the Kafka Receiver adapter to send messages to the Kafka broker.”“You use the Kafka Sender adapter to connect to an external Kafka broker via Kafka protocol and to fetch messages.”“Transport Protocol
TCP”
A distributed event-streaming platform. For the things here it is the broker that carries messages between the parts of one application.
cloud-integration-pipeline-datastore-extension-uicloud-integration-pipeline-datastore-extension-uiCAP and Fiori elements app for managing Cloud Integration datastoressap official, btp
needed by
derived
needed by cloud-integration-pipeline-datastore-extension-ui
the tenant that runs the Pipeline Extension's API integration flows this application calls, and whose runtime issues the OAuth credentials it is configured with
“Access to an SAP Cloud Integration tenant with the [Process Integration Pipeline Extension - Restart via Data Store](https://hub.sap.com/package/processintegrationpipelineextensionrestartviadatastore/overview) package deployed, including the two optional API Integration Flows:”“OAuth credentials (Client ID, Client Secret, Token URL) for the Cloud Integration runtime”
CAP and Fiori elements app for managing Cloud Integration datastores
btp-private-link-approuterbtp-private-link-approuter@sap/approuter patterns in front of SAP Private Link Servicesap official, btp
optionally used by
derived
optionally used by btp-private-link-approuter
the Cloud Integration scenarios; the frontend-extension scenario uses SAP Build Work Zone, standard edition instead
the consumer in two of the three scenarios, reaching SAP S/4HANA on Azure and Azure Blob Storage through the proxy
“The SAP Cloud Integration capability of SAP Integration Suite enables enterprises to connect different systems and applications in hybrid and cloud landscapes, that are developed and maintained on different technology stacks.”“The main idea of this architecture is to use the Application Router as a proxy for the private connectivity between Azure Blob Storage and SAP Cloud Integration.”
@sap/approuter patterns in front of SAP Private Link Service
SAP-samples/digital-manufacturing-extension-samplesSAP-samples/digital-manufacturing-extension-samplesSamples for the six extension types of SAP Digital Manufacturingsap official, digital-manufacturing
optionally used by
derived
optionally used by SAP-samples/digital-manufacturing-extension-samples
An integration extension sample is used.
The integration samples are built in Cloud Integration itself: a copy of the SAP-delivered BAPI Service Processor artifact, edited to call a non-SAP receiver, with the XSLT customisation applied to the iFlow's mapping.
“Go to SAP Cloud Integration and click on "Build and Develop Integration content" icon.”“You have access to the SAP CI tenant”
Samples for the six extension types of SAP Digital Manufacturing
teched2024-IN280teched2024-IN280TechEd 2024 session on Integration Suite between SAP IBP and otherssap official, btp
used by
derived
used by teched2024-IN280
the service the standard and community packages are copied into and the flows are deployed and run on.
“The integration between SAP IBP and 3rd party systems such as Amazon S3 or Snowflake uses SAP Cloud Integration as a middleware.”
TechEd 2024 session on Integration Suite between SAP IBP and others
Trading Partner ManagementTrading Partner ManagementPartner profiles and agreements for B2B exchange in Integration Suitesap official, btp
used by
derived
used by Trading Partner Management
Holds the Partner Directory an activated agreement is pushed into, and runs the integration flows that carry out the exchange.
“Push the auto-generated runtime artefacts of the B2B scenarios as defined in the agreements into the Partner Directory of SAP Cloud Integration.”“This application achieves the goal by using the entities and artifacts provided by the other capabilities of SAP Integration Suite such as:”
Partner profiles and agreements for B2B exchange in Integration Suite
Lineage
SAP Integration SuiteSAP Integration SuiteIntegration service on BTP with Cloud Integration and API Managementsap official, btp
part of
stated
part of SAP Integration Suite
“To provide a comprehensive integration experience, these services are not available separately, but only as part of the Integration Suite service plan.”“SAP Integration Suite combines Cloud Integration, API Management, Integration Advisor, Open Connectors, and other integration capabilities into a cohesive and simplified toolkit for enterprise integration.”
Integration service on BTP with Cloud Integration and API Management
Download
Learn more
Readings
- Powering Enterprise-Ready Agentic AI with SAP Integration SuitePowering Enterprise-Ready Agentic AI with SAP Integration SuiteA Devtoberfest 2026 session (INT-31) from SAP Integration Suite product management on the MCP gateway. The demo creates an MCP server in a design package from an API already deployed on the tenant, exposes two of its 300-odd resources as tools, attaches authentication and quota policies on a policies tab, and publishes the deployed endpoint as an AI product in Developer Hub of API Management, where an agent subscribes and receives a token, URL, key and secret; the calls then show up in monitoring, in message processing logs and in the analytics dashboard, which is the MCP exposure and the tool governance the edges rest on. Three AI features inside Cloud Integration follow: a content migration agent that converts a PI/PO Java mapping into a Groovy script and generates a second integration flow for its lookup, memory profiling during a flow simulation, and root-cause analysis on a failed message processing log.SAP Developers, published 2026-10-07SAP Developers, YouTube — SAP Developers playlists
- From opportunity to decision: Intelligent Credit Checks with AI Adapter in SAP Cloud IntegrationFrom opportunity to decision: Intelligent Credit Checks with AI Adapter in SAP Cloud IntegrationDevtoberfest 2026 session INT-12, in which an integration consultant builds two scenarios around the AI adapter in Cloud Integration. The first integration flow is triggered by a Salesforce opportunity event, reads that customer's history from S/4HANA over its OData APIs and calls a sales agent through the AI adapter, which writes a credit status and a credit rating band back onto the opportunity for the sales representative to act on; the second calls an operations agent from an exception subprocess and raises a Jira ticket carrying the suggested resolution, the related past tickets and the average resolution time recorded for the issue. The session places the adapter among the HTTP, Open Connectors and application-specific adapter routes, names its SAP Generative AI Hub, OpenAI and Claude variants, and gives the build effort as roughly 50 to 60 hours for the OData calls against the adapter configuration's two tabs.SAP Developers, published 2026-09-23SAP Developers, YouTube — SAP Developers playlists
- Cloud Integration- Activating Enterprise Messaging Capabilities for JMS Queue - CFCloud Integration- Activating Enterprise Messaging Capabilities for JMS Queue - CFTraces a JMS iFlow deployment failure on Cloud Integration (Cloud Foundry) — ERROR_MISSING_SERVICE_KEY — to the Message Queues (Enterprise Messaging) capability being switched off on the tenant rather than a missing service key, since an edition upgrade does not turn it on by itself. Resolves it by enabling Message Queues under Manage Capabilities, which restarts the tenant, then redeploying the affected iFlows.Pavan_Koppula1, published 2026-07-21Pavan_Koppula1, SAP Community
27 more
- Managing JMS Queues Programmatically with the new SAP Cloud Integration JMS OData APIManaging JMS Queues Programmatically with the new SAP Cloud Integration JMS OData APIThe new JMS OData API on Cloud Integration exposes MessagingQueues and MessagingMessages entities, letting a client list, inspect, retry and move JMS messages without opening the monitoring UI, from Cloud Integration 7.52.x on Cloud Foundry and 8.41 on the Edge Integration Cell runtime. It works through OAuth 2.0 client-credentials authentication against a Process Integration Runtime service instance, a fixed row cap with time-window slicing used in place of offset paging because queues change between requests, and a consistent OData error envelope for the codes the surface returns.MarcoKoch, published 2026-06-01MarcoKoch, SAP Community
- SAP Cloud Integration (CI/CPI) - Reusable Script Collection Pattern for Sensitive Data MaskingSAP Cloud Integration (CI/CPI) - Reusable Script Collection Pattern for Sensitive Data MaskingOpens with the question compliance teams ask about Cloud Integration, whether an integration team based outside Europe with Message Monitoring access can read the personal data in a logged payload, and answers that in most standard configurations it can. The pattern against it is a reusable Groovy script collection plus one global variable holding the masking rules: a script near the start of an iFlow AES-encrypts the original payload into a header or property and replaces values in the body by value pattern first and field-name keyword second, a second script restores the original just before the sender, so a Log Payload step anywhere in the flow captures the masked body while the target system still receives the real data. The post names its own limits, that pattern-based masking is heuristic and that CPI trace can capture the payload before the scripts run, and grounds the pattern in GDPR Articles 5(1)(f), 25, 32 and 44-49, reading the EDPB's Guidelines 05/2021 to mean that access from a country without an EU adequacy decision, uncovered by Standard Contractual Clauses or another valid transfer mechanism, can itself constitute a cross-border transfer.AdarshRao, published 2026-05-25AdarshRao, SAP Community
- End to End Currency Conversion Integration using SAP Integration Suite (SAP CPI)End to End Currency Conversion Integration using SAP Integration Suite (SAP CPI)A hands-on build of a currency-conversion integration flow in Cloud Integration: an HTTPS sender adapter takes JSON input, a Request-Reply step calls an external exchange-rate API, and a Groovy script converts the amount and formats it as an HTML table before a Mail Adapter delivers the result. Most of the walkthrough is the Exception Subprocess added after hitting HTTP 500 and 429 errors in testing, which captures the error message, response code and message-processing-log ID and turns them into a readable response instead of a raw stack trace.shahabaz, published 2026-04-09shahabaz, SAP Community
- Building a Real‑Time Currency Conversion iFlow using SAP Cloud Integration (CPI)Building a Real‑Time Currency Conversion iFlow using SAP Cloud Integration (CPI)A step-by-step build of a currency-conversion integration flow in Cloud Integration: an HTTPS sender adapter accepts JSON, a content modifier stores the currencies and amount as exchange properties, and a Request-Reply step calls an external rate API before a Groovy script renders the result as an HTML table. A Global Exception Subprocess centralizes error handling for the whole flow, turning the MPL ID, error type and message into HTML and mailing it as a notification to a support address.RajeshwerRao_G_1, published 2026-04-01RajeshwerRao_G_1, SAP Community
- Centralized Error Handling in SAP Cloud IntegrationCentralized Error Handling in SAP Cloud IntegrationBusiness integration flows in Cloud Integration route their runtime errors to a shared Central Error Logger flow through an Exception Subprocess and a ProcessDirect adapter, instead of each flow handling failures on its own. The logger normalises the incoming error data — flow name, message ID, correlation ID, timestamps — and formats it into an HTML email sent through a Mail Receiver Adapter. The author validated the same logger flow, unchanged, against a second, more complex business flow with routers and multiple email notifications.vishaladhikari, published 2026-03-27vishaladhikari, SAP Community
- Stop Building From Scratch: Unlocking SAP Cloud Integration’s Standard ContentStop Building From Scratch: Unlocking SAP Cloud Integration’s Standard ContentArgues against building integrations from scratch by pointing to the Discover space of Cloud Integration: over 700 prebuilt integration packages and nearly 4000 iFlows, covering common scenarios such as S/4HANA-to-Salesforce business-partner and order sync, included at no extra cost under an SAP Integration Suite licence. Walks through where to find and copy a package, and the support trade-off it creates: SAP keeps supporting the standard baseline, but once a flow is directly modified the customer owns the lifecycle of that change, which the author sets against patterns like overlay mappings and wrapper orchestrators that preserve support.Punith_Oswal, published 2025-12-19Punith_Oswal, SAP Community
- Parallel Data Filtering and Dropbox Integration Using SAP Cloud IntegrationParallel Data Filtering and Dropbox Integration Using SAP Cloud IntegrationA step-by-step build of an integration flow in Cloud Integration: a Start Timer triggers the flow, a Parallel Multicast splits student records by gender through XPath filters, and each branch uploads its file to Dropbox over a Receiver Adapter authorized against a Dropbox app's OAuth2 credentials. An Exception Subprocess captures the error message and a Mail Adapter sends it over SMTP, centralizing error handling and an email notification for the whole flow.Vurumind03, published 2025-12-10Vurumind03, SAP Community
- Microsoft GRAPH API - Read and extract attachments of Outlook email from Cloud IntegrationMicrosoft GRAPH API - Read and extract attachments of Outlook email from Cloud IntegrationBuilds an integration flow in Cloud Integration that authenticates to the Microsoft Graph API with an OAuth2 Client Credentials credential and an HTTP Receiver Adapter, then calls the Outlook inbox by MessageID to retrieve an email's attachment. A Groovy script using the pdfbox and fontbox libraries extracts the text from a PDF attachment, as an alternative to placing the attachment on SFTP unchanged or fetching the whole message with its attachment through the $value query.ChaithraShanmugam, published 2025-12-09ChaithraShanmugam, SAP Community
- SAP Neo Retires – Integration Developers Must Know Before Migrating from Neo to CFSAP Neo Retires – Integration Developers Must Know Before Migrating from Neo to CFWalks through what changes when Cloud Integration moves from the Neo environment to Cloud Foundry under SAP Integration Suite: custom adapters move from an Eclipse-plugin deployment to Integration Adapter artifacts managed in Cloud Integration's Design and Monitor applications, Neo's environment variables (HC_APPLICATION, HC_HOST, HC_REGION and others) map to Cloud Foundry's TENANT_NAME, VCAP_SERVICES and PORT, and OAuth clients for API access move from Neo administration tools to XSUAA under Integration Suite. Covers the same shift for security materials, transport management and monitoring, ahead of Neo's end of maintenance on 31 December 2028.SivaS, published 2025-12-03SivaS, SAP Community
- Beyond REST: Exploring GraphQL API Integration in SAP BTP Integration SuiteBeyond REST: Exploring GraphQL API Integration in SAP BTP Integration SuiteBecause Cloud Integration in SAP Integration Suite ships no native GraphQL adapter, the author builds a GraphQL integration flow on the standard HTTP adapter: a Groovy script assembles the query or mutation payload and sets the JSON content type, and a JSON-to-XML converter turns the response into something message mapping can consume. The walkthrough uses the public Countries API to stand in for a real order-synchronisation flow between an e-commerce platform and SAP S/4HANA.Avinash_Vaidya, published 2025-11-11Avinash_Vaidya, SAP Community
- Lessons Learned: Fetching Learning History from SuccessFactors LMS Using OData APIsLessons Learned: Fetching Learning History from SuccessFactors LMS Using OData APIsA walkthrough of pulling SuccessFactors LMS Learning History records through its OData V4 API: the mandatory criteria/targetUserID filter, the errors that appear without it, and the $metadata endpoint used to confirm entity names, since the API returns one student at a time and never in bulk. Builds the integration flow in Cloud Integration as a Groovy script that loops over a list of student IDs, calls the API with a bearer token per student and aggregates the JSON responses into one payload.aayushaggarwal, published 2025-09-17aayushaggarwal, SAP Community
- Cloud Integration with Document AICloud Integration with Document AIWalks through connecting Cloud Integration to SAP Document AI: an iFlow posts a prescription PDF to Document AI's job API, polls the job endpoint until it completes, and a groovy script reads back the result, keeping only the fields above a stated 60% confidence threshold. The scenario is a hospital extracting a new patient's past illnesses, allergies and blood group from uploaded prescriptions, matched against a custom extraction schema.PriyankaChak, published 2025-08-10PriyankaChak, SAP Community
- Optimized IDoc Routing in SAP CI with Value Mapping and Groovy-Based Receiver DeterminationOptimized IDoc Routing in SAP CI with Value Mapping and Groovy-Based Receiver DeterminationShreyasShenoy07 replaces SAP PI/PO's single shared IDoc destination with a receiver-determination pattern built in Cloud Integration: a generic iFlow reads the IDoc's EDI_DC40 header, looks up the sender identifier and the receiver list in two Value Mapping tables keyed by sender system and IDoc type, and a Groovy script evaluates each receiver's XPath condition before routing the message to a receiver-specific iFlow over the ProcessDirect adapter. Adding or changing a receiver becomes a Value Mapping edit instead of an iFlow redeployment, and the same IDoc can fan out to several receivers when more than one condition matches.ShreyasShenoy07, published 2025-08-08ShreyasShenoy07, SAP Community
- Process Integration Pipeline Extension - Restart via Data StoreProcess Integration Pipeline Extension - Restart via Data StoreOn SAP Cloud Integration's Process Integration Pipeline, a message that exhausts its JMS retries lands in a Dead Letter Queue with no API to query or move it, and the JMS broker carries a hard size limit. This package, published on SAP Business Accelerator Hub, replaces that path with Data Store entries written through the pipeline's custom exception-handling exit, a scheduled Restart Job Integration Flow, and two optional HTTP APIs for on-demand restarts and Data Store management. Entry names encode the partner ID, the pipeline stage, the message ID and a retry count, so messages can be filtered and restarted by scenario instead of moved one by one in the queue monitor.mate_moricz, published 2025-07-23mate_moricz, SAP Community
- Automating iFlow Documentation with SAP Integration Suite and Gemini AIAutomating iFlow Documentation with SAP Integration Suite and Gemini AIAn integration flow built from Cloud Integration's own steps — timer start, parallel multicast, process calls, join and gather, and a data store write — retrieves another iFlow's design-time metadata and resources (Groovy scripts, XSLT mappings, EDMX schemas) through the IntegrationDesigntimeArtifacts OData API on SAP Integration Suite. The walkthrough gives each flow step's configuration, the OData endpoints and sample request/response payloads, and an exception subprocess for error logging, before assembling the retrieved XML and posting it to Google's Gemini API to generate a technical specification document stored back in a datastore.Andrew-Fawzy, published 2025-07-18Andrew-Fawzy, SAP Community
- SAP SOAP Sender & Receiver Adapters: Your Integration Game ChangersSAP SOAP Sender & Receiver Adapters: Your Integration Game ChangersA step-by-step build of two integration flows in Cloud Integration: a SOAP Sender Adapter, bound to an uploaded WSDL, that extracts an order number from an inbound SOAP request via XPath and enriches it with a shipment date fetched from the public Northwind OData service before mapping the result back into the SOAP response. A second flow's SOAP Receiver Adapter takes the reverse path, converting an inbound JSON request to XML and forwarding it to that first flow's SOAP backend, authenticated with Basic auth against a WSDL-derived operation name.Rishikasairi, published 2025-06-24Rishikasairi, SAP Community
- SFTP Authentication Setup in SAP BTP Integration Suite: A Step-by-Step Guide.SFTP Authentication Setup in SAP BTP Integration Suite: A Step-by-Step Guide.A walkthrough of configuring the SFTP adapter's three authentication modes in Cloud Integration — username/password, public key and dual — each set up through Security Material and a Known Hosts entry generated from an SSH key pair. The sender and receiver integration flows it builds convert an OData response to CSV and move the file over SFTP, exercising the adapter and message-conversion steps the flow editor provides.NaveenReddy_06, published 2025-06-24NaveenReddy_06, SAP Community
- How to Perform Initial Loads from S/4HANA to Advanced Event Mesh with Odata PollHow to Perform Initial Loads from S/4HANA to Advanced Event Mesh with Odata PollWalks through building a Cloud Integration flow that polls the S/4HANA Business Partner OData API on a timer, splits the response into individual records, and publishes each as an event to Advanced Event Mesh through its adapter, with the topic set dynamically from a grouping property. Selects fields and expands associations with $select/$expand against an EDMX from the API Business Hub, and works around the OData V2 adapter's lack of JSON support by falling back to the HTTP adapter with an XML-to-JSON converter. Flags the trade-off: the pattern needs no backend change beyond activating the API, but the polled payload has to stay aligned with whatever event format the ERP pushes on change.AlexPfeil, published 2025-04-04AlexPfeil, SAP Community
- How to Configure Retry Mechanism in SAP BTP CI/IS to Handle Only Connectivity Errors when using AEMHow to Configure Retry Mechanism in SAP BTP CI/IS to Handle Only Connectivity Errors when using AEMShows how to configure a Cloud Integration iFlow with an AEM sender so only connectivity errors trigger a retry: a Groovy script reads the CamelHttpResponseCode header and looks it up in a value map, and a router then sends a transient failure such as a 408 timeout down the retry path, where the retry limit set in AEM applies, and an error needing manual intervention, such as a 401, down a path that ends the flow at once and emails the team. It applies only to receiver adapters that return CamelHttpResponseCode, among them HTTP, SOAP, IDoc and OData. It builds on an earlier post of the author's, which this one does not name, where an email goes out after the final retry attempt.Jayabalaji_Sakthivel, published 2025-01-21Jayabalaji_Sakthivel, SAP Community
- SAP PI Migration to BTP Integration Suite Patterns and learning experiencesSAP PI Migration to BTP Integration Suite Patterns and learning experiencesWalks through the integration patterns an SAP PI migration project moved onto SAP Cloud Integration iFlows — API Management proxies fronting calls into on-premise SAP systems over XI/SOAP via Cloud Connector, SFTP transfers, and eventing routes — and the operational lessons from running it: sizing JMS queues, choosing exactly-once JMS queues over Cloud Integration's Data Store for XI receiver adapters and at-least-once JMS for XI sender adapters, and workarounds for gaps in the migration tooling. The API Management proxies handle JWT validation against a non-SAP identity provider, IP filtering and OData-to-OpenAPI conversion in front of the iFlows.saikrishna_kalivarapu2, published 2024-12-04saikrishna_kalivarapu2, SAP Community
- SFTP File Level Checks in SAP BTP Cloud IntegrationSFTP File Level Checks in SAP BTP Cloud IntegrationFor an SFTP flow in Cloud Integration that an external party triggers, the post recommends polling with SFTP Poll-Enrich rather than relying on the Sender SFTP adapter and its built-in scheduler, and because Poll-Enrich polls one file per trigger, the design is a Main flow whose Looping Process Call repeatedly invokes a Local Integration Process that holds the Poll-Enrich step. On top of that design, it adds four router conditions, each checked against SAP_PollEnrichMessageFound, CamelLoopIndex, CamelFileName or CamelFileLength: no file found on the first poll, no more files left mid-loop, more than one file present when exactly one should be processed, and an empty file, each letting the flow terminate or raise an exception instead of failing on an unhandled read.Srishti_Gupta, published 2024-09-16Srishti_Gupta, SAP Community
- SAP Event Mesh: S4 HANA On-Prem and SAP CI(BTP IS) through WebSocket and WebhooksSAP Event Mesh: S4 HANA On-Prem and SAP CI(BTP IS) through WebSocket and WebhooksA step-by-step walkthrough of wiring Event Mesh to publish and consume events between an on-premise S/4HANA system and Cloud Integration, contrasting persistent queues (one subscriber, kept until consumed) against unpersisted topics, and WebSocket's AMQP transport against webhook delivery for the same queue. Two tested findings support it: a queue consumer running in continuous consumption mode receives a message ahead of a webhook on the same topic, and a message stays queued and is retried (almost 8770 times in under a minute, in the author's test) until the consumer processes it successfully.FarooqAhmed, published 2023-10-03FarooqAhmed, SAP Community
- SAP Cloud Integration chamber of horrorsSAP Cloud Integration chamber of horrorsA Devtoberfest 2026 integration-track session that goes through anti-patterns in Cloud Integration iFlows: scripts that re-implement flow steps or make external calls, the ESB_Messaging.send role on every sender channel, default flow-step names, dependence on undocumented platform internals, code that rewrites what the Groovy and Java libraries already hold, XML namespaces stripped to simplify XPath, HTTP calls between iFlows on one tenant where ProcessDirect would stay inside it, externalised parameters too few or too many, and MPL attachments left switched on in production. Each one comes with how to spot it — long scripts, jar files for SFTP communication, the design guidelines and upgrade readiness checks, or a rule in the presenter's own CPILint run locally or in a pipeline — and that pass over flow steps, sender roles, adapters and the message processing log is what the Integration flows edge rests on. The questions afterwards cover the GitHub integration in Cloud Integration, the absence of an official MCP server for building iFlows, and whether generated code shifts the choice between mapping, XSLT and scripting.SAP DevelopersSAP Developers, YouTube — SAP Developers playlists
- Conversational search for the Cloud Integration capabilityConversational search for the Cloud Integration capabilityCloud Integration content becomes searchable in natural language through three architectures SAP's abstract names: MCP servers, retrieval-augmented generation and knowledge graphs, set against the work of analysing and governing a growing SAP Integration Suite tenant. The abstract names the three and does not say which is built or how they compare. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Vadim Klimov, written here from SAP's abstract; the recording is not yet published.Vadim Klimov, SAP TechEd — session catalogue
- Explore version control and automation with GitHub in Cloud IntegrationExplore version control and automation with GitHub in Cloud IntegrationGitHub access set up in Cloud Integration: integration flows committed and versioned from Cloud Integration's own tools, several people working on the same artifacts, and a commit that triggers a CI/CD pipeline. The abstract states what the GitHub connection does and stops before the branch model, the pipeline's steps or which pipeline service runs them. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Marco Ertel, Morten Wittrock, Patrick Kelleher, Shivani Borkar and Tobin Sydneysmith, written here from SAP's abstract; the recording is not yet published.SAP TechEd — session catalogue
- Governance, automation, and observability in Cloud IntegrationGovernance, automation, and observability in Cloud IntegrationGovernance controls in Cloud Integration for developers and architects, automations written against its public OData API, and monitoring across Cloud Integration and SAP Cloud ALM with AI-assisted error analysis. The abstract names the OData API as the automation surface and does not list the controls or the operations the API exposes. A TechEd 2026 session (Wednesday 28 October, Berlin; also IN208V, virtual), presented by Morten Wittrock and Sunny Kapoor, written here from SAP's abstract; the recording is not yet published.SAP TechEd — session catalogue
- Evolution of the Code10 CI Accelerator add-on for SAP Integration SuiteEvolution of the Code10 CI Accelerator add-on for SAP Integration SuiteThe Code10 CI Accelerator, a partner add-on that puts a process monitor over pipeline concepts and patterns in Cloud Integration, the Edge Integration Cell runtime and more of SAP Integration Suite, and how it has changed as the suite has. The add-on is not in the atlas, so the edges rest on the Integration Suite capabilities it monitors; the abstract names no pipeline pattern and no feature of the add-on. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Antonio Valladares Fernandez, written here from SAP's abstract; the recording is not yet published.SAP TechEd — session catalogue
Others providing
Compare all 2 on the Integration flows page →Integration flowsIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is destinations, and brokering events between systems is Event Mesh.SAP only
- integration-suite-partner-directory-accelerator-for-pipeline-conceptintegration-suite-partner-directory-accelerator-for-pipeline-conceptA Java Swing desktop tool that maintains the Partner Directory entries the Pipeline for Cloud Integration reads at runtime.sap official, btpJava Swing tool maintaining Partner Directory entries for the Pipeline
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, integration-and-messaging
History in the atlas
- HTTP, SFTP, SMTP, OData V2, OData V4, SOAP, RFC, AMQP, Kafka, TCP, WebSocket, GraphQL, SQL
- The use case for receiving Kafka messages lists the Kafka sender adapter as a documented contribution, and the graph held no edge from Cloud Integration to Kafka. From SAP's adapter pages, which name the Kafka protocol and, in the adapter's General tab, TCP as its transport.
- First seen.
For your agent
- Ref
artifact:btp-cloud-integration- JSON
- /artifacts/btp-cloud-integration.json
- MCP
- Connecting an agent