cancel
Showing results for 
Search instead for 
Did you mean: 

message via SM59 "HTTP connection to external partner" not sent to partner

Former Member
0 Kudos

I have a scenario where I am supposed to send a message to an external partner using https. I have created the HTTP connection in SM59 "HTTP connection to external server" and selected the default certificate. This connection is referenced in the http receiver CC in PI 7.1, but when I send the iDoc message from the backend it is not sent out of PI to the external partner.

There are no apparent errors in the trace files in SMICM on the PI system, but our firewall guys say, that they cannot see the outgoing call in our firewall and the external partner cannot see the message either.

There is connection to the external server from the PI server, which has been confirmed by a telnet connection.

We think that there might be a problem on our web server, but we are not sure.

We have previously succeeded in calling an other server at the external partner from the PI system using a different client certificate. When we do a connection test in SM59 we get an error 500 but the external partner can see the GET request in their firewall.

Any suggestions are more than welcome

MIkael

Accepted Solutions (0)

Answers (3)

Answers (3)

abhay_rajhans2
Contributor
0 Kudos

Hi Mikael.

Check following link with the response of Michal.

Former Member
0 Kudos

> When we do a connection test in SM59 we get an error 500 but the external partner can see the GET request in their firewall.

error 500 is ok in that case. So you got a response from your partner in that case which shows the technical connection is ok (at least on firewall level).

Now plese check in SXMB_MONI and runtime workbench message monitoring how far the message came in PI.

CSY

stefan_grube
Active Contributor
0 Kudos

Have you checked, that the message is going through PI without errors?

And when there is an error, what is the error message?

Former Member
0 Kudos

The error message appears in the call adapter pipeline step before the supposed mapping is supposed to take place. The error message is:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Call Adapter --> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""><SAP:Category>XIAdapter</SAP:Category><SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code><SAP:P1>400</SAP:P1><SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:Stack>HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED

</SAP:Stack><SAP:Retry>A</SAP:Retry></SAP:Error>

Mikael

Former Member
0 Kudos

> before the supposed mapping is supposed to take place.

? It more looks as if the error occurs when sending via the HTTP receiver.

What is the content-type used in the HTTP receiver ? text/xml ?

CSY

Former Member
0 Kudos

yes, text/xml.

Besides the trace files in SMICM of the PI system, the message monitor in RWB and the xsmb_monitor, are there any other places to look for the reason?