Show TOC

Background documentationUsing Central and Non-Central Advanced Adapter Engines Locate this document in the navigation structure

 

You can set up the Advanced Adapter Engine in the following ways, depending on the chosen installation option.

More information: Installation Options

Dual-Stack PI Installation

In a dual-stack PI installation, you have the following options how to set up the Advanced Adapter Engine (AAE).

  • You can use the AAE as part of the Integration Server.

    This option is called central Adapter Engine.

  • You can use the AAE stand-alone, next to the Integration Server.

    That means, the AAE can be installed on a system with a different SAP system ID (SID) than the Integration Server and can be used as an independent integration hub. However, note that you need an ES Repository and an Integration Directory as design and configuration tools in order to set up the scenarios.

    This option is called non-central Advanced Adapter Engine.

The following figure illustrates the constellations of PI components in a non-central AAE setup for a PI dual-stack installation:

This graphic is explained in the accompanying text.

Using a Non-Central AAE within a Dual-Stack PI Installation

Note Note

By default, the non-central AAE uses the user management of the Integration Server. In order to decouple the non-central AAE from the Integration Server also with regard to user management, you have also the option to configure a “local” user management on the host of the non-central AAE.

End of the note.

This setup enables you a more robust usage of the non-central AAE.

More information: User Management for Non-Central AAE (PI-AF)

Advanced Adapter Engine Extended (AEX) Installation

In an AEX installation, you also have the option of using an AAE non-centrally.

The design and configuration environment (ES Repository and Integration Directory) resides on the system of the central AAE. Both central and non-central AAE register themselves at the same System Landscape Directory (SLD).

The following figure illustrates the constellations of PI components in a non-central AAE setup for an installation of the Advanced Adapter Engine Extended (AEX):

This graphic is explained in the accompanying text.

Using a Non-Central AAE Within an AEX

With regard to user management, the non-central AAE works completely autarkic because it uses a local User Management Engine.

More information: Advanced Adapter Engine Extended