Skip to Content
avatar image
Former Member

ABAP Server(Inbound) Proxies

ABAP class is deployed in SAP R3 using message interface defined in XI.

legacy ->XI WAS 6.4 ->SAP R3 (WAS 6.4)

Is there an alternate approach (ABAP class generated from netweaver developer studio) to connect legacy with local integration server of SAP R3 WAS 6.4? I'm trying to understand the pros and cons without XI as middleware. As R3 based on WAS 620 and above could able to handle proxies. Appreciate the inputs.

legacy->SAP R3 (WAS 6.4)

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Mar 27, 2007 at 11:12 PM

    Hi Ravi,

    you could use java proxy (client proxy) to connect your legacy system to SAP XI and then use an inbound abap proxy (server proxy) from XI to R3.

    I would say there is no alternative approach because you need an ABAP class inside R3, but for the legacy system, the corresponding of the ABAP class is the JAVA class created from inside XI and used (e.g. in netweaver developer studio) inside the code of your legacy application to communicate with XI.

    So your scenario should be:

    Legacy -(java proxy) -> XI -(abap proxy) ->R3

    I suggest you to have a look at: How" target="_blank">">How to Work with Java Proxies



    Add comment
    10|10000 characters needed characters exceeded

  • Mar 27, 2007 at 11:13 PM


    if you won't use XI you will loose the important thing:

    Monitoring - so you will need either to develop some monitoring youself (what for if you have XI and everything in standard) or you will not develop it... and

    someone will cry if an error will appear later on 😊

    so if you hava XI and r3 (from WAS 6.20) jut use it - don't develop

    something that will be diffucult to develop and MAINTAIN later on



    Add comment
    10|10000 characters needed characters exceeded