SAP Cloud Foundry TRIAL has limitation connecting with a System on-premise NO-SAP

[jalf1991]

Hi everyone,

Principal question:

My question is simple: SAP Cloud Foundry TRIAL ACCOUNT has limitation connecting with a System on-premise NO-SAP like a DB (TCP)?

Other Question:

In this moment I'm triying to deploy a Java App CF runtime binding with Service: Connectivity, XSUAA and destination. I have implemented TCP for Cloud Application (Socket5 implementation) official: Using the TCP Protocol for Cloud Applications - SAP Help Portal. All OK until this point. The app needs to connect to DB SQL Server exposed in SCC ( both servers are installed in my personal PC). The socket5 class implementation response OK. Finally, when the Java app try to connect to DB SQL Sever with the socket hots and port (Simple SQL Connection) the next exception is generated:

OUT com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 127.0.0.1, port 1433 has failed. Error: "Connection refused (Connection refused). Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.

Note:

-My firewall is turn OFF (Internet e Intranet) in my PC for this test. TCP is nno blocked.

- My SQL Server has configuración TCP/IP Enable and port 1433 to Internet PUBLIC.

I need help, I think that I have some kind of limitation when I want to try to connect from CF App to on-premise system no-SAP like my DB SQL Server.

Thanks for your help

[jalf1991]

Group Security account - CF Trial Account.

i can see space en DEV status. c3d1947136cd4c748a7aa794001af496 is about it you comment in security?

[fconsonni]

Hi Alfredo,

I have the same problem as you in connecting BTP with a SQL Server DB exposed in SCC. Were you able to solve the issue?

Thanks

[wiking]

I think I got similar issue, under trial account using SCC TCP tunnel and Connectivity Socks proxy, when I tried to acess my on-premise PostgreSQL DB (See https://answers.sap.com/questions/13560664/error-getaddrinfo-enotfound-cannot-proxying-to-bac.html ), while I got error "getaddrinfo ENOTFOUND". ANd how did you solve such issue?

[WouterLemaire]

You can connect any system to your cloud connector, also non sap.

The error you get is because of security reasons. It’s not allowed to access on premise destinations from outside the sap cloud platform. You can use BAS to solve this...

[jalf1991]

Hi c3d1947136cd4c748a7aa794001af496

Thanks for you comment.

How could I do this with BAS ?. I'm working the Java app in VS code and deploy in CF Trial Account.

From SCC the SQL Sever (127.0.0.1:1433) is reachable without problem.

My SAP CF Trial Account is config with connection OK in SCC too.

There is some thing to do about my security in SCC or CF?

Thanks

[WouterLemaire]

I think it’s security inside scp. Nothing you can change.

You should be able to import or clone your project in BAS and just run it like in vscode. The difference is that it directly runs in scp.

[jalf1991]

Interesting point!. I will try to do that. Thanks c3d1947136cd4c748a7aa794001af496 , I appreciate a lot your time. I will comment you my results!.

[jalf1991]

Hi c3d1947136cd4c748a7aa794001af496

Test results from BAS:

I tried to run my project from BAS but I'm getting: Time out when the Java App try to Connect with SOCKET5 Server CF. Look: SEE IMAGE ATTACHED

2021-02-16-17h01-23.png

How you see from BAS the app never connect with SOCKET5 Proxy CF server. Do you know the way to do it or any idea ?.

OR if I want to test my java app (CF) to connect to SQL Sever DB onpremise then, I need looking for a pay account SAP CF environment?

Thanks for your help.

[WouterLemaire]

Hmm not sure, I would have expected that this would work without timeout...

[jalf1991]

I guess that is because the socket5 CF Server is just avaliable from CF Application runtime. It's neccesary to deploy the app in CF for testing the connection to SQL Sever exposed in SCC.

If you try to run the app from BAS environment the app never reaches the Socket Server. Timeout is normal to happen...