Skip to Content
avatar image
Former Member

activate-abap-proxies-with-aex

Hi ALL,

I am facing issue while connecting my ERP system to PO 7.4.

I have done the exact steps as http://scn.sap.com/people/michal.krawczyk2/blog/2012/01/19/michals-pi-tips-how-do-you-activate-abap-proxies-with-aex--simplified-version, but the RFC PI_AAE is failing with 500 error.

When i checked launching the URL:
http://<aaehost>:<port>/XISOAPAdapter/MessageServlet?ximessage=true

It is failing with 500 Server error:


In default Trace, Error log says below:

Error#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#

com.sap.ASJ.web.000137#BC-XI-CON-SOP#sap.com/com.sap.aii.adapter.soap.app#C000C0A8A39802AC0000000000000DCC#1737950000000004#sap.com/com.sap.aii.adapter.soap.app#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0##12693CADAC5411E4C5F20000001A84DE#12693cadac5411e4c5f20000001a84de#12693cadac5411e4c5f20000001a84de#0#Thread[HTTP Worker [@228500667],5,Dedicated_Application_Thread]#Plain##

Cannot process an HTTP request to servlet [MessageServlet] in [XISOAPAdapter] web application.

[EXCEPTION]

null; nested exception caused by:

com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection SOAP_http://sap.com/xi/XI/Systemcannot be created as it was not registered before!

  at com.sap.engine.messaging.impl.api.ConnectionFactoryImpl.checkConnectionRegistration(ConnectionFactoryImpl.java:259)

  at com.sap.engine.messaging.impl.api.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:113)

  at com.sap.engine.messaging.impl.api.ConnectionFactoryImpl.createConnection(ConnectionFactoryImpl.java:99)

  at com.sap.aii.adapter.soap.web.SOAPHandler.<init>(SOAPHandler.java:153)

  at com.sap.aii.adapter.soap.web.MessageServlet.init(MessageServlet.java:185)

  at com.sap.engine.services.servlets_jsp.server.application.WebComponents.getServlet(WebComponents.java:864)

  at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)

  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)

Can anyone please assist me in resolving the same.


Regards,

Prashanth


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • avatar image
    Former Member
    Feb 04, 2015 at 11:19 AM
    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 04, 2015 at 11:33 AM

    Hi Prashanth,

    configure the following property in the XI Service.

    1. Open nwa > Configuration > Infrastructure > Java System Properties

    2. Select Services tab and Filter for 'XPI Adapter: XI'

    3. In the properties tab search for 'xiadapter.version.minor'

    4. Change the value to 0

    Thanks,

    Naveen

    Add comment
    10|10000 characters needed characters exceeded

  • May 15, 2015 at 08:32 AM

    We experienced exactly the same issue in a Unix HA Clustered Production environment, but did not experience it on the same unix Development / QA which aren't clustered.

    We tried all of the above suggestions to no avail. However our Default Traces contained a lot of other SLD Errors.

    The steps below were the reply from SAP Support and these solved the problem for us:

    Reply from SAP:

    We have checked the default traces you have provided us with and they

    are indeed full of SLD related errors.

    The most important one should be the following:

    SLD Registration Job: Error during Http request to

    http://<host>:<port>/AdapterFramework/regtest. Http code: 503

    All other SLD related errors that can be found within the traces might

    be a result of this error.

    In order to try to fix this, please check the configuration maintained

    in "NWA -> Configuration -> Infrastructure -> SLD Data Supplier

    Configuration" and note the following:

    To properly configure this service, use the Destinations Service to:

    1. Set up the registration by creating a destination called

    "SLD_DataSupplier" of type HTTP. Enter the following configuration

    settings. (Note: The specified user must have the user role

    "SAP_SLD_DATA_SUPPLIER" or higher on the target SLD Server.)

    - Appropriate URL (http://<host>:)

    - Authentication should be set to BASIC

    - Appropriate Username and Password

    2. Set up the AS Java access to the SLD by creating a destination

    called "SLD_Client" of type HTTP. Enter the same configuration

    settings as in the SLD_DataSupplier destination. (Note: The specified

    user must have user role "SAP_SLD_GUEST" or higher. Additional write

    access permissions may be required by certain applications. Refer to

    the corresponding application documentation for SLD access requirements.

    In addition to the above, please also perform the following steps:

    - Access the SLD - http://<host>:<port>/dir -> SLD

    - Log on as an administrator for AS Java / SLD administrator

    - Choose Administration

    -> Settings

    -> "Perform Role Mapping"

    Afterwards, please try registering the PI components in the SLD again.

    Finally, please try to perform CPACache refreshes as follows:

    http://host:j2eeport/CPACache/refresh?mode=full
    and
    http://host:j2eeport/CPACache/refresh?mode=delta

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 26, 2015 at 12:34 PM

    Hi Prashanth,

    I assume you have newly installed/migrated to PI 7.4 system.

    Can you please cross check whether post installation configuration steps were performed completely or not.


    In most of the cases, this could be the issue.


    Also, please check whether you are having issues with RFC destination SAP_PROXY_ESR or not.

    Regards

    Vishnu

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 30, 2016 at 02:45 AM

    Dear All,

    This issues is resolved? I encounter same problem. I execute the report SPROX_CHECK_HTTP_COMMUNICATION, failed. The third-party system submit a request to ECC via PI 7.4 single stack. I set a external breakpoint. BUT there is no vaule for every field.

    Anybody know the reasons?

    Thank you for support.

    Many thanks & best regards,

    Hubery

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Cach refresh worked for me.

      The HTTP rfc from ECC to PO is working fine now.

      Thanks a lot Paul for the solution