User Management for Non-Central AAE (PI-AF)
Use
In a dual-stack installation of SAP PI, you have the option to use the Advanced Adapter Engine (AAE) stand-alone, next to the Integration Server. This option is referred to as non-central AAE . That way, you have the runtime engines, AAE, and Integration Engine, de-coupled from each other at runtime.
By default, user management for the AAE in a such a scenario relies on AS ABAP as described under User Management and Authorization Concepts (Dual-Stack) .
Therefore, with regard to user management, there is still a coupling between both stacks. If for any reason the Integration Server system connected to the non-central AAE is down, the message processing on the non-central AAE might also be affected because the service users involved are still maintained in the Integration Server system.
Some scenarios require that the non-central Advanced Adapter Engine continues running when the connected Integration Server is down. Therefore, the user management for a non-central AAE can also be de-coupled from AS ABAP-based user management of the Integration Server. This option is referred to as local user management for non-central AAE .
Local User Management for Non-Central AAE
To configure user management in a way that it can be used de-coupled from the Integration Server, you have to perform specific steps during installation and post-installation of the non-central AAE.
Installing the Non-Central AAE
When installing the non-central AAE, after starting SAPInst , choose Parameter Mode .
Select the value Custom , make sure that you choose UME Configuration Use Java Database on User Management Engine screen.
Post-Installation Steps (Configuration Wizard)
After installation, you need to perform the following post-installation steps:
-
Start SAP NetWeaver Administrator.
-
On the Configuration tab page, choose .
-
Choose All Configuration Tasks and search for PI Adapter Engine Initial Setup (under Find ).
-
Execute the configuration step.
More information:


