SAP Cloud Connector: Complete Guide to Download, Installation & Configuration
SAP Cloud Connector (SCC) is a lightweight, on-premise agent that creates a secure tunnel between your company’s internal network and SAP Business Technology Platform (BTP). It allows SAP BTP applications to securely access on-premise systems — such as SAP S/4HANA, SAP ECC, SAP BW, or any HTTP/RFC service — without opening inbound firewall ports.
In this guide, you will learn everything about SAP Cloud Connector: how to download it, how to install it on Windows, Linux, and Mac, how to configure it step by step with SAP BTP, and how to set up on-premise to cloud connectivity. Whether you are a beginner or an experienced SAP Basis consultant, this guide covers it all.
Table of Contents
- 1. What Is SAP Cloud Connector?
- 2. SAP Cloud Connector Download
- 3. Prerequisites and System Requirements
- 4. SAP Cloud Connector Installation on Windows
- 5. SAP Cloud Connector Installation on Linux
- 6. How to Set Up SAP Cloud Connector on Mac
- 7. SAP Cloud Connector Login — First-Time Access
- 8. How to Set Up SAP Cloud Connector with BTP (Step by Step)
- 9. SAP Cloud Connector On-Premise to Cloud Configuration
- 10. Troubleshooting Common Issues
- 11. Frequently Asked Questions
1. What Is SAP Cloud Connector?
SAP Cloud Connector (SCC) is a free, on-premise software component provided by SAP. It acts as a reverse invoke proxy — meaning the connection is always initiated from inside your corporate network towards SAP BTP. This is the key security advantage: no inbound ports need to be opened in your company’s firewall.
SAP Cloud Connector is used whenever you need to:
- Connect SAP BTP applications to on-premise SAP systems (S/4HANA, ECC, BW, Gateway)
- Enable SAP Integration Suite (Cloud Integration) to access on-premise APIs
- Use SAP Build Apps or SAP Business Application Studio with on-premise OData services
- Run SAP Analytics Cloud against on-premise data sources
- Extend on-premise SAP systems using SAP BTP extensions and side-by-side scenarios
SAP Cloud Connector provides fine-grained access control, meaning administrators can expose only specific URLs, RFC destinations, or database schemas to BTP — not the entire backend system.
2. SAP Cloud Connector Download
You can download SAP Cloud Connector for free from the SAP Development Tools page. Unlike most SAP products, you do not need an S-User or SAP Service Marketplace access to download it.
Download URL: https://tools.hana.ondemand.com/#cloud
On this page, scroll to the Cloud Connector section. You will see download options for:
| Platform | File Type | Recommended For |
| Windows (MSI Installer) | .msi | Production use — installs as a Windows Service |
| Windows (Portable) | .zip | Development and testing only |
| Linux (RPM Installer) | .zip containing .rpm | Production use on SUSE / Red Hat Linux |
| Linux (Portable) | .tar.gz | Development use or when root access is unavailable |
| macOS (Portable) | .tar.gz | Development and testing on Mac only |
Important: SAP also provides the SAP JVM (Java Virtual Machine) on the same page. If Java is not already installed on your server, download and install the SAP JVM first, as the Cloud Connector is a Java application that requires a JVM to run.
3. Prerequisites and System Requirements
Before installing SAP Cloud Connector, make sure the following requirements are met:
| Requirement | Details |
| Operating System | 64-bit: Windows Server 2012 R2/2016/2019/2022, SUSE Linux Enterprise Server 12/15, Red Hat Enterprise Linux 7/8/9, macOS (portable only) |
| Java Runtime | SAP JVM 8, SapMachine 11 or 17, or other supported JDKs |
| RAM | Minimum 2 GB (4 GB+ recommended for production) |
| Disk Space | Minimum 500 MB free |
| Network | Outbound HTTPS (port 443) to SAP BTP must be allowed |
| Firewall | No inbound ports required — SCC initiates outbound connections only |
| SAP BTP Account | A valid SAP BTP subaccount (trial or enterprise) |
| Admin Rights | Administrator/root access on the target machine (for installer version) |
| Windows Only | Microsoft Visual Studio C++ 2013 and 2019 runtime libraries (for SAP JVM) |
4. SAP Cloud Connector Installation on Windows
The Windows MSI installer is the recommended method for production environments. It registers SAP Cloud Connector as a Windows Service that starts automatically on boot.
Step-by-Step: Windows Installation
- Go to https://tools.hana.ondemand.com/#cloud
- Download the MSI Installer for Windows
- If Java is not installed, also download and install the SAP JVM from the same page
- Double-click the MSI file to launch the installer wizard
- On the prerequisites check screen, verify no errors and click Next
- Choose your installation directory (default is fine for most setups) and click Next
- Set the port number for the SCC admin UI (default: 8443) and click Next
- Select the JDK installation directory and click Next
- Click Install and wait for the process to complete
- Click Finish — the Cloud Connector service starts automatically
After installation, the Cloud Connector runs as a Windows Service. You can verify this by opening services.msc and looking for the SAP Cloud Connector service.
Portable version (for development): Extract the ZIP file to any folder, then run go.bat to start the Cloud Connector. This does not create a Windows Service.
5. SAP Cloud Connector Installation on Linux
For Linux, SAP provides an RPM-based installer that registers the Cloud Connector as a daemon service. This is recommended for production environments on SUSE Linux Enterprise Server or Red Hat Enterprise Linux.
Step-by-Step: Linux RPM Installation
- Download the Linux ZIP file from https://tools.hana.ondemand.com/#cloud
- Transfer the ZIP file to your Linux server
- Extract the ZIP to get the RPM file:
unzip sapcc-<version>-linux-x64.zip
- Install the RPM package as root:
sudo rpm -i com.sap.scc-ui-<version>.x86_64.rpm
- The Cloud Connector starts automatically as a daemon. Verify it is running:
systemctl status scc_daemon
- Access the admin UI at https://<hostname>:8443
Linux Daemon Commands
| Command | Description |
| systemctl start scc_daemon | Start the Cloud Connector |
| systemctl stop scc_daemon | Stop the Cloud Connector |
| systemctl restart scc_daemon | Restart the Cloud Connector |
| systemctl status scc_daemon | Check if the Cloud Connector is running |
| service scc_daemon start|stop|restart | Alternative for System V init distributions |
Portable version (for development): Extract the tar.gz archive and run ./go.sh to start. Make sure the JAVA_HOME environment variable is set to your Java installation directory.
6. How to Set Up SAP Cloud Connector on Mac
On macOS, only the portable version of the SAP Cloud Connector is available. This means it is intended for development and testing purposes only — not for production use.
Step-by-Step: Mac Installation
- Download the macOS tar.gz archive from https://tools.hana.ondemand.com/#cloud
- Make sure Java (JDK 8 or 11) is installed on your Mac. You can verify with:
java -version
- Extract the archive:
tar -xzof sapcc-<version>-macosx-x64.tar.gz
- Navigate to the extracted folder and start the Cloud Connector:
cd scc
./go.sh
- Open your browser and go to: https://localhost:8443
- Login with default credentials (see next section) and proceed with configuration
Note: The Mac portable version does not run as a background daemon. It stops when you close the terminal. The portable version also does not support automatic upgrades — you must manually download and replace the files for each new version.
7. SAP Cloud Connector Login — First-Time Access
After installation on any operating system, you access the SAP Cloud Connector through a web-based admin UI in your browser.
Login URL https://localhost:8443
If you are accessing the Cloud Connector from another machine on the network, replace localhost with the hostname or IP address of the machine where SCC is installed.
Default Login Credentials
| Field | Value |
| User Name | Administrator (case-sensitive) |
| Password | manage |
Important: On first login, the system will immediately ask you to change the default password before you can proceed. SAP does not enforce password strength rules, but you should choose a strong password for production environments.
After changing the password, you will also be prompted to choose the Installation Type:
- Master — Choose this for a standalone installation or the primary instance in a high-availability setup
- Shadow — Choose this for the secondary (standby) instance in a high-availability setup
For most setups, select Master and click Save.
8. How to Set Up SAP Cloud Connector with BTP (Step by Step)
After installation and first login, the next step is to connect your SAP Cloud Connector to your SAP BTP subaccount. This creates the secure tunnel between your on-premise network and SAP BTP.
Step-by-Step: Connect SCC to SAP BTP
- In the SCC admin UI, you will see the Define Subaccount screen after first login
- Enter the following details from your SAP BTP Cockpit:
| Field | Where to Find It |
| Region | SAP BTP Cockpit → Subaccount Overview → look for the region (e.g., Europe (Frankfurt), US East) |
| Subaccount ID | SAP BTP Cockpit → Subaccount Overview → Subaccount ID (a GUID) |
| Display Name | Any friendly name you choose (e.g., ‘Dev Subaccount’) |
| Subaccount User | Your SAP BTP email/username with admin access |
| Password | Your SAP BTP account password |
| Location ID | Optional — leave empty for single SCC setups; use it when multiple SCCs connect to the same subaccount |
- Click Save
- If the connection is successful, you will see a green “Connected” status in the SCC dashboard
- Verify in SAP BTP Cockpit: go to Connectivity → Cloud Connectors — your SCC instance should appear as connected
Tip: If you have a proxy server in your corporate network, configure the HTTPS proxy in the Cloud Connector settings before connecting to BTP. Go to the Cloud Connector admin UI menu and look for the proxy configuration option.
9. SAP Cloud Connector On-Premise to Cloud Configuration
Once the SCC is connected to your BTP subaccount, the next step is to configure which on-premise systems BTP can access. This is done through the Cloud to On-Premise access control settings.
Step-by-Step: Add System Mapping
- In the SCC admin UI, click Cloud to On-Premise in the left menu
- Under Access Control, click the + (Add) button to add a new system mapping
- Select the Backend Type:
| Backend Type | When to Use |
| ABAP System | For SAP ECC, S/4HANA, SAP Gateway, or any ABAP-based system |
| SAP HANA | For direct SAP HANA database connections |
| Non-SAP System | For third-party or custom HTTP services |
| RFC | For Remote Function Call connections to ABAP systems |
- Select the Protocol (HTTP or HTTPS) and click Next
- Enter the Internal Host and Internal Port of your on-premise system (the actual hostname/IP and port)
- Enter the Virtual Host and Virtual Port — these are the names that BTP applications will use to reach the system. You can choose any values you like (e.g., virtual host: mys4hana, port: 443)
- Set Principal Type to None (for most scenarios) and click Next
- Select Use Virtual Host for Host in Request Header and click Next
- Add a description and click Finish
Add Accessible Resources
After creating the system mapping, you must define which URL paths or RFC destinations BTP is allowed to access:
- Select the newly created system mapping
- In the Resources section below, click the + (Add) button
- Enter the URL Path (e.g., /sap/ to expose all SAP services)
- Select Path and All Sub-Paths for the access policy
- Click Save
The on-premise system is now accessible from SAP BTP through the virtual host and port you defined. To complete the setup, create a Destination in SAP BTP Cockpit:
- In SAP BTP Cockpit, go to Connectivity → Destinations
- Click New Destination
- Enter the virtual host and port from the SCC mapping as the destination URL
- Set the proxy type to OnPremise
- Configure authentication and save
Your SAP BTP applications can now use this destination to access the on-premise system securely through the Cloud Connector.
10. Troubleshooting Common Issues
| Issue | Solution |
| Cannot access https://localhost:8443 | Make sure the SCC service is running. On Windows: check services.msc. On Linux: run systemctl status scc_daemon |
| Connection to BTP subaccount failed | Verify that outbound HTTPS (port 443) is allowed in your firewall. Check if a proxy needs to be configured in SCC settings |
| “Connected” status not showing in BTP Cockpit | Double-check the Subaccount ID and Region. The Subaccount ID is case-sensitive |
| Login page shows error after password change | Clear your browser cache or try an incognito window |
| Port 8443 is already in use | Change the SCC port during installation or edit the config.ini file in the installation directory |
| SCC not starting on Linux | Verify JAVA_HOME is set correctly. Run: echo $JAVA_HOME and ensure it points to a valid JDK |
| System mapping shows “Unreachable” | The internal host/port of the on-premise system is incorrect or the system is down. Check network connectivity from the SCC server |
| Mac: ./go.sh permission denied | Run: chmod +x go.sh then try again |
| Forgot admin password | On Linux: run config.sh –reset-admin-password in the SCC installation directory. On Windows: reinstall SCC or edit the configuration |
11. Frequently Asked Questions
What is SAP Cloud Connector used for?
SAP Cloud Connector is used to create a secure connection between your on-premise SAP systems (S/4HANA, ECC, BW, Gateway) and SAP Business Technology Platform (BTP). It enables BTP applications like SAP Integration Suite, SAP Build Apps, and SAP Analytics Cloud to access on-premise data without opening inbound firewall ports.
Where can I download SAP Cloud Connector?
You can download SAP Cloud Connector for free from the SAP Development Tools page at https://tools.hana.ondemand.com/#cloud. No S-User or SAP Service Marketplace access is required. Download options are available for Windows (MSI and portable), Linux (RPM and portable), and macOS (portable only).
How do I install SAP Cloud Connector on Windows?
Download the MSI installer from tools.hana.ondemand.com, double-click the MSI file, follow the installation wizard (set port, choose JDK directory), and click Install. The SCC registers as a Windows Service and starts automatically. Access the admin UI at https://localhost:8443.
How do I install SAP Cloud Connector on Linux?
Download the Linux ZIP file, extract it to get the RPM file, then install using: sudo rpm -i com.sap.scc-ui-<version>.rpm. The SCC starts as a daemon service automatically. Use systemctl status scc_daemon to check it is running.
Can I install SAP Cloud Connector on Mac?
Yes, but only the portable version is available for macOS. It is intended for development and testing only. Download the macOS tar.gz file, extract it, and run ./go.sh to start the Cloud Connector.
What are the default login credentials for SAP Cloud Connector?
The default username is Administrator (case-sensitive) and the default password is manage. You will be forced to change the password on first login.
How do I connect SAP Cloud Connector to SAP BTP?
After logging into the SCC admin UI, enter your SAP BTP subaccount details: Region, Subaccount ID, Display Name, and your BTP credentials. Click Save. If the connection is successful, the status shows as “Connected.” Verify in BTP Cockpit under Connectivity → Cloud Connectors.
What is the default port for SAP Cloud Connector?
The default port for the SAP Cloud Connector admin UI is 8443. You can change this during installation or by editing the configuration file.
Is SAP Cloud Connector free?
Yes, SAP Cloud Connector is free to download and use. It is provided as part of the SAP BTP Connectivity service. You need a valid SAP BTP subaccount (trial accounts work for testing and development).
What is the difference between the installer and portable version?
The installer version (MSI for Windows, RPM for Linux) registers the Cloud Connector as a service/daemon that starts on boot, supports automatic upgrades, and is recommended for production. The portable version (ZIP/tar.gz) requires manual start, does not auto-restart on reboot, and is meant for development and testing only.
Does SAP Cloud Connector require inbound firewall ports?
No. SAP Cloud Connector uses a reverse invoke architecture, meaning it initiates all connections outbound from your network to SAP BTP. No inbound firewall rules need to be changed, which is a key security advantage.
Summary
SAP Cloud Connector is a critical component in any SAP hybrid landscape. It provides the secure bridge between your on-premise SAP systems and SAP BTP — without requiring complex firewall changes or VPN configurations.
Here is a quick recap of the key points covered in this guide:
- Download from https://tools.hana.ondemand.com/#cloud (free, no S-User required)
- Install on Windows using the MSI installer for production; it registers as a Windows Service
- Install on Linux using the RPM package; it runs as a daemon (scc_daemon)
- Mac is supported with the portable version only, for development and testing
- Login at https://localhost:8443 with username Administrator and password manage (change on first login)
- Connect to BTP by entering your subaccount Region, Subaccount ID, and BTP credentials
- Configure access through Cloud to On-Premise system mappings and accessible resources
- Create a Destination in BTP Cockpit using the virtual host/port from the SCC mapping
With SAP Cloud Connector properly configured, your SAP BTP applications can securely access any on-premise system — enabling hybrid scenarios, cloud extensions, and real-time integrations.