Skip to Content

Overview: Configuration-Guide for ABAP backend systems integrating with AEX

All ABAP backend systems involved in an AEX integration scenario need to be connected to the AEX. To ensure that all adapters are properly running with the ABAP system, different configuration steps are required and need to be completed before any integration scenarios can be developed. Therefore I created the following blog to provide an overview about all necessary steps to be completed.

I tried to provide a complete set of guides (either by referencing to my own blogs or by referencing to existing good blogs) for properly setting up the AEX and any ABAP backend system for different integration scenarios. Not all of the steps are mandatory since the required steps mainly depend on the type of integration scenarios used. It is stated in brackets if a configuration step is mandatory or not.

Setup Steps:

  1. Setup of SLD connections (mandatory)
  2. Setup of proxy connections (optional if no proxies are used)
  3. Integration Engine configuration and backend queue activation
  4. Setup of IDOC_AAE adapter (optional if no IDOCs are used)
  5. Activation of XI services on ABAP system (optional if no SOAP or proxy is used)

1st step: Setup of SLD connections:

Please refer to my blog for details regarding setup of SLD connections:

2nd step: Setup of proxy connections:

Please refer to my blog for details regarding the setup of a proper proxy connectivity:

3rd step: Integration Engine configuration and backend queue activation:

Please refer to my blog for details regarding the integration engine configuration:

4th step: Setup of the IDOC_AAE adapter:

William Li wrote a very good blog about the required setup steps. Please refer to this link:

5th step: Activation of XI services on ABAP backend system

Please refer to my blog for details regarding the integration engine configuration:

Please let me know if anything is missing or if I explained thing wrong in this or any referenced blog.

This helps to improve this guide a lot!

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

    please review step

    -> 5th step: Activation of XI services on ABAP backend system

    as this should be done with a standard report and not manually (as per my comment to this blog)

    Thank you,


    Michal Krawczyk 

  • Hi Harald,

    I was working on single stack for the first time and I was all at sea. I knew what all transactions should be done in dual stack but here I was struggling like a fresher 🙁

    Your blog was very helpful to me. Thanks a lot 🙂



  • Thank you so much for this blog Harald.

    I am having a small doubt.

    For proxy communication:

    2. Step: RFC-Connection to the AEX

    SM59 -> http Connection to ABAP System (Type H)

    I am little confused. Should we create H type connection or G type connection?

    In many other blogs I have observed they have suggested to create G type connection.

    Please help. We are in SAP PO 7.4 single stack.



      • I am also confused by the RFC connection type. According to the HHTP Destination for the Advanced Adapter Engine is type "G" below:

        Creating the HTTP Destination for Advanced Adapter Engine  

        To create the HTTP destination to connect your ABAP backend system (business system) to Advanced Adapter Engine (AEX), perform the following steps:

        1. Start transaction SM59.An overview of RFC connections is displayed.
        2. To create a new RFC connection, choose  Create .
        3. Specify an RFC destination.
        4. Specify Connection Type   G (HTTP Connection to External Server).
        5. Add a short description of the RFC destination.
        6. Choose  Enter .The settings fields for the connection type are displayed.
        7. On the  Technical Settings tab, specify the HTTP address for the gateway that the Advanced Adapter Engine will use to send messages.

        Source:Connecting the ABAP Backend to Advanced Adapter Engine - Configuring Process Integration After Installation - SAP Librar…

  • Hi Harald,

      This is a nice work; really helped in transitioning from SAP PI 7.31 to SAP PO 7.4.

      Just to add that i was confused about the type of the RFC connection (H or G); confusion stemmed from the title for Type H - HTTP Connections to ABAP Systems. I guess it does not matter.

    Thumbs up for you.