BTP & Integrationadvanced

BTP Build Work Zone Part 2: Architecture — Identity, Content Federation and Operations

Key takeaway

Architect Work Zone for the enterprise: identity through Identity Authentication with SSO to back ends, content federation from S/4HANA and other SAP systems (exposing roles and apps), HTML5 app repository and destinations, performance and caching, transports and operations.

Explanation

📌 KEY POINTS
✅ Users log in via Identity Authentication; SSO to back ends needs aligned identities.
✅ Content federation imports roles/apps exposed by S/4HANA and other providers — no manual rebuild.
✅ BTP apps are served from the HTML5 application repository via destinations.
✅ Transport site content and roles between environments; monitor availability and errors.
⚠️ Different user identifiers in IAS and S/4 break SSO — tiles open but back-end calls fail.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 covered editions and content. Now architecture.

━━━━━━━━━━━━━━━━━━━━
▶ 1. IDENTITY & SSO

IAS, back-end user mapping.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CONTENT FEDERATION

Content exposure in S/4; content providers.

━━━━━━━━━━━━━━━━━━━━
▶ 3. BTP APPS

HTML5 repo, managed app router, destinations.

━━━━━━━━━━━━━━━━━━━━
▶ 4. OPERATIONS

Transports, monitoring, hypercare.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PERFORMANCE

Caching, content size.

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

Configure SSO via IAS.
Expose S/4 content and add a content provider.
Assign federated roles and test.

✅ CHECKPOINT: S/4 apps open with SSO from the site.

Code example

ABAP Code

===== ARCHITECTURE =====User → IAS (corporate IdP) → Work Zone site  ├─ Federated content: S/4HANA content provider (exposed roles, apps) → SSO to S/4  └─ BTP apps: HTML5 app repository + destinations (managed app router) ===== OPERATIONS =====Content provider refresh after back-end role changes | transports of site/role content | monitoring of tile errors

Real project scenario

A global portal showed the same pages to all users because roles were not federated and everyone had one catch-all role. Enabling content federation from S/4 and assigning exposed roles gave users role-specific content.

Common mistakes

Identifier mismatch.
Manual content duplicates.
Stale federated content.
Catch-all roles.
No transports.

Best practices

Aligned identities.
Federation first.
Refresh after changes.
Role-specific access.
Transport content.

Interview angle

Questions: "What is content federation?", "How does SSO work in Work Zone?", "How are BTP apps served?"
Strong answer: identity, federation, HTML5 repo, operations, performance.

Practice this lesson

Quick check

1. S/4 roles changed but the Work Zone site still shows old tiles. What should be done?

2. During hypercare, which Work Zone check is most useful?

3. What does content federation in Work Zone provide?

Interview questions

1. A production issue is reported in SAP Build Work Zone around Build Work Zone Architecture: Identity, Content Federation, Task Center and Governance. How would you troubleshoot it systematically and avoid the common failure patterns?

Answer it in your own words first, then compare.

2. What design decisions and trade-offs matter most when implementing SAP Build Work Zone, particularly for SAP Build Work Zone Fundamentals: Standard vs Advanced Edition?