Communicate from SAP Public Cloud to Java Application (Jco Server) via WebSocketRFC Problem

[andrzej_rosinski]

Hello everybody,

i am having a problem while trying to call a outbound service from the SAP Public Cloud to a external JCo WebSocketRFC Server instance. 

My JCo WebSocketRFC server is running on a VM that is exposed to the internet on port 8080.

In the SAP Public Cloud i have already configured the communication system where i have just entered the "Host Name" of my VM and set the Authentification Method in the "Users for Outbound Communication" to None since i do not need the authentification for the tests.

I have also configured a communication agreement for the communication system

On the Eclipse ADT side i have a communication scenario that looks like this:

with the corresponding outbound service

Now, when i try to call the outbound service from SAP Public Cloud ABAP with the corresponding code:

like described by SAP i get the following error

Anyone has an idea why this fails? Dis anyone made a scenario like this before? - to communicate from the SAP Public Cloud to a external server program? I have only found tutorials how to communicate with on prem systems.

The JcoTrace for the server says the following (i have replaced the real IP with "hostname" in the screenshot)

obviously the handshake cannot be completed. I am trying to connect to the server withot any authentification (i have set the communication scenario to "Unauthentifiacted" and i have startet the Jco server without any p12 files - jco.server.use_tls=0).

Server props:

@MarkusTolksdorf @simon_luser Thanks for your reply, i have added the Trace from the Jco. Could the problem be the missing authorisation? 

[simon_luser]

Do you see the full failure text? Can you activate JCo trace to see if you even reach the JCo server?

[simon_luser · Accepted solution]

The problem is currently jco.server.use_tls=0, this is actually not supported from ABAP cloud clients, they will always communicate via TLS, however your current JCo server expects plain WebSocket communication now with this setting. For testing purposes you can create and setup a simple p12 file containing an own server certificate which ABAP trusts.

[andrzej_rosinski · Accepted solution]

Yes 🙂 that was the problem. So TLS is obligatory in this scenario ane one cannot daectivate it with the parameter jco.server.use_tls=0. I have created a empty p12 keystore and also set the jco.server.wsport to 443 (i didn't worked on 8080) Thank you very much!

[simon_luser · Accepted solution]

This property will only deactivate it on JCo side, but not on the ABAP part 😉