ABAP Proxy communication (Server Proxy)

By Suraj Kumar Pabbathi, PI Competency Lead, YASH Technologies

Proxy objects implement message interfaces from Integration Repository. Proxies are executable interfaces, which converts non-language-specific interface descriptions into WSDL. i.e., you use proxies to implement the actual message exchange that is described in the Integration Builder. 

Types of Proxy objects: You can use message interfaces to create the following proxy objects:

  • ABAP Proxy objects
  • JAVA Proxy objects

During the process of ABAP proxy generation, it gets WSDL (Web Service Description Language) description of message interfaces from the Integration Repository by using HTTP communication. 

Proxy Generation

As part of SAP Web AS 6.40

  • ABAP proxy generation enables you to generate proxies to communicate by using the Web service infrastructure and by using SAP Exchange Infrastructure
  • ABAP proxies that were generated from message interfaces in the Integration Repository (IR) can be used in both infrastructures.
  • This means that if none of the Integration Server services are available for a proxy-to-proxy communication scenario in ABAP, you can use a point-to-point connection using the Web service infrastructure instead.


The prerequisites to configure ABAP Proxy include: (landscape dependent) 

  1. The business systems should be based on SAP Web AS 6.20 and SAP Web AS 6.20 kernel patch level above 1253
  2. You have installed the XI Add-On in each of these business systems as described in the Installation Guide SAP Exchange Infrastructure 3.0
  3. The business systems and your central Integration Server are maintained in the System Landscape Directory (SLD).

 Configuration required on the Business System:

1.       Create a HTTP connection in the business system using transaction SM59

Technical Setting:

·         Connection Type: H

·         Target Host: System name

·         Service Number: HTTP Port name

·         Path Prefix: /sap/XI/engine/?type=entry

Logon Security

On the Logon/Security tab page, enter the following logon data:

·         User: XIAPPLUSER (for example); this user should represent the sending business system (see also the SAP XI Security Guide under Service Users for Message Exchange).

·         Password: the password you have specified for this user

·         Client: SAP XI Integration server

·         Language: Language required 

2.       Configuration Business system as local Integration Engine.

1.       Go to Transaction SXMB_ADM

2.       Choose Edit --> Change Global Configuration Data.

3.       Select Role of Business System: Application system

4.       Corresponding Integration server: dest://<HTTPDESTINATION>. Here <HTTPDESTINATION> XI_XIR_CONNECTION created in step 1. Dest://XI_XIR_CONNECTION.

5.       Under Specific Configuration Data you can specify additional configuration data

    • Select the relevant category under Specific Configuration Data.
    • Choose Change Specific Configuration Data.
    • For ABAP Proxies, Add the following configuration:
      1.Category RUNTIME
      2.Parameters: IS_URL
      3.Current Value: dest://XI_XIR_CONNECTION


3.       Connection between Business System and System Landscape Directory

  • Create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection.
  • To create RFC Destination: LCRSAPRFC
    • Connection Type: T
    • Choose the Technical settings tab page and do the following:
      In the Program ID field under Registered Server Program, enter LCRSAPRFC
      This program ID must correspond to a program ID specified in the RFC engine settings of the SAP J2EE Engine on the Integration Server host.
  • Repeat the above step for RFC destination for SAPSLDAPI

4.       Maintaining the SAP J2EE Connection Parameters for LCRSAPRFC and SAPSLDAPI in SAP J2EE engine

  • Goto J2EE Engine
  • Choose Cluster --> Server --> Services. JCo RFC provider
  • Under RFC destination specify the following:
    Program ID: LCRSAPRFC
    Gateway Host: <Integration Server host>
    Gateway Service: <Integration Server gateway service>
    Number of process: 3
  • Under Repository specify the following: Application Server: <Integration Server host>

5.       Maintain SLD access details in Transaction SLDAPICUST

If there is an HTTP error during connection, check the error using the transaction SLDCHECK in the Business system. Also ensure that HTTP connection is working fine.

In XI Adapter use HTTP connection rather than giving R/3 input details, as this is easier to transport and for maintenance. One receiver adapter can be used for all Interfaces connecting to a Business system.



Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image