Solution : https://service.sap.com/sap/support/notes/1249794 (SAP Service marketplace login required)
Summary :
If HTTP is not configured in SMICM and only HTTPS is enabled, launching transaction SOAMANAGER may fail due to incomplete or incorrect SSL configurations leading to SSL errors detailed in the dev_icm logs under DIR_HOME (transaction AL11). These issues manifest as errors in SSL certificate verification, incomplete certificate chains, and failures in establishing secure SSL sessions, affecting the call to the Web Dynpro ABAP application APPL_SOAP_MANAGEMENT. To resolve, ensure URL mapping and prefix security parameters align with Note 932640, update the SSL certificate trust settings in STRUST, and verify patches from Notes 1238429 and 1229898 are applied.
Key words :
//<port-nr>/sap/bc/webdynpro/sap/appl_soap_management solution ensure, ms/urlmap_secure = 1 ms/urlprefix_secure = 1 call transaction strust, web dynpro abap application appl_soap_management, administration -> local icm -> exit soft, incorrect secure sockets layer, sslv3 read server certificate, <port_b>ssl ni-sock, secude-ssl errorstack ---------- >>error, secude-ssl errorstack ---------->> ---------- begin, call transaction smicm
Related Notes :
| 1238429 | Error in WSDL generation for access using HTTPS |
| 1229898 | Error when starting Web Dynpro applications from SAP GUI |
| 1094342 | |
| 932640 | Load balancing using message server through HTTPS |