Port Configured in R/3 system to Call a proxy in PI...RFC connection test

[Former Member]

Hi,

We have to call a proxy in the PI system. For that We had configured a logical port(T.Code - LPCONFIG) in R/3. In that we had given a RFC destination with the Connection type HTTP.

Whenever we test the connection Response body is as given below. Can one tell me what could be the problem.

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

<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" 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:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>

</SAP:Error>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

Thanks,

Sekhar.J

[sunil_singh13]

Hi Sekhar,

Whenever we test the connection

you get such response during testing of your connection. It is not a error.

You must have got SOAP response code 500. It means connection was sucessful.

Thanks

Sunil Singh

[MichalKrawczyk]

Hi,

>We have to call a proxy in the PI system. For that We had configured a logical port(T.Code - LPCONFIG) in R/3. In that we had given a RFC destination with the Connection type HTTP.

first of all you don't need LPCONFIG to call a proxy from R/3

then calling a proxy in PI system means you need to call from PI (IE server) to some other clinet on PI (application client) and not from R/3 - is that what you're trying to do ?

Regards,

Michal Krawczyk

[Former Member]

Hi Micheal,

Sorry it is a typo from my side. I am calling a proxy in R/3 by using an ABAP program.

The code in the ABAP program is as given below. In the below code, we are using logical port to call PI system's In bound Method.

DATA: loc_object TYPE REF TO zco_si_eccacknowledgement_out.

DATA: loc_rqst TYPE zeccacknowledgement.

DATA: loc_ack TYPE zdt_eccacknowledgement.

DATA: loc_port TYPE prx_logical_port_name VALUE 'DEFAULT'.

CREATE OBJECT loc_sys_flt .

TRY.

CREATE OBJECT loc_object

EXPORTING

logical_port_name = loc_port.

.

CATCH cx_ai_system_fault INTO loc_sys_flt.

ENDTRY.

loc_ack-request_id = '1000000034'.

loc_ack-mdm_id = 'R17'.

loc_ack-system_id = 'XYZ'.

loc_ack-status = 'FAIL'.

loc_ack-err_msg = 'Fail Test in DU1 on 08/02/2009'.

loc_rqst-eccacknowledgement = loc_ack.

TRY.

CALL METHOD loc_object->si_eccacknowledgement_out_asyn

EXPORTING

output = loc_rqst.

CATCH cx_ai_system_fault INTO loc_sys_flt.

ENDTRY.

[Former Member]

Hi,

in your report assign loc_port to the XI port defined in WE21.........

Regards,

Rajeev Gupta

[markangelo_dihiansan]

Hi,

That could be because you are sending nothing(empty payload) to the destination. It looks like the connection to the end system is working though. Try sending a message to the target system. This should work.

Hope this helps,