Skip to Content

What is AEX

PI 7.3 offers the same functionality regarding to prior version but with some new features. One of those is the Advance Adapter Engine Extended (AEX) with richer connectivity and routing capabilities.

This new Engine has the particularity that relies in in Java only, not ABAP involved, is available with added features to close the gap with the dual-stack option.

So, a new intallation option is available when deciding to install SAP PI. AEX has the particularity that  provides the connectivity capabilities of the Advanced Adapter Engine (AAE). As well AEX provides design and configuration tools (ES Repository and the Integration Directory) to set up scenarios that are based on the AAE. The Integration Directory installed with AEX contains the same subset of configuration options as that of the AAE, basically the integrated configuration.


Based on that we conclude that since AEX is based on AS Java alone, fully independent, it is easier to install and maintain as well as it needs less memory and data storage. Therefore, AEX is a cost-saving option compared to a full installation of SAP NetWeaver PI.

There are some restrinction to keep in mind when deciding to go for AEX like:

  1. The connectivity options are restricted to the adapters of the AAE.

  2. You cannot use integration processes (cross-component Business

    Process Management).

  3. You can only use process integration scenarios as Modeling option

    in the ES Repository. ABAP mapping is not available

but also you consider the benefits that is carry with:

  1.  Reduction in overall TCO with single-stack Faster installation, less hardware, fast restart

  2. Drastically reduced resource consumption scenarios speed.

  3. Monitoring simplification with one dedicated toolset and one stack

  4. One database scheme


Three type of use cases applys when you decided to implement AEX:


  • Using AEX as lean, low-cost integration middleware
  • Using AEX as test environment

AEX in combination with SAP NetWeaver PI

  • Separating landscapes for different regions or organizations of an enterprise
  • Separating network zones
  • Using AEX as manual fail-over system (Business Continuity)

Using AEX as lean, low-cost integration middleware

  • Fundamental-to-advanced messaging capabilities for SAP and non-SAP integration (no immediate or major BPM requirements)
  • High performance and robustness
  • Avoid larger system resource and operational footprint and TCO of dual-stack PI installation  

I hope, this blog allow you to understand what AEX is and the mains goals of it.


Using AEX as lean, low-cost integration middleware
Using AEX as test environment
Be the first to leave a comment
You must be Logged on to comment or reply to a post.