MCPInstall

sap-btp-integration-suite

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.

Installs
607
Last 24h
+9
Trending rank
#9264
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/secondsky/sap-skills --skill sap-btp-integration-suite
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads sap-btp-integration-suite automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

CapabilityPurposeKey Artifact
Cloud IntegrationA2A/B2B/B2G integrationIntegration Flow (iFlow)
API ManagementAPI lifecycle & governanceAPI Proxy
Event MeshEvent-driven architectureTopics & Queues
Edge Integration CellHybrid deploymentKubernetes runtime
Integration AdvisorB2B mapping automationMIG/MAG
Trading Partner ManagementPartner onboardingAgreements
GraphUnified data APIBusiness Data Graph
Integration AssessmentTechnology selectionISA-M
Migration AssessmentPO migration planningExtraction & 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 validation passed but tenant import remains pending.

Integration Flow Structure

Sender → [Adapter] → Integration Process → [Adapter] → Receiver
                           ↓
              ┌────────────┴────────────┐
              │  Message Processing     │
              │  - Content Modifier     │
              │  - Router/Filter        │
              │  - Mapping              │
              │  - Splitter/Aggregator  │
              │  - Script               │
              │  - External Call        │
              └─────────────────────────┘

Common Flow Steps

CategorySteps
RoutingRouter, Filter, Multicast, Recipient List
TransformationContent Modifier, Mapping, Converter, Script
SplittingGeneral Splitter, Iterating Splitter, EDI Splitter
PersistenceData Store, Write Variable, JMS Send
ExternalRequest Reply, Send, Poll Enrich, Content Enricher
SecurityEncryptor, Decryptor, Signer, Verifier
Error HandlingException Subprocess, Escalation Event

Adapter Categories

Protocol Adapters: HTTP, HTTPS, SFTP, FTP, AMQP, JMS, Kafka, AS2, AS4, SOAP, OData Application Adapters: SuccessFactors, Ariba, Salesforce, ServiceNow, Workday Database Adapters: JDBC (Oracle, SQL Server, PostgreSQL, HANA, DB2) Cloud Adapters: AWS (S3, SQS, SNS), Azure (Service Bus, Storage), Google Cloud

Scripting Guidelines

Prefer standard steps over scripts. When scripting is necessary:

// Access message body
def body = message.getBody(String.class)

// Access headers
def header = message.getHeader("HeaderName", String.class)

// Access properties
def prop = message.getProperty("PropertyName")

// Modify body
message.setBody(newBody)

// Add header
message.setHeader("NewHeader", "value")

// Logging (use SLF4J)
def log = org.slf4j.LoggerFactory.getLogger("script")
log.info("Processing message")

Best Practices:

  • Use XmlSlurper.parse(Object) instead of parseText(String) for large payloads
  • Use StringBuilder for string concatenation
  • Never use TimeZone.setDefault() (VM-wide impact)
  • Never write credentials to headers (tracing exposes them)

API Management Development

API Proxy Structure

Client → Proxy Endpoint → [Policies] → Target Endpoint → Backend
              ↓                              ↓
         PreFlow                        PreFlow
         Conditional Flows              Conditional Flows
         PostFlow                       PostFlow
              ↓                              ↓
         Fault Rules                    Fault Rules

Policy Categories

CategoryPolicies
SecurityOAuth 2.0, Verify API Key, Basic Auth, SAML, Access Control
TrafficQuota, Spike Arrest, Concurrent Rate Limit, Response Cache
MediationAssign Message, Extract Variables, JSON/XML Transform, XSL Transform
ExtensionJavaScript, Python Script, Service Callout
Threat ProtectionJSON/XML Threat Protection, Regular Expression Protection
LoggingMessage Logging, Statistics Collector

Common Policy Attributes

<PolicyName enabled="true" continueOnError="false" async="false">
  <!-- Policy configuration -->
</PolicyName>

Message Quality of Service

Exactly-Once Processing

Use when duplicates must be prevented:

  1. JMS Queues - Transactional message storage
  2. Idempotent Process Call - Duplicate detection via ID mapping
  3. Data Store - Persistent message tracking

Idempotent Pattern

Sender → [ID Mapping] → Check Duplicate → Process → [ID Mapping Complete]
                              ↓ (duplicate)
                         Return Cached Response

Edge Integration Cell

Deployment Requirements

  • Kubernetes cluster (EKS, AKS, GKE, OpenShift, RKE2)
  • Minimum: 4 worker nodes, 4 vCPU, 16GB RAM each
  • Storage: 100GB+ persistent volume
  • Network: Ingress controller, DNS configuration

Workflow

  1. Activate Edge Integration Cell in Integration Suite
  2. Prepare Kubernetes cluster (platform-specific)
  3. Deploy Edge Lifecycle Management Bridge
  4. Deploy Edge Integration Cell solution
  5. Configure keystore synchronization
  6. Deploy integration content

Troubleshooting

Common Issues

IssueResolution
Adapter connection failedCheck credentials, firewall, Cloud Connector
Message mapping errorValidate source/target structures, check XPath
TimeoutIncrease adapter timeout, optimize mapping
Memory issuesStream large payloads, reduce logging
Duplicate messagesImplement idempotent processing
Keystore sync failedVerify certificate validity, check permissions

Monitoring Hierarchy

Integration Suite → Monitor → Integrations and APIs
    ├── Message Processing → All Integration Flows
    ├── Manage Integration Content → Deployed Artifacts
    ├── Manage Security → Keystores, Credentials
    └── Manage Stores → Data Stores, Variables, Queues

Limits Reference

ResourceLimit
Integration flows per tenantVaries by plan
JMS queues30 per tenant (standard)
Data stores100MB total storage
Message processing log retention30 days
Attachment size40MB
API proxies (APIM)Based on service plan
Business data graphs500/account, 50/subaccount

Bundled Resources

Reference Documentation

Detailed guides available in references/ directory:

Core Development:

  • cloud-integration.md - iFlow development, steps, patterns, best practices
  • iflow-package-authoring.md - Importable iFlow package structure and HTTPS-to-SFTP generation rules
  • adapters.md - All 80+ adapter configurations (HTTP, SFTP, OData, RFC, etc.)
  • scripting.md - Groovy/JavaScript patterns, APIs, and templates
  • api-management.md - API proxy development, 34 policies, Developer Hub
  • security.md - Authentication, keystores, certificates, credentials

Capabilities:

  • edge-integration-cell.md - Hybrid Kubernetes deployment guide
  • event-mesh.md - Topics, queues, brokers, webhooks, EDA patterns
  • integration-advisor-tpm.md - B2B integration, MIGs, MAGs, partner management
  • graph-odata.md - Business Data Graph, OData provisioning
  • data-space-integration.md - Catena-X, EDC, sovereign data exchange
  • migration-assessment.md - PO migration, ISA-M, technology mapping

Operations:

  • operations-monitoring.md - Message monitoring, stores, connectivity tests
  • content-transport.md - TMS, CTS+, MTAR, manual export/import
  • troubleshooting.md - Error resolution, diagnostics, HTTP error catalog

Templates

Ready-to-use templates in templates/ directory:

  • https-to-sftp-iflow-package/ - Reviewable unzipped importable iFlow template for HTTPS sender to SFTP receiver scenarios
  • groovy-script-template.groovy - Common script patterns
  • api-policy-template.xml - Policy configuration template

Documentation Links

Official Sources

Capability-Specific

Release Notes

  • What's New: Check what-s-new-for-sap-integration-suite-79cd682.md in documentation
  • Patch Releases: Check patch-release-notes-for-sap-integration-suite-58595b5.md

FAQ

What does the sap-btp-integration-suite skill do?

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.

How do I install sap-btp-integration-suite?

Run npx skills add https://github.com/secondsky/sap-skills --skill sap-btp-integration-suite in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sap-btp-integration-suite/ (personal) or .claude/skills/sap-btp-integration-suite/ (project).

Which AI agents can use sap-btp-integration-suite?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is sap-btp-integration-suite safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains sap-btp-integration-suite?

It is published by secondsky in secondsky/sap-skills. It has 607 recorded installs.

More from secondsky/sap-skills

View all →

sap-abap

secondsky/sap-skills

Comprehensive ABAP development skill for SAP systems. Use when writing ABAP code, working with internal tables, structures, ABAP SQL, object-oriented programming, RAP (RESTful Application Programming Model), CDS views, EML statements, ABAP Cloud development, string processing, dynamic programming, RTTI/RTTC, field symbols, data references, exception handling, or ABAP unit testing. Covers both classic ABAP and modern ABAP for Cloud Development patterns.

Data & Databases1.3K installs

sap-fiori-tools

secondsky/sap-skills

Develops SAP Fiori applications using SAP Fiori tools extensions for VS Code and SAP Business Application Studio. Use when: generating Fiori Elements or Freestyle SAPUI5 applications, configuring Page Editor for List Report or Object Page, working with annotations and Service Modeler, setting up deployment to ABAP or Cloud Foundry, creating adaptation projects, using Guided Development, previewing with mock data or live data, configuring SAP Fiori launchpad, or using AI-powered generation with Project Accelerator/Joule. Technologies: SAP Fiori Elements, SAPUI5, OData V2/V4, CAP, SAP BTP, ABAP, Cloud Foundry, fiori-mcp-server (MCP tools for AI-assisted generation).

AI & Agents1.2K installs

sap-cap-capire

secondsky/sap-skills

SAP Cloud Application Programming Model (CAP) development skill using Capire documentation. Use when: building CAP applications, defining CDS models, implementing services, working with SAP HANA/SQLite/PostgreSQL databases, deploying to SAP BTP Cloud Foundry or Kyma, implementing Fiori UIs, handling authorization, multitenancy, or messaging. Covers CDL/CQL/CSN syntax, Node.js and Java runtimes, event handlers, OData services, and CAP plugins.

Backend & APIs1.2K installs

sap-btp-developer-guide

secondsky/sap-skills

Develops business applications on SAP Business Technology Platform (BTP) using CAP (Node.js/Java) or ABAP Cloud. Use when: building cloud applications on SAP BTP, deploying to Cloud Foundry or Kyma runtimes, integrating with SAP HANA Cloud, implementing SAP Fiori UIs, connecting to remote SAP systems, building multitenant SaaS applications, extending SAP S/4HANA or SuccessFactors, setting up CI/CD pipelines, implementing observability, or following SAP development best practices. Keywords: SAP BTP, Business Technology Platform, CAP, Cloud Application Programming Model, ABAP Cloud, Cloud Foundry, Kyma, SAP HANA Cloud, SAP Fiori, SAPUI5, CI/CD, observability, multitenant, SaaS, SAP BTP ABAP environment, SAP Business Application Studio, SAP Cloud SDK, SAP Integration Suite, SAP Event Mesh, SAP Connectivity Service, SAP Destination Service, XSUAA, OAuth, OpenID Connect, OData, CDS, Core Data Services, ABAP CDS, ABAP RESTful Application Programming Model, RAP, ABAP development, SAP BTP deve

DevOps & Cloud1.1K installs

sap-btp-best-practices

secondsky/sap-skills

SAP BTP best practices for enterprise architecture, account management, security, and operations, with verification evidence tracked in the repository ledger. Use when planning BTP implementations, setting up account hierarchies, configuring environments, implementing authentication, designing CI/CD pipelines, establishing governance, building Platform Engineering teams, implementing failover strategies, or managing application lifecycle on SAP BTP. Keywords: SAP BTP, account hierarchy, global account, directory, subaccount, Cloud Foundry, Kyma, ABAP, SAP Identity Authentication, CI/CD, governance, Platform Engineering, failover, multi-region, SAP BTP best practices

sap-btp-connectivity

secondsky/sap-skills

SAP BTP Connectivity skill covering Destination Service, Connectivity Service, Cloud Connector, Connectivity Proxy, and Transparent Proxy for Kubernetes. Use when configuring destinations (HTTP, RFC, LDAP, MAIL, TCP), setting up cloud-to-on-premise connectivity, implementing OAuth and principal propagation, deploying connectivity proxies in Kubernetes/Kyma, troubleshooting connectivity errors (405, 407, 503), or configuring multitenancy.

DevOps & Cloud950 installs

Popular backend & apis skills

View category →

find-skills

vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

OfficialBackend & APIs4.1M installs

entra-app-registration

microsoft/azure-skills

Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.

OfficialBackend & APIs566.7K installs

This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).

Backend & APIs514.8K installs

embedded-captions

heygen-com/hyperframes

Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.

Backend & APIs453.3K installs

entra-agent-id

microsoft/azure-skills

Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).

OfficialBackend & APIs336.6K installs

neon

neondatabase/agent-skills

Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.

Backend & APIs237.1K installs