BTP Cloud Connector Part 3: High Availability, Multiple Connectors and Operations
Run Cloud Connector in production: master/shadow high availability, multiple connectors with location IDs for sites or load, monitoring (connections, performance, certificates), updates and backups, and a troubleshooting path for failed calls.
Explanation
📌 KEY POINTS
✅ High availability: a master instance with a shadow instance that takes over on failure.
✅ Multiple connectors (e.g. per data center) are distinguished by location IDs in destinations.
✅ Monitor tunnel status, back-end response times, and certificate expiry (system and CA certificates).
✅ Keep backups of configuration and update regularly (security fixes).
⚠️ Expired certificates break principal propagation and tunnels — track expiry dates.
━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured access. Now operations.
━━━━━━━━━━━━━━━━━━━━
▶ 1. HA SETUP
- Master/shadow; failover behavior.
━━━━━━━━━━━━━━━━━━━━
▶ 2. MULTIPLE CONNECTORS
- Location IDs; routing by site.
━━━━━━━━━━━━━━━━━━━━
▶ 3. MONITORING
- Tunnel, performance, alerts.
━━━━━━━━━━━━━━━━━━━━
▶ 4. MAINTENANCE
- Updates, backups, certificates.
━━━━━━━━━━━━━━━━━━━━
▶ 5. TROUBLESHOOTING
- 503 not connected, 403 resource not exposed, 401 auth.
━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP
- Set up a shadow instance.
- Test failover.
- Configure monitoring and alerts.
✅ CHECKPOINT: failover works without integration errors.
Code example
===== HA =====Master (active) ⇄ Shadow (standby) | failover on master outage | config synced from master ===== TROUBLESHOOTING =====503 / "Tunnel not connected" → SCC connected to subaccount? location ID matches?403 → resource path not exposed in Access Control401 → destination credentials / principal propagation mappingLogs: SCC audit log, trace (temporarily), BTP connectivity messagesReal project scenario
A manufacturing company's integrations stopped overnight when a Cloud Connector certificate expired. Adding certificate monitoring and an HA shadow with tested failover prevented repeat outages.
Common mistakes
- No HA.
- Untracked certificates.
- Untested failover.
- No backups.
- Traces left on permanently.
Best practices
- Master/shadow.
- Certificate calendar.
- Failover tests.
- Config backups.
- Traces only when needed.
Interview angle
Questions: "How does Cloud Connector HA work?", "When use multiple connectors?", "How do you troubleshoot 503?"
Strong answer: HA, location IDs, monitoring, maintenance, troubleshooting.
Practice this lesson
Quick check
1. In a Cloud Connector high availability setup consisting of a master and a shadow instance, how do the two instances behave during normal operation?
2. Why might an administrator configure multiple Cloud Connector instances with different Location IDs mapped to the same BTP subaccount?
3. Which prerequisite is essential on the on-premise back-end system to support principal propagation via Cloud Connector?
Interview questions
1. A production issue is reported in Cloud Connector. What would you check first, and how would you troubleshoot it systematically?
Answer it in your own words first, then compare.
2. Suppose you inherit an existing Cloud Connector solution. How would you review it before making a change?
Answer it in your own words first, then compare.
Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.