BTP & Integrationintermediate

BTP Transport Management Part 2: Configuring a Multi-Node Landscape

Key takeaway

Configure cTMS end to end: destinations that let each node deploy into its target subaccount, transport nodes with content types, routes, upload/export via CI/CD or the content agent, import settings, and roles.

Explanation

📌 KEY POINTS
✅ Each target node uses a destination pointing to the deploy endpoint of its subaccount/space.
✅ Nodes define allowed content types (e.g. multitarget application, integration content).
✅ Routes chain nodes; importing forwards to the next node's queue.
✅ Content arrives via upload, CI/CD pipelines, or the content agent from tools like Integration Suite.
⚠️ A destination pointing to the wrong space deploys test content into production.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 explained cTMS. Now configuration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. DESTINATIONS

Deploy destination per node (target subaccount/space).

━━━━━━━━━━━━━━━━━━━━
▶ 2. NODES

Name, content type, destination.

━━━━━━━━━━━━━━━━━━━━
▶ 3. ROUTES

DEV_EXPORT → TEST → PROD.

━━━━━━━━━━━━━━━━━━━━
▶ 4. EXPORT SOURCES

CI/CD service, content agent.

━━━━━━━━━━━━━━━━━━━━
▶ 5. ROLES & TESTS

Admin/operator; end-to-end transport test.

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

Create deploy destinations for TEST and PROD.
Create nodes and a route.
Export from CI/CD and import.

✅ CHECKPOINT: MTA deployed to TEST then PROD via queues.

Code example

ABAP Code

===== NODE SETUP =====Destination TMS_DEPLOY_TEST → deploy service endpoint of test subaccount/space (technical user or OAuth)Node TEST: content type Multi-Target Application, destination TMS_DEPLOY_TESTNode PROD: content type MTA, destination TMS_DEPLOY_PRODRoute: TEST → PROD ===== EXPORT =====CI/CD job "upload to cTMS" (node DEV/TEST) | Integration Suite → content agent → cTMS

Real project scenario

A retail company built BTP apps and configured cTMS but pointed the PROD node destination at the test space. The first 'production' import landed in test. A naming convention and end-to-end test before go-live caught similar issues.

Common mistakes

Wrong destination targets.
Unsecured service keys.
Missing content types.
No end-to-end test.
Ambiguous names.

Best practices

Clear destination names.
Secure credentials.
Correct content types.
Test transports.
Documented landscape.

Interview angle

Questions: "How do you configure a cTMS node?", "How does content reach cTMS?", "What does a route do?"
Strong answer: destinations, nodes, routes, export sources, roles/tests.

Practice this lesson

Quick check

1. What tells a cTMS transport node where to deploy content?

2. A team proposes letting developers import directly into the PROD node. Why is this a problem?

3. Interviewers commonly ask candidates to explain how BTP transport differs from classical ABAP CTS, and to justify why a governed transport mechanism is needed even in a cloud-native landscape. In the Transport Management context, which answer shows the strongest practical judgment?

Interview questions

1. Configure a DEV → TEST → PROD transport landscape with cTMS for MTAs and integration content.

Answer it in your own words first, then compare.

2. How would you apply Transport Management in a real SAP project? Walk through the design or implementation approach.