Skip to Content
Oct 08, 2013 at 11:39 AM

SAP ABAP Proxy 4.7 Enterprise to PI 7.31 AEX (Java only)



I am converting a XI 3.0 system to a new PI 7.31 Java Only stack. I have different SAP backend systems (ECC 6.0 and R/3 4.7 Enterprise)

I am able to use abap proxies from an ECC 6 back-end system using the sender SOAP Adapter (message protocol xi 3.0) without any problems.

Now the problem:

I started converting abap proxies on a SAP 4.7 Enterprise system, the SAP core is 6.20 and the PI_BASIS 2005_1_620 is at sp 16.

I have adapted the SPROXY and all the SLD transactions to the new PI 7.31. They are all working fine.

I have also adapted the url to <host>:<port>/XISOAPAdapter/MessageServlet?ximessage=true

The abap proxies worked fine with the XI 3.0 system, but when sending the proxy to the PI 7.31 I get into problems.

The program that calls the proxy is working fine, no errors. The message is added nicely to the SXI_MONITOR.

I get an error in the sxi_monitor when calling the Integration Server.

This is the message:

< Trace level =" 1 " type =" B " name =" CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP " >

<Trace level="3" type="T">HTTP-client: creating...</Trace>

<Trace level="3" type="T">HTTP-client: creation finished</Trace>

<Trace level="3" type="T">Serializing message object...</Trace>

<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>

<Trace level="3" type="T">HTTP-client: request sent</Trace>

<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>

<Trace level="3" type="T">HTTP-client: response received</Trace>

<Trace level="3" type="T">HTTP-client: checking status code...</Trace>

<Trace level="3" type="T">HTTP-client: status code = 500</Trace>

<Trace level="3" type="T">HTTP-client: closing...</Trace>

<Trace level="3" type="System_Error">HTTP-client: error response= <?xml version='1.0'?> <SOAP:Envelope xmlns:SOAP=""><SOAP:Body><SOAP:Fault xmlns:SOAP=""> <faultcode>SOAP:Client</faultcode> <faultstring>Server Error</faultstring> <faultactor></faultactor><detail><SAP:Error xmlns:SAP="" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSING">GENERAL</SAP:Code> <SAP:Stack><![CDATA[ No Binding found for the Message Information at at javax.servlet.http.HttpServlet.service( at javax.servlet.http.HttpServlet.service( at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at at$FCAProcessorThread.process( at at at at$ ]]></SAP:Stack> </SAP:Error></detail></SOAP:Fault></SOAP:Body></SOAP:Envelope></Trace>


<Trace level="1" type="System_Error">Exit XMB because of system error!</Trace>

<Trace level="3" type="System_Error">System-Error: HTTP.HTTP_STATUS_CODE_NEQ_OK</Trace>

<Trace level="3" type="System_Error">HTTP status code 500 : Internal Server Error</Trace>


On the monitoring side of the AEX (PI 7.31 Java Only) there is no information regarding the message.

Can someone tell me if it should be possible to connect a SAP R/3 4.7 system to a PI 7.31 java only system using abap proxies?

Thanks in advance.