2007 Jun 14 4:40 PM
I am trying to establish a HTTPS connection to an external web site in transaction SM59, but I get ICM_HTTP_CONNECTION_FAILED errors. I get the same errors from a bespoke ABAP program.
I know the request is getting to the web site, but the response is not getting back into SAP.
This is not firewall related.
I have installed and configured the SAPCRYPTOLIB software for SSL support and entered the necessary instance profile parameters.
I have configured STRUST.
SM59 is setup for type G (HTTP Connection to Ext. Server) and port no. 8443
I have started the HTTPS service in SMICM
I have noticed an odd entry in the SCICM trace file, but dont know how to fix.
<i>ERROR => Connection request from (-1/65535/0) to host: mms-sap.sapmms.com, service: 8000 failed (NIECONN_PENDING)</i>
Does anyone have any suggestions?
2007 Jun 15 4:19 AM
Not sitting in front of a SAP system I'm probably off, because my answer's too dumb: The exception indicates HTTP, but I'd expect HTTPS (not sure though if SAP really distinguishes those two protocols in the exceptions). Have you checked the box "SSL Active" on the Logon/Security tab?
2007 Jun 15 4:19 AM
Not sitting in front of a SAP system I'm probably off, because my answer's too dumb: The exception indicates HTTP, but I'd expect HTTPS (not sure though if SAP really distinguishes those two protocols in the exceptions). Have you checked the box "SSL Active" on the Logon/Security tab?
2007 Jun 15 3:23 PM
Thanks for your comments.
I've tried everything in SM59.
SAP refers to both protocols as HTTP.
I think the error is with the response coming back into SAP. SAP doesn't know what to do. It might be DNS related or I might need to configure the ICM somewhere. Oddly the response comes back into sap on port 8000 (which is HTTP). It went out on port 8443 (which is HTTPS).
?
2007 Jun 15 3:45 PM
ok. I can fix this by removing the HTTP port from SMICM - as i don't need it on my dev system. It looks like it was just picking up the first port it could find.
If I only have a HTTPS port it can only use this and it all works happily.
Not an ideal solution I must admit. There must be a way to switch off a port for inbound comms. or divert to another.