sap-btp-integration-suite

# SAP BTP Integration Suite Development

## Table of Contents
- [Quick Reference](#quick-reference)
- [Capability Overview](#capability-overview)
- [Cloud Integration Development](#cloud-integration-development)
- [API Management Development](#api-management-development)
- [Event Mesh](#event-mesh)
- [Edge Integration Cell](#edge-integration-cell)
- [Integration Advisor](#integration-advisor)
- [Trading Partner Management](#trading-partner-management)
- [Migration Assessment](#migration-assessment)
- [Bundled Resources](#bundled-resources)

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

### 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:

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

| 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

```xml
<PolicyName enabled="true"