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

[LeonBoeijen]

Hello,

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="http://schemas.xmlsoap.org/soap/envelope/"><SOAP:Body><SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <faultcode>SOAP:Client</faultcode> <faultstring>Server Error</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="PARSING">GENERAL</SAP:Code> <SAP:Stack><![CDATA[ com.sap.aii.af.lib.mp.module.ModuleException: No Binding found for the Message Information at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:430) at javax.servlet.http.HttpServlet.service(HttpServlet.java:754) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103) at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:126) at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:432) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328) ]]></SAP:Stack> </SAP:Error></detail></SOAP:Fault></SOAP:Body></SOAP:Envelope></Trace>

</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>

</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.

Leon

[marksmyth]

Hello Leon,

The note 1819457 XI Runtime: @versionMinor has incorrect value 001, should resolve this error (and the notes referenced within). In particular note 1488164 XI runtime: Proxy call of Release 6.20.

Regards

Mark

[Former Member]

Hi

pls refer

http://scn.sap.com/people/michal.krawczyk2/blog/2012/01/19/michals-pi-tips-how-do-you-activate-abap-...

Rgds

Krishna

[LeonBoeijen]

Hello Krishna,

I have followed all these steps, that is why it is working on the ECC 6.0 backend system.

My problem is with the R/3 4.7 Enterprise backend system.

Leon

[Former Member]

Refer the discussion- http://scn.sap.com/thread/2093668

Should answer you

Regards

Krishna

[LeonBoeijen]

Thanks,

This link really explains that it is not possible to do abap proxy from an 6.20 system to a PI 7.31 AEX, java only.

I will find an other solution.