High Availability for SAP Cloud Connector

The SAP Cloud Connector establishes a secure connection between SAP Cloud Platform applications and on-premises systems. It operates as a reverse invocation proxy, bridging the gap between the on-premises network and the SAP Cloud Platform.

Requirements

To implement high availability for the SAP Cloud Connector, you must have two SAP Cloud Connectors installed. After the installation of the SAP Cloud Connector, during your initial login, you will be prompted to choose between setting up a master or shadow system. Opt for 'master' for the first installed SAP Cloud Connector and 'shadow' for the second installed SAP Cloud Connector.

Prerequisites:

1. Two separate Virtual Machine

2. Microsoft Visual C++ 2013

3. JVM

4. SAP Cloud Connector Installer

Virtual Machines (AWS EC2):

Microsoft Visual C++ 2013

Download Visual C++ Redistributable Packages for Visual Studio 2013 from Official Microsoft Download CenterMicrosoft Store - Download Center

JVM

Download and place it in your VM, latter just browse the path while installing SCC

SAP Cloud Connector Installer

Now, it's time to install both Master and Shadow SCC:

Configure Master

Configure Shadow

Enable HA (High Availability) in the Master SCC

Connect Master from the Shadow

Connect BTP Subaccount from Master SCC

In the BTP level, you will see both master and shadow SCC:

Use case Scenario:

SAP Cloud Connector (SCC) is a component that connects on-premises systems to SAP Cloud Platform, allowing secure and controlled communication between cloud applications and on-premises resources. The concept of "master" and "shadow" SCC instances is used to provide high availability and failover capabilities. Here are some use case scenarios for master and shadow SAP Cloud Connector instances:

1. High Availability:

   • The master SCC instance serves as the primary connector, handling the traffic between cloud applications and on-premises systems.

   • The shadow SCC instance is a backup or standby connector that takes over in case the master SCC becomes unavailable due to hardware failures, maintenance, or other issues.

   • This setup ensures continuous availability of the connection between the cloud and on-premises systems, minimizing downtime.

2. Disaster Recovery:

   • In a disaster recovery scenario, the master SCC instance may be located in one data center or region, while the shadow SCC instance is placed in a separate data center or region.

   • If the primary data center or region experiences a disaster, the shadow SCC can be activated to maintain the connectivity between the cloud and on-premises systems.

   • This helps ensure business continuity even in the face of major disruptions.

3. Load Balancing and Scalability:

   • By distributing the load between the master and shadow SCC instances, you can achieve load balancing for incoming traffic.

   • When the load on the master SCC reaches a certain threshold, the shadow SCC can be configured to take on some of the traffic, preventing overload and ensuring optimal performance.

4. Maintenance and Updates:

   • When performing maintenance or updates on the master SCC instance, you can temporarily switch traffic to the shadow SCC to avoid service disruptions.

   • This allows you to keep the connection between your cloud applications and on-premises systems intact while performing necessary maintenance tasks.

5. Geographic Redundancy:

   • In scenarios where you have on-premises systems distributed across multiple geographical locations, you can deploy master and shadow SCC instances near those locations.

   • This helps reduce latency and ensures that cloud applications can connect to the nearest SCC instance for improved performance.

6. Failover Testing:

   • You can use the shadow SCC for failover testing and disaster recovery drills without affecting the production environment.

   • This allows you to validate your failover procedures and ensure that the shadow SCC is ready to take over when needed.

Overall, the use of master and shadow SCC instances enhances the reliability, availability, and performance of the SAP Cloud Connector, making it a crucial component for integrating on-premises systems with SAP Cloud Platform and other cloud-based applications.

Only for Testing and Learning Purposes to make it simple, you can allow all the inbound ports for both the master and shadow EC2 VM

Only for Testing and Learning Purposes and to make it simple, you can switch off the Firewall in the Windows VM