Proxy - PI to ECC - message not coming to ECC -Error Parsing PI Response

[Former Member]

Hi All,

Scenario is PI proxy message is reciving from ECC, but connection test from PI to ECC not work.

The user PIISUSER is correct. SLD ia working.

I have this Response Text from SM59.

HTTP/1.0 500 Empty HTTP request received

Content-Type: text/xml

Content-Length: 815

content-id: <soap-51351C81FD6941CFE10000000A4BE920@sap.com>

soapaction: 'http://sap.com/xi/XI/Message/30'

server: SAP Web Application Server (1.0;700)

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Header>

</SOAP:Header>

<SOAP:Body>

<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Empty HTTP request received</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Empty HTTP query received; message processing not possible

</SAP:Stack></SAP:Error></detail></SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope

Pleas help me on it.

Thanks

[Former Member · Accepted solution]

Hi Ejersbo,

This is really an error, this is the typical response you get when doing a connection test on an HTTP type destination from SM59.

Have you checked the normal things like:

- SXMB_MONI in PI

- SMQ2 in PI

etc to see where the messages are getting stuck?

Regards, Trevor

[Former Member · Accepted solution]

Hi Trevor,

Thanks for reply,

There is no error on SMQ2, but I have this from : - SXMB_MONI in PI

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--  Inbound Message

  -->

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

  <SAP:Category>XIAdapterFramework</SAP:Category>

  <SAP:Code area="MESSAGE">GENERAL</SAP:Code>

  <SAP:P1 />

  <SAP:P2 />

  <SAP:P3 />

  <SAP:P4 />

  <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: iaik.security.ssl.SSLCertificateException: Peer certificate rejected by ChainVerifier</SAP:AdditionalText>

  <SAP:Stack />

  <SAP:Retry>M</SAP:Retry>

  </SAP:Error>

Thanks

[markangelo_dihiansan · Accepted solution]

Hello,

Since you are using the Adapter Framework, you need to 'trust' the certificates of the ECC system. You can do this by placing the SSL CA (certificate authoritie/s) of the ECC system into the TrustedCAs view in NWA.

Hope this helps,

Mark

[Former Member · Accepted solution]

Hello Mark,

Thanks for help;

On PI NWA "TrustedCAs" are  about 12 Name :

EntrustPersonalServerCA,

EntrustServerCA

SAPPassportCA,

SAPServerCA

.

.

Which one should I use.

Thanks

[markangelo_dihiansan · Accepted solution]

Hello,

You have to ask the basis of ECC system to provide you their CA certs. This will be the one you will install in NWA.

Regards,

Mark

[smavachee]

Nothing wrong with it. Connection is successful.

You are sending an empty call, test it by sending an ABAP Proxy message.

It will work.

Thanks

Sunil

[markangelo_dihiansan]

Hello,

The response from the SM59 destination test of type H is normal. It would really return a 500 because you sent an empty HTTP Body, but aside from that, the connection is working. What is the error that you are getting?

Regards,

Mark