Sap Btp Integration Suite

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
• Capability Overview
• Cloud Integration Development
• API Management Development
• Event Mesh
• Edge Integration Cell
• Integration Advisor
• Trading Partner Management
• Migration Assessment
• Bundled Resources

Quick Reference

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

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

Common Policy Attributes

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

Message Quality of Service

Exactly-Once Processing