Hi Leo,
The program SPROX_CHECK_HTTP_COMMUNICATION doesn't check connectivity from ECC to PI, but is used to check if ECC (or other ABAP system where it is called) is capable of processing HTTP requests. What SPROX_CHECK_HTTP_COMMUNICATION does is, it sends an HTTP request to a local HTTP ping service (of the system where the program was called), which is normally ICF service /sap/public/ping (less commonly is /sap/bc/ping). HTTP communication failure error indicates the issue either when sending an HTTP request to a ping service, or receiving and processing response from it.
To progress with analysis of root cause of an error, please check:
- Details (long text) of an error message in the program SPROX_CHECK_HTTP_COMMUNICATION. It shall contain indication of when the error occurred - when sending a ping request or processing its response;
- In transaction SMICM, check that HTTP service is active (menu Goto > Services). If not, activate it;
- In transaction SICF, navigate to a service /sap/public/ping and check if it is active. If not, activate it;
- In transaction SICF, navigate to a service /sap/public/ping and execute a test service call for it (right click on a service and select "Test Service" from a context menu). Ensure that you get response with HTTP status code 200 saying that server was reached successfully.
If checks above are all successful, but error remains, it may also be helpful to collect HTTP trace during execution of the program SPROX_CHECK_HTTP_COMMUNICATION so that you can retrieve more details about context of an error. To do this, you can increase ICM trace level to maximum (3) in transaction SMICM, execute the program SPROX_CHECK_HTTP_COMMUNICATION and then check HTTP trace file (for example, using transaction SMICM or accessing corresponding trace file - dev_icm on application server). Don't forget to reduce ICM trace level back to its original value when tracing is completed.
Regards,
Vadim