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 |
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 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
| 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 |
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
| 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 |
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:
- JMS Queues - Transactional message storage
- Idempotent Process Call - Duplicate detection via ID mapping
- 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
- 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
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 |
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
| 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 |
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
1---
2name: sap-btp-integration-suite
3description: "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."
4
5
6license: GPL-3.0
7metadata:
8 source: https://skillmd.com/skills/secondsky/sap-btp-integration-suite
9 maintainer: "Eduard Jiglau"
10 maintainer_email: "hello@sap-ai-skills.com"
11 website: "https://sap-ai-skills.com"
12 version: "2.4.1"
13 last_verified: 2025-11-27
14 documentation_source: "https://github.com/SAP-docs/sap-btp-integration-suite"
15 sap_help_portal: "https://help.sap.com/docs/integration-suite"
16 status: production
17 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]
18
19allowed-tools:
20 - Read
21 - Bash
22 - Glob
23 - Grep
24 - WebFetch
25 - WebSearch
26---
27
28# SAP BTP Integration Suite Development
29
30## Related Skills
31
32- **sap-btp-cloud-platform**: Use for BTP subaccount, subscription, entitlement, and role setup
33- **sap-btp-connectivity**: Use for destinations, Cloud Connector, and hybrid connectivity dependencies
34- **sap-api-style**: Use for API proxy documentation, OpenAPI quality, and API lifecycle standards
35- **sap-btp-cloud-transport-management**: Use for transporting integration artifacts across landscapes
36
37## When to Use This Skill
38
39Use 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.
40
41## Table of Contents
42- [Quick Reference](#quick-reference)
43- [Capability Overview](#capability-overview)
44- [Cloud Integration Development](#cloud-integration-development)
45- [API Management Development](#api-management-development)
46- [Event Mesh](#event-mesh)
47- [Edge Integration Cell](#edge-integration-cell)
48- [Integration Advisor](#integration-advisor)
49- [Trading Partner Management](#trading-partner-management)
50- [Migration Assessment](#migration-assessment)
51- [Bundled Resources](#bundled-resources)
52
53## Quick Reference
54
55| Capability | Purpose | Key Artifact |
56|------------|---------|--------------|
57| Cloud Integration | A2A/B2B/B2G integration | Integration Flow (iFlow) |
58| API Management | API lifecycle & governance | API Proxy |
59| Event Mesh | Event-driven architecture | Topics & Queues |
60| Edge Integration Cell | Hybrid deployment | Kubernetes runtime |
61| Integration Advisor | B2B mapping automation | MIG/MAG |
62| Trading Partner Management | Partner onboarding | Agreements |
63| Graph | Unified data API | Business Data Graph |
64| Integration Assessment | Technology selection | ISA-M |
65| Migration Assessment | PO migration planning | Extraction & Analysis |
66
67---
68
69## Capability Overview
70
71### Cloud Integration
72Build 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.
73
74**Core Components**:
75- Integration Flows (iFlows) - Visual message processing pipelines
76- Adapters - Protocol/application connectors (SFTP, HTTP, OData, RFC, AMQP, Kafka, etc.)
77- Message Mapping - Graphical/XSLT/Groovy transformations
78- Data Stores & Variables - Persistence for stateful processing
79- Security Material - Keystores, credentials, PGP keys
80
81### API Management
82Complete API lifecycle management with security, traffic control, and developer engagement.
83
84**Core Components**:
85- API Proxies - Facade layer for backend services
86- Policies (34 types) - Security, traffic, mediation rules
87- Developer Hub - API portal for developers
88- Products - API bundles with access control
89- Analytics - Usage metrics and insights
90
91### Event Mesh
92Publish and consume business events across your enterprise ecosystem for event-driven architectures.
93
94### Edge Integration Cell
95Hybrid runtime for processing data within private landscapes while designing in the cloud. Deploy on Kubernetes (EKS, AKS, GKE, OpenShift, RKE2).
96
97### Integration Advisor
98AI-powered B2B content development supporting UN/EDIFACT, SAP IDoc, ASC X12. Creates Message Implementation Guidelines (MIGs) and Mapping Guidelines (MAGs).
99
100### Trading Partner Management
101Streamline B2B relationships with partner profiles, agreement templates, and automated runtime artifact generation. Supports AS2, SFTP, FTP protocols.
102
103---
104
105## Cloud Integration Development
106
107### Importable iFlow Generation
108
109When 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.
110
111For HTTPS-to-SFTP scenarios, start from `templates/https-to-sftp-iflow-package/` and preserve its directory layout:
112
113```
114.project
115META-INF/MANIFEST.MF
116metainfo.prop
117src/main/resources/parameters.prop
118src/main/resources/parameters.propdef
119src/main/resources/scenarioflows/integrationflow/HTTPS_to_SFTP_Template.iflw
120```
121
122Customize only the externalized placeholders unless the user asks for a different design:
123- `{{HTTPS_ENDPOINT_PATH}}`
124- `{{SFTP_HOST}}`
125- `{{SFTP_PORT}}`
126- `{{SFTP_DIRECTORY}}`
127- `{{SFTP_FILENAME}}`
128- `{{SFTP_CREDENTIAL_ALIAS}}`
129
130Keep 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.
131
132### Integration Flow Structure
133
134```
135Sender → [Adapter] → Integration Process → [Adapter] → Receiver
136 ↓
137 ┌────────────┴────────────┐
138 │ Message Processing │
139 │ - Content Modifier │
140 │ - Router/Filter │
141 │ - Mapping │
142 │ - Splitter/Aggregator │
143 │ - Script │
144 │ - External Call │
145 └─────────────────────────┘
146```
147
148### Common Flow Steps
149
150| Category | Steps |
151|----------|-------|
152| Routing | Router, Filter, Multicast, Recipient List |
153| Transformation | Content Modifier, Mapping, Converter, Script |
154| Splitting | General Splitter, Iterating Splitter, EDI Splitter |
155| Persistence | Data Store, Write Variable, JMS Send |
156| External | Request Reply, Send, Poll Enrich, Content Enricher |
157| Security | Encryptor, Decryptor, Signer, Verifier |
158| Error Handling | Exception Subprocess, Escalation Event |
159
160### Adapter Categories
161
162**Protocol Adapters**: HTTP, HTTPS, SFTP, FTP, AMQP, JMS, Kafka, AS2, AS4, SOAP, OData
163**Application Adapters**: SuccessFactors, Ariba, Salesforce, ServiceNow, Workday
164**Database Adapters**: JDBC (Oracle, SQL Server, PostgreSQL, HANA, DB2)
165**Cloud Adapters**: AWS (S3, SQS, SNS), Azure (Service Bus, Storage), Google Cloud
166
167### Scripting Guidelines
168
169**Prefer standard steps over scripts**. When scripting is necessary:
170
171```groovy
172// Access message body
173def body = message.getBody(String.class)
174
175// Access headers
176def header = message.getHeader("HeaderName", String.class)
177
178// Access properties
179def prop = message.getProperty("PropertyName")
180
181// Modify body
182message.setBody(newBody)
183
184// Add header
185message.setHeader("NewHeader", "value")
186
187// Logging (use SLF4J)
188def log = org.slf4j.LoggerFactory.getLogger("script")
189log.info("Processing message")
190```
191
192**Best Practices**:
193- Use `XmlSlurper.parse(Object)` instead of `parseText(String)` for large payloads
194- Use `StringBuilder` for string concatenation
195- Never use `TimeZone.setDefault()` (VM-wide impact)
196- Never write credentials to headers (tracing exposes them)
197
198---
199
200## API Management Development
201
202### API Proxy Structure
203
204```
205Client → Proxy Endpoint → [Policies] → Target Endpoint → Backend
206 ↓ ↓
207 PreFlow PreFlow
208 Conditional Flows Conditional Flows
209 PostFlow PostFlow
210 ↓ ↓
211 Fault Rules Fault Rules
212```
213
214### Policy Categories
215
216| Category | Policies |
217|----------|----------|
218| Security | OAuth 2.0, Verify API Key, Basic Auth, SAML, Access Control |
219| Traffic | Quota, Spike Arrest, Concurrent Rate Limit, Response Cache |
220| Mediation | Assign Message, Extract Variables, JSON/XML Transform, XSL Transform |
221| Extension | JavaScript, Python Script, Service Callout |
222| Threat Protection | JSON/XML Threat Protection, Regular Expression Protection |
223| Logging | Message Logging, Statistics Collector |
224
225### Common Policy Attributes
226
227```xml
228<PolicyName enabled="true" continueOnError="false" async="false">
229 <!-- Policy configuration -->
230</PolicyName>
231```
232
233---
234
235## Message Quality of Service
236
237### Exactly-Once Processing
238
239Use when duplicates must be prevented:
240
2411. **JMS Queues** - Transactional message storage
2422. **Idempotent Process Call** - Duplicate detection via ID mapping
2433. **Data Store** - Persistent message tracking
244
245### Idempotent Pattern
246
247```
248Sender → [ID Mapping] → Check Duplicate → Process → [ID Mapping Complete]
249 ↓ (duplicate)
250 Return Cached Response
251```
252
253---
254
255## Edge Integration Cell
256
257### Deployment Requirements
258
259- Kubernetes cluster (EKS, AKS, GKE, OpenShift, RKE2)
260- Minimum: 4 worker nodes, 4 vCPU, 16GB RAM each
261- Storage: 100GB+ persistent volume
262- Network: Ingress controller, DNS configuration
263
264### Workflow
265
2661. Activate Edge Integration Cell in Integration Suite
2672. Prepare Kubernetes cluster (platform-specific)
2683. Deploy Edge Lifecycle Management Bridge
2694. Deploy Edge Integration Cell solution
2705. Configure keystore synchronization
2716. Deploy integration content
272
273---
274
275## Troubleshooting
276
277### Common Issues
278
279| Issue | Resolution |
280|-------|------------|
281| Adapter connection failed | Check credentials, firewall, Cloud Connector |
282| Message mapping error | Validate source/target structures, check XPath |
283| Timeout | Increase adapter timeout, optimize mapping |
284| Memory issues | Stream large payloads, reduce logging |
285| Duplicate messages | Implement idempotent processing |
286| Keystore sync failed | Verify certificate validity, check permissions |
287
288### Monitoring Hierarchy
289
290```
291Integration Suite → Monitor → Integrations and APIs
292 ├── Message Processing → All Integration Flows
293 ├── Manage Integration Content → Deployed Artifacts
294 ├── Manage Security → Keystores, Credentials
295 └── Manage Stores → Data Stores, Variables, Queues
296```
297
298---
299
300## Limits Reference
301
302| Resource | Limit |
303|----------|-------|
304| Integration flows per tenant | Varies by plan |
305| JMS queues | 30 per tenant (standard) |
306| Data stores | 100MB total storage |
307| Message processing log retention | 30 days |
308| Attachment size | 40MB |
309| API proxies (APIM) | Based on service plan |
310| Business data graphs | 500/account, 50/subaccount |
311
312---
313
314## Bundled Resources
315
316### Reference Documentation
317Detailed guides available in `references/` directory:
318
319**Core Development**:
320- `cloud-integration.md` - iFlow development, steps, patterns, best practices
321- `iflow-package-authoring.md` - Importable iFlow package structure and HTTPS-to-SFTP generation rules
322- `adapters.md` - All 80+ adapter configurations (HTTP, SFTP, OData, RFC, etc.)
323- `scripting.md` - Groovy/JavaScript patterns, APIs, and templates
324- `api-management.md` - API proxy development, 34 policies, Developer Hub
325- `security.md` - Authentication, keystores, certificates, credentials
326
327**Capabilities**:
328- `edge-integration-cell.md` - Hybrid Kubernetes deployment guide
329- `event-mesh.md` - Topics, queues, brokers, webhooks, EDA patterns
330- `integration-advisor-tpm.md` - B2B integration, MIGs, MAGs, partner management
331- `graph-odata.md` - Business Data Graph, OData provisioning
332- `data-space-integration.md` - Catena-X, EDC, sovereign data exchange
333- `migration-assessment.md` - PO migration, ISA-M, technology mapping
334
335**Operations**:
336- `operations-monitoring.md` - Message monitoring, stores, connectivity tests
337- `content-transport.md` - TMS, CTS+, MTAR, manual export/import
338- `troubleshooting.md` - Error resolution, diagnostics, HTTP error catalog
339
340### Templates
341Ready-to-use templates in `templates/` directory:
342- `https-to-sftp-iflow-package/` - Reviewable unzipped importable iFlow template for HTTPS sender to SFTP receiver scenarios
343- `groovy-script-template.groovy` - Common script patterns
344- `api-policy-template.xml` - Policy configuration template
345
346---
347
348## Documentation Links
349
350### Official Sources
351- **GitHub Repository**: [https://github.com/SAP-docs/sap-btp-integration-suite](https://github.com/SAP-docs/sap-btp-integration-suite)
352- **SAP Help Portal**: [https://help.sap.com/docs/integration-suite](https://help.sap.com/docs/integration-suite)
353- **SAP Community**: [https://community.sap.com/topics/cloud-platform-integration-suite](https://community.sap.com/topics/cloud-platform-integration-suite)
354- **SAP Business Accelerator Hub**: [https://api.sap.com/](https://api.sap.com/)
355
356### Capability-Specific
357- **Cloud Integration**: [https://help.sap.com/docs/cloud-integration](https://help.sap.com/docs/cloud-integration)
358- **API Management**: [https://help.sap.com/docs/sap-api-management](https://help.sap.com/docs/sap-api-management)
359- **Event Mesh**: [https://help.sap.com/docs/event-mesh](https://help.sap.com/docs/event-mesh)
360- **Integration Advisor**: [https://help.sap.com/docs/integration-advisor](https://help.sap.com/docs/integration-advisor)
361
362### Release Notes
363- **What's New**: Check `what-s-new-for-sap-integration-suite-79cd682.md` in documentation
364- **Patch Releases**: Check `patch-release-notes-for-sap-integration-suite-58595b5.md`