Skip to Content

Have you got the error message “Unable to connect to the Integration Builder, when you are trying to create a ABAP PROXY from a R/3 system?

This blog enumerates the process of Configuration required for ABAP proxy. All the configurations are available in the SAP XI configuration guide and Installation guides. This is an attempt to bring the entire configuration together.

Consider the following system landscape for configuration of the ABAP Proxy:

Two systems exist in the landscape:

System X : SAP XI 3.0 system and

System Y : SAP R/3 on WAS 620

The prerequisites to configuration for 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 HTTP connection in the business system.

Configuration Details:

Technical Setting:

1. Following Inputs are required for technical setting

1     Connection Type: H

2     Target Host: System name

3     Service Number: HTTP Port name

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

Logon Security

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

1     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).

2     Password: the password you have specified for this user

3     Client: SAP XI Integration server

4     Language: Language required

image

SAPISU_XID created in step 1. Dest://SAPISU_XID.

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

   1.Select the relevant category under Specific Configuration Data.

   2.Choose Change Specific Configuration Data.

   For ABAP Proxies, Add the following configuration:

     1.Category RUNTIME

     2.Parameters: IS_URL

     3.Current Value: dest://SAPISU_XID

image

    4.Choose ENTER.

    5.Choose the Technical settings tab page and do the following:

    6.In the Program ID field under Registered Server Program, enter LCRSAPRFC

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

image

1. You can reuse this program ID for all Business systems

2. If there is HTTP error during connection, first run transaction SLDCHECK in the Business system. Also check that HTTP connection is working fine.

3. In XI Adapter use HTTP connection rather then giving R/3 input details as this is easier to transport and maintenance

4. One receiver adapter can be used for all Interfaces connecting to a Business system.

+

To report this post you need to login first.

7 Comments

You must be Logged on to comment or reply to a post.

  1. Chandu Cheeti
    Thanks for the Web log.

    Can you please clarify this point point?

    You have installed the XI Add-On in each of these business systems as described in the Installation Guide SAP Exchange Infrastructure 3.0.

    I don’t see anything in the installation guide.

    Regards

    Chandu

    (0) 
    1. Heiko K├╝ffen
      As far as I understand for WebAS 620 ABAP you need the XI AddOn “SAP Exchange Infrastructure 2.0” (APPINT). You can install this AddOn with Tcode SAINT and apply Support Packages of it with Tcode SPAM. Note 439915 may help you with all that stuff.

      If you have SAP R/3 Enterprise 4.7×110 based on Basis Release 620 you already should have installed the AddOn with Support Package Level 1. Somewhere I found the information that Support Package Level 4 must be used for working with ABAP proxy.

      Regards
      Heiko Küffen

      (0) 
  2. Ravi Prakash Raika
    i got a problem when i am creating a HTTP conection in R/3 system
    when enter Path Prefix.
    Technical Setting:
    1. Following Inputs are required for technical setting
    1 Connection Type: H
    2 Target Host: XI
    3 Service Number: 50000
    4 Path Prefix: /sap/XI/engine/?type=entry

    here i am getting error message that “Query string not allowed”

    plz guide on this.

    (0) 
    1. Stefan Grube
      > here i am getting error message that “Query string not allowed”

      This is only a warning. Press enter to ignore it.
      Instead of port number 50000 choose the ABAP port number 8000.

      Hope that helps
      Stefan

      (0) 
  3. Charu Kulkarni
    Good post. I suppose every time someone installs a new system an the basis boys and girls forget to create these connections we would have these issues.

    Just want to share one more pain point.

    If you have followed all the steps in the configuration or this blog and still not able to connect to the central XI Integration Engine then

    Please check if the host names entered in the Exchange profile are able to be resolved from  the business system ( the SAP server >640 ).

    If the host names are not resolved then the HTTP communication will not work and SPROXY -> Goto -> Test Connection will report failure on SPROX_CHECK_IFR_RESPONSE, SPROX_CHECK_IFR_CONNECTION

    Cheers,

    Charu Kulkarni

    (0) 
  4. Gabriel Mendes

    Hi guys, i need to ask, how do you do this with PI 7.4?

    I have seen that i have to create a G type RFC named SAP_PROXY_ESR and prefix /rep but i still see local objects in ECC, i dont see the objects from my integration server, what else do i have to check? i even created this rfc’s but nothing.

    (0) 

Leave a Reply