BTP & Integrationadvanced

BTP Integration Suite Part 6: Transport, Versioning and CI/CD

Key takeaway

Move integration content safely: package and artifact versioning, externalized parameters per tenant, transports via Cloud Transport Management (content agent) or MTAR, CI/CD pipelines for iFlows, and why manual fixes in production must be back-ported.

Explanation

📌 KEY POINTS
✅ Version artifacts and packages; save versions with meaningful comments before transport.
✅ Externalized parameters let the same iFlow run with tenant-specific values.
✅ Transport via content agent + Cloud Transport Management (recommended) or MTAR export/import.
✅ CI/CD pipelines can test and deploy iFlows automatically.
⚠️ Fixing iFlows directly in production without back-porting to dev creates drift that the next transport overwrites.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 5 covered capability choice. Now lifecycle.

━━━━━━━━━━━━━━━━━━━━
▶ 1. VERSIONING

Artifact versions; package versions.

━━━━━━━━━━━━━━━━━━━━
▶ 2. EXTERNALIZATION

Parameters per tenant.

━━━━━━━━━━━━━━━━━━━━
▶ 3. TRANSPORT OPTIONS

cTMS via content agent; MTAR.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CI/CD

Automated deploy/tests for integration content.

━━━━━━━━━━━━━━━━━━━━
▶ 5. HOTFIXES

Fix in dev, transport; or back-port immediately.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Version an iFlow with comment.
Transport via cTMS to test.
Configure parameters in test and deploy.

✅ CHECKPOINT: same artifact version runs in test with test values.

Code example

ABAP Code

===== TRANSPORT PATH =====DEV tenant: save version 1.3.0 ("TICKET-123 add country routing") → Transport (content agent) → cTMS node TEST → import → configure externalized params → deploy ===== HOTFIX RULE =====Prod fix? → same change in DEV immediately → version → transport → prod overwritten with identical content

Real project scenario

A production iFlow was fixed manually after an incident, but the fix wasn't applied in dev. The next regular transport overwrote it and the incident reoccurred. A back-port rule and transport-only production changes fixed the process.

Common mistakes

Manual prod fixes.
No version comments.
Missing parameter config.
MTAR by email.
No CI/CD tests.

Best practices

Transport-only prod changes.
Meaningful versions.
Configure params per tenant.
cTMS path.
Pipeline tests.

Interview angle

Questions: "How do you transport iFlows?", "What are externalized parameters?", "How do you handle hotfixes?"
Strong answer: versioning, externalization, transport options, CI/CD, hotfix discipline.

Practice this lesson

Quick check

1. What allows the same iFlow version to run with different URLs in test and production?

2. A production iFlow was fixed manually; the next transport reintroduced the bug. What prevents this?

3. Which is the recommended transport route for integration content between tenants?

Interview questions

1. A hotfix made directly in production was lost after the next transport. How do you set up integration content lifecycle?

Answer it in your own words first, then compare.

2. Describe a robust process for managing and transporting an integration flow from a development tenant to a production tenant. What are the key principles and best practices you would follow to ensure a reliable and reproducible deployment?