SAP Cloud SDK for JAVA: Acces On-Premise System via localhost

[TikeerGuo]

Hello,

I followed this blog post to access an OData service with the Cloud Platform SDK. I Used a custom OData Service instead of the standard Businesspartner OData service and a R3 ERP on-Premise backend system instead of S/4 HANA.

If I deploy the app to my Cloud Foundry subaccount it is working fine and my OData service is executed via Cloud Connector and destination service on my on-premise backend.

If I try to execute the same application on the local tomee server the on-premise backend system is not reached.

My destination on my subaccount looks like this:

If I pass all the information (URL,User,Password) to the local destination it is not working...

The same erroppr apperas on executing the integration tests.

What must I do to access my on-premise backlend from localhost?

Best regards,

Chris

[TikeerGuo]

Hi Chris,

I also follow this blog, in cloud connector Cloud To On-Premise, configured HTTPS protocol to s4hana op system, then configure HTTP destination in BTP and check connection works(and use this HTTP destination to do other testing such as call s4hana data from postman, it works).

But i follow the blog, after deployment to BTP, the hello world servlet can be called, but cannot call the data

. It just gives error internal server error.

And also try to run locally and also set the local destination variable to follow the blog, but face error environment variable vcap_services is not defined. Do you have any idea?

Thanks lot.

[former_member186608]

Can you kindly post the entire log output between those two points:

Begin:

[INFO] --- maven-surefire-plugin:3.0.0-M3:test (default-test) @ integration-tests --
[INFO]
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------

End:

INFO: Destroying ProtocolHandler ["http-nio-53950"]

Ensure that you do not post any confidential data here.

The point is I guess there is more promising information in the stacktrace(s).