sap-btp-integration-suite
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSAP BTP Integration Suite Development
SAP BTP Integration Suite 开发
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
- sap-btp-cloud-platform: 用于BTP子账户、订阅、权限及角色设置
- sap-btp-connectivity: 用于目标配置、Cloud Connector及混合连接依赖管理
- sap-api-style: 用于API代理文档、OpenAPI质量及API生命周期标准管理
- sap-btp-cloud-transport-management: 用于跨环境传输集成工件
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.
在构建或排查Cloud Integration iFlows、API Management代理、Event Mesh主题/队列、Edge Integration Cell部署、Integration Advisor映射、Trading Partner Management流程,或是从Process Orchestration迁移评估时,使用该技能。
Table of Contents
目录
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 |
| 能力 | 用途 | 核心工件 |
|---|---|---|
| Cloud Integration | A2A/B2B/B2G集成 | Integration Flow (iFlow) |
| API Management | API生命周期与治理 | API Proxy |
| Event Mesh | 事件驱动架构 | 主题与队列 |
| Edge Integration Cell | 混合部署 | Kubernetes运行时 |
| Integration Advisor | B2B映射自动化 | MIG/MAG |
| Trading Partner Management | 合作伙伴入驻 | 协议 |
| Graph | 统一数据API | 业务数据图谱 |
| Integration Assessment | 技术选型 | ISA-M |
| Migration Assessment | PO迁移规划 | 提取与分析 |
Capability Overview
能力概述
Cloud Integration
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
为A2A、B2B和B2G场景构建并运行跨云、本地及混合环境的集成流。支持80+种适配器及实时消息处理。
核心组件:
- Integration Flows (iFlows) - 可视化消息处理流水线
- Adapters - 协议/应用连接器(SFTP、HTTP、OData、RFC、AMQP、Kafka等)
- Message Mapping - 图形化/XSLT/Groovy转换
- Data Stores & Variables - 有状态处理的持久化存储
- Security Material - 密钥库、凭证、PGP密钥
API Management
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
具备安全管控、流量控制及开发者互动功能的完整API生命周期管理。
核心组件:
- API Proxies - 后端服务的 facade 层
- Policies(34种)- 安全、流量、中介规则
- Developer Hub - 面向开发者的API门户
- Products - 带访问控制的API捆绑包
- Analytics - 使用指标与洞察
Event Mesh
Event Mesh
Publish and consume business events across your enterprise ecosystem for event-driven architectures.
在企业生态系统内发布和消费业务事件,支撑事件驱动架构。
Edge Integration Cell
Edge Integration Cell
Hybrid runtime for processing data within private landscapes while designing in the cloud. Deploy on Kubernetes (EKS, AKS, GKE, OpenShift, RKE2).
在私有环境内处理数据、同时在云端进行设计的混合运行时。可部署于Kubernetes(EKS、AKS、GKE、OpenShift、RKE2)。
Integration Advisor
Integration Advisor
AI-powered B2B content development supporting UN/EDIFACT, SAP IDoc, ASC X12. Creates Message Implementation Guidelines (MIGs) and Mapping Guidelines (MAGs).
支持UN/EDIFACT、SAP IDoc、ASC X12的AI驱动型B2B内容开发工具。可创建消息实施指南(MIGs)和映射指南(MAGs)。
Trading Partner Management
Trading Partner Management
Streamline B2B relationships with partner profiles, agreement templates, and automated runtime artifact generation. Supports AS2, SFTP, FTP protocols.
通过合作伙伴档案、协议模板及自动化运行时工件生成,简化B2B关系管理。支持AS2、SFTP、FTP协议。
Cloud Integration Development
Cloud Integration 开发
Importable iFlow Generation
可导入iFlow生成
When a user asks to generate an iFlow package, ZIP, importable archive, , or complete Cloud Integration artifact, use before writing files. Do not invent a flat XML-only package.
.iflwreferences/iflow-package-authoring.mdFor HTTPS-to-SFTP scenarios, start from and preserve its directory layout:
templates/https-to-sftp-iflow-package/.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.iflwCustomize 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.
当用户要求生成iFlow包、ZIP文件、可导入归档、或完整Cloud Integration工件时,先参考再编写文件。请勿创建纯XML的扁平包。
.iflwreferences/iflow-package-authoring.md对于HTTPS转SFTP场景,从开始,并保留其目录结构:
templates/https-to-sftp-iflow-package/.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除非用户要求不同设计,否则仅自定义外部化占位符:
{{HTTPS_ENDPOINT_PATH}}{{SFTP_HOST}}{{SFTP_PORT}}{{SFTP_DIRECTORY}}{{SFTP_FILENAME}}{{SFTP_CREDENTIAL_ALIAS}}
请勿在生成的工件中包含凭证、租户URL、私有主机名、证书及已部署运行时状态。若无法获取SAP Cloud Integration租户进行导入测试,请说明本地包结构和XML验证已通过,但租户导入仍待完成。
Integration Flow Structure
集成流结构
Sender → [Adapter] → Integration Process → [Adapter] → Receiver
↓
┌────────────┴────────────┐
│ Message Processing │
│ - Content Modifier │
│ - Router/Filter │
│ - Mapping │
│ - Splitter/Aggregator │
│ - Script │
│ - External Call │
└─────────────────────────┘发送方 → [适配器] → 集成流程 → [适配器] → 接收方
↓
┌────────────┴────────────┐
│ 消息处理 │
│ - 内容修改器 │
│ - 路由器/过滤器 │
│ - 映射 │
│ - 拆分器/聚合器 │
│ - 脚本 │
│ - 外部调用 │
└─────────────────────────┘Common Flow Steps
常见流程步骤
| Category | Steps |
|---|---|
| Routing | Router, Filter, Multicast, Recipient List |
| Transformation | Content Modifier, Mapping, Converter, Script |
| Splitting | General Splitter, Iterating Splitter, EDI Splitter |
| Persistence | Data Store, Write Variable, JMS Send |
| External | Request Reply, Send, Poll Enrich, Content Enricher |
| Security | Encryptor, Decryptor, Signer, Verifier |
| Error Handling | Exception Subprocess, Escalation Event |
| 分类 | 步骤 |
|---|---|
| 路由 | 路由器、过滤器、多播、接收方列表 |
| 转换 | 内容修改器、映射、转换器、脚本 |
| 拆分 | 通用拆分器、迭代拆分器、EDI拆分器 |
| 持久化 | 数据存储、写入变量、JMS发送 |
| 外部交互 | 请求回复、发送、轮询增强、内容增强器 |
| 安全 | 加密器、解密器、签名器、验证器 |
| 错误处理 | 异常子流程、升级事件 |
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
协议适配器: HTTP、HTTPS、SFTP、FTP、AMQP、JMS、Kafka、AS2、AS4、SOAP、OData
应用适配器: SuccessFactors、Ariba、Salesforce、ServiceNow、Workday
数据库适配器: JDBC(Oracle、SQL Server、PostgreSQL、HANA、DB2)
云适配器: AWS(S3、SQS、SNS)、Azure(服务总线、存储)、谷歌云
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 instead of
XmlSlurper.parse(Object)for large payloadsparseText(String) - Use for string concatenation
StringBuilder - Never use (VM-wide impact)
TimeZone.setDefault() - Never write credentials to headers (tracing exposes them)
优先使用标准步骤而非脚本。当必须使用脚本时:
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")最佳实践:
- 处理大负载时,使用而非
XmlSlurper.parse(Object)parseText(String) - 使用进行字符串拼接
StringBuilder - 切勿使用(影响整个虚拟机)
TimeZone.setDefault() - 切勿将凭证写入头部(追踪日志会暴露凭证)
API Management Development
API Management 开发
API Proxy Structure
API代理结构
Client → Proxy Endpoint → [Policies] → Target Endpoint → Backend
↓ ↓
PreFlow PreFlow
Conditional Flows Conditional Flows
PostFlow PostFlow
↓ ↓
Fault Rules Fault Rules客户端 → 代理端点 → [策略] → 目标端点 → 后端服务
↓ ↓
PreFlow PreFlow
条件流程 条件流程
PostFlow PostFlow
↓ ↓
故障规则 故障规则Policy Categories
策略分类
| Category | Policies |
|---|---|
| Security | OAuth 2.0, Verify API Key, Basic Auth, SAML, Access Control |
| Traffic | Quota, Spike Arrest, Concurrent Rate Limit, Response Cache |
| Mediation | Assign Message, Extract Variables, JSON/XML Transform, XSL Transform |
| Extension | JavaScript, Python Script, Service Callout |
| Threat Protection | JSON/XML Threat Protection, Regular Expression Protection |
| Logging | Message Logging, Statistics Collector |
| 分类 | 策略 |
|---|---|
| 安全 | OAuth 2.0、验证API密钥、基础认证、SAML、访问控制 |
| 流量 | 配额、流量抑制、并发速率限制、响应缓存 |
| 中介 | 分配消息、提取变量、JSON/XML转换、XSL转换 |
| 扩展 | JavaScript、Python脚本、服务调用 |
| 威胁防护 | JSON/XML威胁防护、正则表达式防护 |
| 日志 | 消息日志、统计收集器 |
Common Policy Attributes
常见策略属性
xml
<PolicyName enabled="true" continueOnError="false" async="false">
<!-- Policy configuration -->
</PolicyName>xml
<PolicyName enabled="true" continueOnError="false" async="false">
<!-- Policy configuration -->
</PolicyName>Message Quality of Service
消息服务质量
Exactly-Once Processing
仅一次处理
Use when duplicates must be prevented:
- JMS Queues - Transactional message storage
- Idempotent Process Call - Duplicate detection via ID mapping
- Data Store - Persistent message tracking
当必须防止重复时使用:
- JMS队列 - 事务性消息存储
- 幂等流程调用 - 通过ID映射检测重复
- 数据存储 - 持久化消息追踪
Idempotent Pattern
幂等模式
Sender → [ID Mapping] → Check Duplicate → Process → [ID Mapping Complete]
↓ (duplicate)
Return Cached Response发送方 → [ID映射] → 检查重复 → 处理 → [ID映射完成]
↓ (重复)
返回缓存响应Edge Integration Cell
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
- Kubernetes集群(EKS、AKS、GKE、OpenShift、RKE2)
- 最低配置:4个工作节点,每个节点4 vCPU、16GB内存
- 存储:100GB+持久化卷
- 网络:Ingress控制器、DNS配置
Workflow
工作流程
- Activate Edge Integration Cell in Integration Suite
- Prepare Kubernetes cluster (platform-specific)
- Deploy Edge Lifecycle Management Bridge
- Deploy Edge Integration Cell solution
- Configure keystore synchronization
- Deploy integration content
- 在Integration Suite中激活Edge Integration Cell
- 准备Kubernetes集群(平台特定配置)
- 部署Edge生命周期管理桥接器
- 部署Edge Integration Cell解决方案
- 配置密钥库同步
- 部署集成内容
Troubleshooting
故障排查
Common Issues
常见问题
| Issue | Resolution |
|---|---|
| Adapter connection failed | Check credentials, firewall, Cloud Connector |
| Message mapping error | Validate source/target structures, check XPath |
| Timeout | Increase adapter timeout, optimize mapping |
| Memory issues | Stream large payloads, reduce logging |
| Duplicate messages | Implement idempotent processing |
| Keystore sync failed | Verify certificate validity, check permissions |
| 问题 | 解决方案 |
|---|---|
| 适配器连接失败 | 检查凭证、防火墙、Cloud Connector |
| 消息映射错误 | 验证源/目标结构,检查XPath |
| 超时 | 增加适配器超时时间,优化映射 |
| 内存问题 | 流式处理大负载,减少日志输出 |
| 重复消息 | 实现幂等处理 |
| 密钥库同步失败 | 验证证书有效性,检查权限 |
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, QueuesIntegration Suite → 监控 → 集成与API
├── 消息处理 → 所有集成流
├── 管理集成内容 → 已部署工件
├── 管理安全 → 密钥库、凭证
└── 管理存储 → 数据存储、变量、队列Limits Reference
限制参考
| Resource | Limit |
|---|---|
| Integration flows per tenant | Varies by plan |
| JMS queues | 30 per tenant (standard) |
| Data stores | 100MB total storage |
| Message processing log retention | 30 days |
| Attachment size | 40MB |
| API proxies (APIM) | Based on service plan |
| Business data graphs | 500/account, 50/subaccount |
| 资源 | 限制 |
|---|---|
| 租户内集成流数量 | 随套餐不同而变化 |
| JMS队列 | 每个租户30个(标准版) |
| 数据存储 | 总存储100MB |
| 消息处理日志保留时长 | 30天 |
| 附件大小 | 40MB |
| API代理(APIM) | 基于服务套餐 |
| 业务数据图谱 | 每个账户500个,每个子账户50个 |
Bundled Resources
捆绑资源
Reference Documentation
参考文档
Detailed guides available in directory:
references/Core Development:
- - iFlow development, steps, patterns, best practices
cloud-integration.md - - Importable iFlow package structure and HTTPS-to-SFTP generation rules
iflow-package-authoring.md - - All 80+ adapter configurations (HTTP, SFTP, OData, RFC, etc.)
adapters.md - - Groovy/JavaScript patterns, APIs, and templates
scripting.md - - API proxy development, 34 policies, Developer Hub
api-management.md - - Authentication, keystores, certificates, credentials
security.md
Capabilities:
- - Hybrid Kubernetes deployment guide
edge-integration-cell.md - - Topics, queues, brokers, webhooks, EDA patterns
event-mesh.md - - B2B integration, MIGs, MAGs, partner management
integration-advisor-tpm.md - - Business Data Graph, OData provisioning
graph-odata.md - - Catena-X, EDC, sovereign data exchange
data-space-integration.md - - PO migration, ISA-M, technology mapping
migration-assessment.md
Operations:
- - Message monitoring, stores, connectivity tests
operations-monitoring.md - - TMS, CTS+, MTAR, manual export/import
content-transport.md - - Error resolution, diagnostics, HTTP error catalog
troubleshooting.md
references/核心开发:
- - iFlow开发、步骤、模式、最佳实践
cloud-integration.md - - 可导入iFlow包结构及HTTPS转SFTP生成规则
iflow-package-authoring.md - - 80+种适配器配置(HTTP、SFTP、OData、RFC等)
adapters.md - - Groovy/JavaScript模式、API及模板
scripting.md - - API代理开发、34种策略、Developer Hub
api-management.md - - 认证、密钥库、证书、凭证
security.md
能力相关:
- - 混合Kubernetes部署指南
edge-integration-cell.md - - 主题、队列、代理、Webhook、EDA模式
event-mesh.md - - B2B集成、MIGs、MAGs、合作伙伴管理
integration-advisor-tpm.md - - 业务数据图谱、OData配置
graph-odata.md - - Catena-X、EDC、主权数据交换
data-space-integration.md - - PO迁移、ISA-M、技术映射
migration-assessment.md
运维相关:
- - 消息监控、存储、连接测试
operations-monitoring.md - - TMS、CTS+、MTAR、手动导出/导入
content-transport.md - - 错误解决、诊断、HTTP错误目录
troubleshooting.md
Templates
模板
Ready-to-use templates in directory:
templates/- - Reviewable unzipped importable iFlow template for HTTPS sender to SFTP receiver scenarios
https-to-sftp-iflow-package/ - - Common script patterns
groovy-script-template.groovy - - Policy configuration template
api-policy-template.xml
templates/- - 可审查的未压缩可导入iFlow模板,适用于HTTPS发送方转SFTP接收方场景
https-to-sftp-iflow-package/ - - 常见脚本模式
groovy-script-template.groovy - - 策略配置模板
api-policy-template.xml
Documentation Links
文档链接
Official Sources
官方来源
- GitHub Repository: https://github.com/SAP-docs/sap-btp-integration-suite
- SAP Help Portal: https://help.sap.com/docs/integration-suite
- SAP Community: https://community.sap.com/topics/cloud-platform-integration-suite
- SAP Business Accelerator Hub: https://api.sap.com/
- GitHub仓库: https://github.com/SAP-docs/sap-btp-integration-suite
- SAP帮助门户: https://help.sap.com/docs/integration-suite
- SAP社区: https://community.sap.com/topics/cloud-platform-integration-suite
- SAP Business Accelerator Hub: https://api.sap.com/
Capability-Specific
能力专属链接
- Cloud Integration: https://help.sap.com/docs/cloud-integration
- API Management: https://help.sap.com/docs/sap-api-management
- Event Mesh: https://help.sap.com/docs/event-mesh
- Integration Advisor: https://help.sap.com/docs/integration-advisor
- Cloud Integration: https://help.sap.com/docs/cloud-integration
- API Management: https://help.sap.com/docs/sap-api-management
- Event Mesh: https://help.sap.com/docs/event-mesh
- Integration Advisor: https://help.sap.com/docs/integration-advisor
Release Notes
发布说明
- What's New: Check in documentation
what-s-new-for-sap-integration-suite-79cd682.md - Patch Releases: Check
patch-release-notes-for-sap-integration-suite-58595b5.md
- 新功能: 查看文档中的
what-s-new-for-sap-integration-suite-79cd682.md - 补丁发布: 查看文档中的
patch-release-notes-for-sap-integration-suite-58595b5.md