/sap-btp-integration-suite

name: sap-btp-integration-suite
description: "Enterprise integration solutions using SAP Integration Suite on BTP. Covers Cloud Integration (iFlows), API Management, Event Mesh, Edge Integration Cell, Integration Advisor, Trading Partner Management, and Migration Assessment. Use for building integration flows, managing API proxies, event-driven architectures, B2B/EDI integrations, hybrid deployments, adapter configuration, Groovy/JavaScript message processing, and troubleshooting."


license: GPL-3.0
metadata:
  maintainer: "Eduard Jiglau"
  maintainer_email: "hello@sap-ai-skills.com"
  website: "https://sap-ai-skills.com"
  version: "2.4.1"
  last_verified: 2025-11-27
  documentation_source: "https://github.com/SAP-docs/sap-btp-integration-suite"
  sap_help_portal: "https://help.sap.com/docs/integration-suite"
  status: production
  keywords: [sap integration suite, cloud integration, cpi, iflow, api management, apim, event mesh, edge integration cell, integration advisor, trading partner management, b2b integration, edi integration, migration assessment, graph, odata provisioning, message mapping, groovy script, adapter configuration, sftp adapter, http adapter, odata adapter, rfc adapter, amqp adapter, kafka adapter, jms queue, data store, idempotent processing]

allowed-tools:
  - Read
  - Bash
  - Glob
  - Grep
  - WebFetch
  - WebSearch

SAP BTP Integration Suite Development

Related Skills

• **sap-btp-cloud-platform**: Use for BTP subaccount, subscription, entitlement, and role setup
• **sap-btp-connectivity**: Use for destinations, Cloud Connector, and hybrid connectivity dependencies
• **sap-api-style**: Use for API proxy documentation, OpenAPI quality, and API lifecycle standards
• **sap-btp-cloud-transport-management**: Use for transporting integration artifacts across landscapes

When to Use This Skill

Use this skill when building or troubleshooting Cloud Integration iFlows, API Management proxies, Event Mesh topics/queues, Edge Integration Cell deployments, Integration Advisor mappings, Trading Partner Management flows, or migration assessment from Process Orchestration.

Table of Contents

• [Quick Reference](#quick-reference)
• [Capability Overview](#capability-overview)
• [Cloud Integration Development](#cloud-integration-development)
• [API Management Development](#api-management-development)
• [Event Mesh](#event-mesh)
• [Edge Integration Cell](#edge-integration-cell)
• [Integration Advisor](#integration-advisor)
• [Trading Partner Management](#trading-partner-management)
• [Migration Assessment](#migration-assessment)
• [Bundled Resources](#bundled-resources)

Quick Reference

| Capability | Purpose | Key Artifact | |------------|---------|--------------| | Cloud Integration | A2A/B2B/B2G integration | Integration Flow (iFlow) | | API Management | API lifecycle & governance | API Proxy | | Event Mesh | Event-driven architecture | Topics & Queues | | Edge Integration Cell | Hybrid deployment | Kubernetes runtime | | Integration Advisor | B2B mapping automation | MIG/MAG | | Trading Partner Management | Partner onboarding | Agreements | | Graph | Unified data API | Business Data Graph | | Integration Assessment | Technology selection | ISA-M | | Migration Assessment | PO migration planning | Extraction & Analysis |

---

Capability Overview

Cloud Integration

Build and run integration flows across cloud, on-premise, and hybrid landscapes for A2A, B2B, and B2G scenarios. Supports 80+ adapters and real-time message processing.

**Core Components**:

• Integration Flows (iFlows) - Visual message processing pipelines
• Adapters - Protocol/application connectors (SFTP, HTTP, OData, RFC, AMQP, Kafka, etc.)
• Message Mapping - Graphical/XSLT/Groovy transformations
• Data Stores & Variables - Persistence for stateful processing
• Security Material - Keystores, credentials, PGP keys

API Management

Complete API lifecycle management with security, traffic control, and developer engagement.

**Core Components**:

• API Proxies - Facade layer for backend services
• Policies (34 types) - Security, traffic, mediation rules
• Developer Hub - API portal for developers
• Products - API bundles with access control
• Analytics - Usage metrics and insights

Event Mesh

Publish and consume business events across your enterprise ecosystem for event-driven architectures.

Edge Integration Cell

Hybrid runtime for processing data within private landscapes while designing in the cloud. Deploy on Kubernetes (EKS, AKS, GKE, OpenShift, RKE2).

Integration Advisor

AI-powered B2B content development supporting UN/EDIFACT, SAP IDoc, ASC X12. Creates Message Implementation Guidelines (MIGs) and Mapping Guidelines (MAGs).

Trading Partner Management

Streamline B2B relationships with partner profiles, agreement templates, and automated runtime artifact generation. Supports AS2, SFTP, FTP protocols.

---

Cloud Integration Development

Importable iFlow Generation

When a user asks to generate an iFlow package, ZIP, importable archive, `.iflw`, or complete Cloud Integration artifact, use `references/iflow-package-authoring.md` before writing files. Do not invent a flat XML-only package.

For HTTPS-to-SFTP scenarios, start from `templates/https-to-sftp-iflow-package/` and preserve its directory layout:

.project
META-INF/MANIFEST.MF
metainfo.prop
src/main/resources/parameters.prop
src/main/resources/parameters.propdef
src/main/resources/scenarioflows/integrationflow/HTTPS_to_SFTP_Template.iflw

Customize only the externalized placeholders unless the user asks for a different design:

• `{{HTTPS_ENDPOINT_PATH}}`
• `{{SFTP_HOST}}`
• `{{SFTP_PORT}}`
• `{{SFTP_DIRECTORY}}`
• `{{SFTP_FILENAME}}`
• `{{SFTP_CREDENTIAL_ALIAS}}`

Keep credentials, tenant URLs, private hostnames, certificates, and deployed runtime state out of generated artifacts. If no SAP Cloud Integration tenant is available for import testing, say that local package structure and XML val