secondsky/sap-skills

sap-btp-integration-suite

Enterprise integration solutions using SAP Integration Suite on BTP.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/secondsky/sap-skills --skill sap-btp-integration-suite

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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:

groovy
// 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

xml
<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

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
secondsky
コミュニティ

sap-hana-cli

Assists with SAP HANA Developer CLI (hana-cli) for database development and administration. Use when: installing hana-cli, connecting to SAP HANA databases, inspecting database objects (tables, views, procedures, functions), managing HDI containers, executing SQL queries, converting metadata to CDS/EDMX/OpenAPI formats, managing SAP HANA Cloud instances, working with BTP CLI integration, or troubleshooting hana-cli commands. Covers: 91 commands, 17+ output formats, HDI container management, clou

1時間の導入数
1
GitHub Stars
501
更新日
11月13日
secondsky
コミュニティ

sap-sqlscript

This skill should be used when the user asks to "write a SQLScript procedure", "create HANA stored procedure", "implement AMDP method", "optimize SQLScript performance", "handle SQLScript exceptions", "debug HANA procedure", "create table function", "inspect a browser-based Datasphere SQL editor with Microsoft Edge CDP", or mentions SQLScript, SAP HANA procedures, AMDP, EXIT HANDLER, or code-to-data paradigm. Comprehensive SQLScript development guidance for SAP HANA database programming includin

1時間の導入数
1
GitHub Stars
501
更新日
11月13日
secondsky
コミュニティ

sap-sac-planning

SAP Analytics Cloud (SAC) planning guidance for planning models, planning-enabled stories, data actions, multi actions, version management, data locking, calendar/input workflows, allocations, value driver trees, BPC live planning, and Seamless Planning with SAP Datasphere. Use this for planning design, planning APIs, data action debugging, planning performance reviews, and authenticated SAC planning story triage in Microsoft Edge via CDP; use sap-sac-scripting for non-planning SAC scripts and s

1時間の導入数
2
GitHub Stars
497
更新日
11月13日
secondsky
コミュニティ

claude-automation-recommender

Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.

1時間の導入数
1
GitHub Stars
497
更新日
11月13日