Skip to Content
author's profile photo
Former Member

INTERNAL.PROXY_NOT_ALLOWED_ON_IS

I am trying to execute the ABAP proxy which tries to push the data into Integration Server.The call is made from ABAP program which is RFC enabled.

While executing this it throws the following system exception.

*****************

INTERNAL.PROXY_NOT_ALLOWED_ON_IS

Proxy calls on the sender or receiver side are not permitted on the IS (client)

******************

I would really appericate any help on this.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • Best Answer
    author's profile photo
    Former Member
    Posted on Mar 08, 2005 at 07:08 PM

    Hi Christine,

    Thanks for the response.I understand the fact that there is nothing extra we can get by having the proxy call through XI server to XI Server ( In fact does not make much sense ) and we can always generate the WebService for Interface.

    But the reason why I am trying to use the proxy is to handle the System Exception and to send these exception back to sender.In proxy call I can catch the system/application exception and form the exception message to send this back to sender through webService.

    I am not sure how to handle the system exception otherwise. I know that we can handle the application exception by Fault Message but not sure about the system exception and so is the proxy approch followed.

    Hope this makes sense.

    Thanks,

    Samir

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Samir,

      You're saying you want to push information into the XI client (Integration-server client). And that's not possible with XI (and causes the error).

      The integration server itself can only be the HUB system, it can never be the endpoint of the scenario. And if you want the data on the XI client to be terminated, e.g. push it into the client it must be the endpoint. This is a scenario tou can't get working.

      What you can do is create a second client on the same system where the XI integration server client resides and give that client the role Applicaton System in SXMB_ADM. Then you can use that client as endpoint in the scenario.

      Best regards,

      Alwin

  • author's profile photo
    Former Member
    Posted on Mar 07, 2005 at 10:18 PM

    Hallo Samir,

    could you please explain your scenario in a bit more detail? Why is your method RFC enabled? I don't think you'll need that.

    Normally if you have an outbound ABAP proxy, you need to create a program that fills the proxy structure and if that is finished pass it to method execute_asynchronous of your proxy which will take care of everything else(including call to Integration Server).

    best regards

    Christine

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Mar 08, 2005 at 02:44 PM

    The end goal is to have the WebService for ABAP proxy which is not possible directly. So I am calling proxy form ABAP Function which I have made as an RFC enable in order to create the webService of it.

    To Explain the situation little more here are the details.

    I have to have the webService which will push the data to integration server.I could have achieved or rather had achieved this by having the SOAP adapter as an inbound adpater, but I did not find any way to handle (send it to sender sys) the system exception ( thrown by XI ).

    In order to handle the system exception I created the ABAP proxy for synchronous outbound interface and tried to call the proxy from ABAP function where the system exception is caught and enabled it as RFC function to expose it webService.

    Before exposing the calling ABAP function as webService I tried to test the function which throws the following exception on execution.

    -


    INTERNAL.PROXY_NOT_ALLOWED_ON_IS

    Proxy calls on the sender or receiver side are not permitted on the IS (client)

    -


    All component resides on the same XI server( the proxy , the calling function and Interface)

    hope this clarifies the situation. I really appricate the response on this and hope to get more help!

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Samir,

      as to my understanding of Proxies, you have a mistake in your concept, which is that the Proxy itself resides on XI. ABAP Proxies reside within an R/3 (or an other SAP application system like APO, CRM etc) representing an XI interface there. If you put the data into the proxy it gets sent to the XI interface and XI will process it. Creating an ABAP proxy on XI itself doesn't make sense as you don't need an (additional) representation of an XI interface on XI.

      If i understand you correctly, you want to create a WebService from an XI interface. To do so, go to the Intgeration Directory and choose menu "Tools --> Define Web Service" which opens a wizzard guiding you through WebService creation.

      If you want to create a WebService on XI for a BAP / RFC (located in R/3 etc.) refer to this article XI 2.0: Expose BAPI/RFC as Web Service How To explaining the seperate steps.

      best regards

      Christine

  • author's profile photo
    Former Member
    Posted on Mar 09, 2005 at 09:29 PM

    End point is a RFC which is set as receiver in XI. I wanted the mechanism to handle the system error which can be enveloped in webService response message to sender.

    Looks the only way to do this is to have another client and proxy call from that client and expose that calling program as webService.

    Is there any other way to handle the system exception in the scenario where sender needs to call the webservice and expects back the response either as correct response/application error (receiving side)/system error (XI)?

    Thanks,

    Samir

    Add comment
    10|10000 characters needed characters exceeded