Skip to Content
avatar image
Former Member

PI7.11 AAE configuration

I have Interfaces that use both Classical (pinpline steps in ABAP stack) and local processing (bypassing ABAP stack and thus pipeline steps in AAE).

This is an example scenario for the Local processing I like to do:

ECC<-- (soap) PI --

>JDBC client.

I've created RFC destination correctly.

Then sxmif--->created sumparameter, Senderid

In sxmb_adm:

I have IS_URL current value = dest://A_INTEGRATION_SERVER which is the classical way.

Then I added IS_URL assigned subparameter (I named it RECONRPTSENDER" for above scenario) with current value, "dest://AAE_PEH"


According to "How to Set up the Communication between ABAP backend and SOAP Adapter using XI Protocol (", page 6,

the system checks the entries with sub parameter first (for instance the above scenario has subparameter, RECONRPTSENDER that I assigend) then it should use "dest://AAE_PEH", but it is going to "dest://A_INTEGRATION_SERVER"

When I change the Corresponding Integ. Server to : dest://AAE_PEH, it does work! But I do not want to do that because I need to use the Classical processing for other scenarios!

What am I missing here? Anyone please..

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Jan 15, 2011 at 04:54 AM


    Please see if you have applied all the notes mentioned in the guide and check the system version also as mentioned in


    As per the guide->pg2,

    As you would need to have both classic central Integration Engine-based scenario and

    AAE-based scenario like at the same time, the sender SAP NetWeaver Application Server

    ABAP is also enhanced to be able to send message to both central Integration Engine and

    Advanced Adapter Engine



    Add comment
    10|10000 characters needed characters exceeded