Skip to Content
Technical Articles
Author's profile photo Nieves Navarro Ruiz

SAP Cloud Connector – How to connect an ABAP System with SAP Cloud Platform

In this post will install and configure a Cloud Connector. So we will install a small server on our computer that will serve as a security tunnel to share the resources of a connection to SAP through our platform. We will also make the necessary configuration to take advantage of those resources from the SAP WebIDE service.

There are two different uses of the SAP Cloud Connector.

On  one hand, it is the official SAP tool to expose our SAP On Premise system to the outside world (outside our DMZ). Although it is a very simple installation, it is a task carried out by experts in operations and Basis. In this scenario, developers consume services directly from their SCP accounts without ever having to enter the Cloud Connector.

On the other hand, through the SAP Cloud Connector we can expose the SAP resources to which we have access from our computer, therefore we can expose any server that we have access to with our SAP Logon as usual. This is an option widely used by developers and will be the use case that we will see in detail below.



Before installing the connector is recommendable to take a look at its prerequisites.

There we can see that it is necessary to have Java JDK version 7 / 8 for its installation. Access the download link here if you need it. The installation should not give any problem but sometimes it happens, especially if you had installed a very old version of Java or things like that.

As a precaution, once the JDK is installed it is necessary to restart the computer before continuing.

To download the SAP Cloud Connector we access the SAP Development Tool site and select the correct version for our system.

Once downloaded, run the installer and follow the default installation of the Cloud Connector.

If the installation has ended with no problem you can go directly to step 2, however it is possible that you have encountered any problem along the way because your system is not detecting the SDK directory correctly, and the path shown is not correct. This is how it should look like:

What could this be due to if we have correctly installed our JDK?

  • One of the possibilities is that we have another version of the JDK and the system has allowed us to install the new one anyway (either because they are different bits versions, or any other reason) they may be bumping into each other even if we indicate the route ourselves. We must delete it and leave only one version.If despite this, it still does not working, it may also be the case that we have a system variable pointing to the previous version, and deleting it would be enough. To check it out, look in the computer configuration → system properties → environment variables.

  • It may happen that despite this the route remains unseen, luckily we can force our system to see it. Take a look at this post to see how to do it.
  • If all of the above has not worked for you, or it was not your case, the system is probably asking us to simply run the connector installation file as an administrator by subject of permissions. You will need to do it through the computer console, since this execution option is not available directly in this case. Use the ‘msiexec -i’ command followed by the file path (it will be easier if you place the installer directly on disk C:/).

Finally, after one of these options, a sum of them or hopefully none of them, our installation must have been completed successfully.



To access the Cloud Connector UI administrator, open the browser and enter https://localhost:8443/ (unless you have indicated a different port during installation).

The browser will report an error, to continue click on ‘advanced settings’ → ‘Access localhost’ or as your browser indicates, I’m with Chrome.

Once on the page, enter with the following data:

  • User: Administrator
  • Password: manage

Upon entering you will have to change the password, and to choose  between ‘master instance’ or ‘shadow instance’ as an instance for the connector.

The first option is quite intuitive, it is the main instance. But what is a shadow instance? It is a redundant instance, that is, in the event of a failure in the main instance the redundant would take its role. We need the master instance



Upon entering, you will be asked to define a SAP Cloud Platform sub-account to which our Cloud Connector points.

If we are working with the free SCP account, the ‘region’ field will be On the other hand, it is also important to be careful with the case sensitive; In a subaccount, it is normal for the ‘p’ to be lowercase. And our password must be the same as in SAP Cloud Platform.

Once all the data is completed, save and if everything is correct, the screen will appear with the data in green indicating that the connection has been established.

We can verify the connection by entering our associated SAP Cloud Platform account → ‘Connectivity’ → ‘Cloud Connector’. Here we will see that the master instance has been created, but that no back-end system has been configured for it yet.

We return to the Cloud Connector administrator and choose the option ‘Cloud To On-Premise’ to add the new configuration.

The first option is left as it comes by default.

We establish ‘HTTPS’ as the protocol.

The ‘Internal Host’ will be the route of the host to which the connector will point, while the internal Port will normally be 44300, since it is the port indicated by default.

It is good to use a Virtual Host and a Virtual Port to not expose the real ones. Here you can choose the values you want.

Choose the general purpose certificate.

Select the ‘Use virtual Host’ option instead of real one so as not to expose them.

Confirm that the data is correct and finish.

We also have to specify the accessible resources of our connection by clicking on the ‘+’ sign.

With the following configuration we indicate the resources that we are going to expose, in our case all SAP. Another more correct option would be to expose only the SAP OData ‘/sap/opu/odata’ although we may want to expose other resources, such as if we want to use an image repository.

Now if we return to our account in SAP Cloud Platform we can see that we have already configured our back-end system.

What we call a security tunnel is already established, but we still have one step left so that our Web IDE can refer to the back-end system, create a destination in SCP

Access the platform → ‘Connectivity’ → ‘Destinations’ → ‘new destination’.

Fill in the destination data taking into account that the URL must refer to the data that we have indicated in the Cloud Connector. In our case it will be the set of the virtual host and the virtual port, since we have preferred to expose the virtual ones.

As we want to share the resources of our computer to consume them from the WebIDE, we will choose a basic authentication, using the same username and password as in the SAP Logon.

In case of you want to expose your On Premise system, the propagation of entity would be more appropiated.

Finally we have to add the properties of our destination.

HTML5.SocketReadTimeoutInSeconds 300
sap-client 100
trustAll true
WebIDEEnabled true
WebIDESystem Here you must indicate the same name that has been given to the destination.
WebIDEUsage odata_abap, dev_abap, ui5_execute_abap, bsp_execute_abap, odata_gen

Do not forget to save, and press the ‘check connection’ button to verify that everything went well.

Now we have our end-to-end connection between an ABAP system and SAP Cloud Platform in a secure way through SAP Cloud Connector. Although if you still need a litmus test that shows you that it works, you can try to create a project from a template in your Web IDE and check that in the section of ‘data connection’ the name of your destination appears.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Application Access Team
      Application Access Team

      good article

      Author's profile photo Carlos Alberto Molero Godoy
      Carlos Alberto Molero Godoy



      Author's profile photo Jose Antonio Moreno
      Jose Antonio Moreno

      Hi, is there a way to connect to a remote SAP system? Outside intranet? I'm using cloud connector but can't connect to backend system.
      The solution was to install cloud connector on the client, but can it be done remotely as well as connecting to a sap system through the SAPGUI?

      Author's profile photo Ruben Rollano Carcajona
      Ruben Rollano Carcajona

      Hi Jose Antonio,


      Yes, you can share the same links that you have in you SAPGUI Logon through your local SAP Cloud Connector in order to access the remote SAP systems from SAP Cloud Platform.

      Author's profile photo Jose Antonio Moreno
      Jose Antonio Moreno

      Hi Ruben,

      Do you have to do something in the ERP? because if I am outside the intranet the status is "Not Reachable", it may be because I connect to the client system with "SAProuter"



      Author's profile photo Ruben Rollano Carcajona
      Ruben Rollano Carcajona

      Hi Jose Antonio,


      Probably your problem is the port. Which one are you using? These are the most common ports: 443, 8443, 44300, 8000, 5200.

      You should use the port that you see when access to the Fiori Launchpad.

      As far as I know, the unique requirement in the SAP system to allow the connection through SAP Cloud Connector is to open this HTTP port.


      Author's profile photo Rishabh Dhakarwal
      Rishabh Dhakarwal

      Hi Jose Antonio,

      This might be of help for finding Internal Port number of the system


      Author's profile photo Pavan Chand Bhamidipati
      Pavan Chand Bhamidipati

      Thanks for sharing . Good explanation step by step

      Author's profile photo Rishabh Dhakarwal
      Rishabh Dhakarwal

      Hi Nieves Navarro Ruiz,

      Thank you so much for such a wonderful post.

      I faced an issue while adding ABAP system in cloud connector, just want to add one thing to the post for those who might face similar issue.

      I tried to add SD5 system in the cloud connector but it was showing 'not reachable'. This issue might be due to wrong internal port number which can be different for different systems. To find out the internal port number for a particular system, do the following:

      1. Go to the Trasaction - SICF
      2. Choose Execute (F8).
      3. Choose Goto  > Port Information.
      4. Note the host and port information for the HTTPS protocol, which is required to set up the communication between SAP Cloud Platform and the ABAP system.

      Hope it helps

      Thanks & Regards

      Rishabh Dhakarwal

      Author's profile photo Sijin Chandran
      Sijin Chandran

      Hi Nieves,


      I have a query regarding the final step i.e. creating Destination.

      Our Back-end system is SSO enabled and we don't have UserName and Password based authentication. So in this case while configuring Destination what should be the "Authentication" mode ?



      Author's profile photo Konrad Grzyb
      Konrad Grzyb

      In my case it is never like this no meter which computer I am using always the same problem after installation: STEP 2 my SCC is running but I can not access port 8443 and there is information:

      This site can’t be reached

      localhost refused to connect.


      In scc20/log there is one file only scc_service.log:
      Start():	Trying to start Service Control Dispatcher
      **** Sun Jan 10 15:04:10 2021 **** Service started
      **** Sun Jan 10 15:04:10 2021 **** LoadJVM():	Loading shared libray of Java Virtual Machine
      LoadJVM():	C:\Program Files (x86)\Java\jdk-15.0.1\bin\server\jvm.dll loaded
      AddJVMOption():	-XX:+HeapDumpOnOutOfMemoryError
      AddJVMOption():	-XX:+DisableExplicitGC
      AddJVMOption():	-Xms1024m
      AddJVMOption():	-Xmx1024m
      AddJVMOption():	-XX:MaxNewSize=512m
      AddJVMOption():	-XX:NewSize=512m
      AddJVMOption():	-XX:+UseConcMarkSweepGC
      AddJVMOption():	-XX:TargetSurvivorRatio=85
      AddJVMOption():	-XX:SurvivorRatio=6
      AddJVMOption():	-XX:MaxDirectMemorySize=2G
      AddJVMOption():	-Dosgi.requiredJavaVersion=1.6
      AddJVMOption():	-Dosgi.install.area=.
      AddJVMOption():	-DuseNaming=osgi
      AddJVMOption():	-Dorg.eclipse.equinox.simpleconfigurator.exclusiveInstallation=false
      AddJVMOption():	-Declipse.ignoreApp=true
      AddJVMOption():	-Dosgi.noShutdown=true
      AddJVMOption():	-Dosgi.framework.activeThreadType=normal
      AddJVMOption():	-Dosgi.embedded.cleanupOnSave=true
      AddJVMOption():	-Dosgi.usesLimit=30
      AddJVMOption():	-Djava.awt.headless=true
      AddJVMOption():	-Dio.netty.recycler.maxCapacity.default=256
      AddJVMOption():	-Djava.class.path=plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
      AddJVMOption():	exit
      AddJVMOption():	abort
      **** Sun Jan 10 15:04:10 2021 **** Run():	Starting cloud connector ...
      **** Sun Jan 10 15:04:10 2021 **** StartSCC():	Calling org/eclipse/equinox/launcher/Main.main()
      Run():	Cloud Connector is running.

      I can not find anywhere information how to solve this issue like it is not a common problem?

      Author's profile photo Saeed mousavi
      Saeed mousavi

      I'm using the new BTP Trial version and after I completed the Cloud Connector configuration I went back to BTP and could not see the menu option for Cloud Connectors (see image below).

      Also, after setting up a New Destination, the test connection fails.

      Author's profile photo Party Tecnico
      Party Tecnico

      Check you roles assigned

      Author's profile photo hong yai
      hong yai

      I need your help.

      I Did not find about HTML 5. SocketReadTimeoutInSeconds choice.


      And when I use trustAll, I am prompted not to add a trustAll.

      So in the end I did not add HTML 5. SocketReadTimeoutInSeconds choice and TrustAll these two attributes. Result An error message is displayed indicating the destination link.

      I didn't use HTTPS in the cloud linker because when I connected to ABAP using HTTPS, THE message "Not Reachable" was displayed, so I had to switch to HTTP.

      May I ask where I need to make corresponding modifications?

      I hope you can help me. Thank you.


      Author's profile photo Deepika B
      Deepika B

      Hi Nieves,

      I have a requirement of authenticating ABAP systems via IAS system. Is it possible for a user to log via SAP logon pad using IAS.


      Thanks ,