HTTPs Post with PI

[Former Member]

Hi friends,

someone already used PI to perform HTTPS post?

Could you send me a walkthrough of the activity?

I'm currently getting the following error:

<?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>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>

<SAP:P1>110</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Error while receiving by HTTP (error code: 110, error text: )</SAP:Stack>

<SAP:Retry>A</SAP:Retry>

</SAP:Error>

Thank you.

Bruno

[Former Member]

Hi Bruno,

In order to send data via HTTPS you need to install the security certificates in PI system. Have you or your basis guys done this? Are you using HTTP or SOAP adapter to send data to your receiver. Please let us konw what details you have given in this channel.

You can do a test using this blog:

/people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway

Regards,

---Satish

[Former Member]

Hi Satish,

Thanks for the help.

Man, had total preference for SOAP, however, my Webservice only accepts requests via HTTPS Post directly, without the attributes contained in SOAP. So I am using the HTTP adapter.

The URL is HTTPS, however, do not own certificate for the exchange of information between the client and server.

Can anyone help me?

Thanks again.

[Former Member]

Hi!

First of all HTTPS has to be configured in your XI/PI. And then you have to ask your network guys whether there is a proxy / firewall between your PI/XI and the receiver service. If so the communication has to be configured there. And additionally you have to maintain the proxy server in your PI/XI.

Regards,

Volker

[Former Member]

Hi,

There is no proxy or firewall between PI and the service receiver. Has installed the SAP Criptograph Library and set up an RFC Destination type "G" with hostname, nº 443 and path.

There's something else to do?

Thank you.

[agasthuri_doss]

Hey,

Check this thread

Cheers

Agasthuri