RFC-to-SOAP webservice using HTTPS

[Former Member]

Hi experts,

I have a RFC-to-SOAP (sync) and the URL of the webservice is using HTTPS. I'm not the owner of the webservice.

Encountered these errors

- for sender comm :

com.sap.aii.af.ra.ms.api.DeliveryException: Peer sent alert: Alert Fatal: illegal parameter

- receiver comm :

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Peer sent alert: Alert Fatal: illegal parameter: iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: illegal parameter

We are not using certificate authentication so I don't think that's the cause.

Have checked that the https is running ok for ABAP but I don't think that got anything to do with the errors. Is there something wrong with SSL setting for J2EE? If yes, how may I check?

Are there some parameters to be set up? In the RFC sender comm & SOAP receiver comm, I do not find any special settings for https.

I have read this link : http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/content.htm. Is it necessary to set the Exchange Profile Parameters? My BASIS colleague is now checking it.

Thanks for reading and will appreciate any advice!

[prateek · Accepted solution]

Have you imported the HTTPS certificate in your Visual admin keystorage?

Regards,

Prateek

[Former Member · Accepted solution]

Thanks Prateek for the quick reply!

Re HTTPS certificate, do you mean the cert for my XI server or the cert from the web service?

I have tested calling the web service using SOAPUI and it works fine without using the cert given by the web service (which is expired anyway)...

[prateek · Accepted solution]

There are two things.

1. You use HTTPS in soap receiver channel. In this case you need to have Webservice certificate in you keystore.

2. You use HTTP in soap receiver channel and still use HTTPS in URL. Then there is no need to import any certificate.

Regards,

Prateek

[Former Member · Accepted solution]

Thanks for the reply!

I'm using just HTTP in soap receiver communication channel and the URL has https (no. 2).

Any idea what could be causing the error?

[Former Member · Accepted solution]

The problem has been resolved after BASIS colleague did the following :

1. Deployed Java Cripto Tool kit

2. Replace Java Cripto extension Set