Configuring the Non-Central Advanced Adapter Engine (PI-AF) for AEX

Use

When you use the Advanced Adapter Engine Extended (AEX), or the Process Orchestration (PO), you have the option of using a non-central Advanced Adapter Engine (AAE). This means that you can install a non-central AAE separately on a system with a different SAP system ID (SID) from the central AAE. At runtime, the non-central AAE works independently of the central one.

More information:

Prerequisites

The non-central AAE is installed with SAPInst.

For more information, see the corresponding installation guide.

Note

The central Adapter Engine has to be accessible with HTTP by the non-central Adapter Engine.
The AEX is configured.

More information: Basic Configuration for SAP PI Advanced Adapter Engine Extended

Procedure

Start SAP NetWeaver Administrator.
Choose Configuration Scenarios Configuration Wizard.
Choose CTC wizard PI Adapter Engine for AEX and follow the instructions on the screen.
Restart the system to enable registration in the System Landscape Directory (SLD).

Note

The CTC wizard performs the following steps automatically:

Reads the relevant exchange profile properties that are necessary to set up the connection between the non-central AAE and the SLD
Looks up the service users that are relevant for the technical communication between the non-central AAE and the other PI components
Creates users in the User Management Engine (UME) of the non-central AAE

Note

During the installation of the non-central AAE as an optional standalone unit for an Advanced Adapter Engine Extended, you have to choose Use Java Database as UME Data Source . This sets up “local” user management on the system of the non-central AAE.
Clears the Integration Directory cache
Creates the SLD data supplier destination

More information: SAP Note 1525614 Information published on SAP site

Manual Configuration

You can configure the non-central Advanced Adapter Engine (PI-AF) for AEX manually.

Read the following properties from the AEX system and write them in the service XPI Service: AII Config Service of the non-central Advanced Adapter Engine:

Location of the central SLD:
- com.sap.aii.connect.cr.name
- com.sap.aii.connect.cr.httpport
- com.sap.aii.connect.cr.httpsport
SLD name of the AEX system: com.sap.aii.connect.integrationserver.sld.name
Basic AEX property: com.sap.aii.ibrep.core.usage_type
Pointing to the AEX system:
- com.sap.aii.connect.directory.name
- com.sap.aii.connect.directory.httpport
- com.sap.aii.connect.directory.httpsport
- com.sap.aii.adapterframework.serviceuser.name
- com.sap.aii.adapterframework.serviceuser.pwd
- com.sap.aii.directory.serviceuser.name
- com.sap.aii.directory.serviceuser.pwd
- com.sap.aii.rwb.serviceuser.name
- com.sap.aii.rwb.serviceuser.pwd
- com.sap.aii.connect.integrationserver.sld.name
- com.sap.aii.integrationserver.serviceuser.pwd
- com.sap.aii.connect.rwb.name
- com.sap.aii.connect.rwb.httpport
- com.sap.aii.connect.rwb.httpsport
- com.sap.aii.connect.integrationserver.name
- com.sap.aii.connect.integrationserver.httpport
- com.sap.aii.connect.integrationserver.httpsport

Alerting properties

property.alerting.is.Active
property.alerting.target

Create service users

Create PIDIRUSER
Create PIRWBUSER
Create PIAPPLUSER
Create PIAFUSER
Create PISUPER

Assign roles to users

PIDIRUSER: Assign SAP_SLD_CONFIGURATOR
PIDIRUSER: Assign SAP_XI_ID_SERV_USER
PIRWBUSER: Assign SAP_SLD_CONFIGURATOR
PIRWBUSER: Assign SAP_XI_RWB_SERV_USER
PIAPPLUSER: Assign SAP_XI_APPL_SERV_USER
PISUPER: Assign NWA_READONLY
PISUPER: Assign SAP_XI_ADMINISTRATOR_J2EE
PISUPER: Assign SAP_XI_CONFIGURATOR_J2EE
PISUPER: Assign SAP_XI_DEVELOPER_J2EE
PISUPER: Assign SAP_XI_CONTENT_ORGANIZER_J2EE
PISUPER: Assign SAP_XI_RWB_SERV_USER
PISUPER: Assign SAP_XI_MONITOR_J2EE
PISUPER: Assign SAP_SLD_ADMINISTRATOR
PISUPER: Assign SAP_SLD_CONFIGURATOR
PISUPER: Assign SAP_SLD_ORGANIZER
PISUPER: Assign SAP_SLD_DEVELOPER
PISUPER: Assign SAP_XI_CMS_SERV_USER
PISUPER.Assign UDDI_Admin
PISUPER.Assign SERVICES_REGISTRY_READ_WRITE

Groups	Roles
SAP_XI_MONITOR	<String>SAP_SLD_GUEST</String> <String>SAP_XI_MONITOR_J2EE</String>
SAP_XI_SUPPORT	<String>SAP_SLD_GUEST</String> <String>SAP_XI_DISPLAY_USER_J2EE</String> <String>SAP_XI_SUPPORT_J2EE</String> <String>SAP_SLD_SUPPORT</String> <String>UDDI_TierN</String> <String>SERVICES_REGISTRY_READ_ONLY</String> <String>NWA_READONLY</String>
SAP_XI_DEVELOPER	<String>SAP_SLD_DEVELOPER</String> <String>SAP_XI_DEVELOPER_J2EE</String>
SAP_XI_CONFIGURATOR	<String>SAP_SLD_CONFIGURATOR</String> <String>SAP_XI_CONFIGURATOR_J2EE</String>
SAP_XI_CONTENT_ORGANIZER	<String>SAP_SLD_ORGANIZER</String> <String>SAP_XI_CONTENT_ORGANIZER_J2EE</String>
SAP_XI_ADMINISTRATOR	<String>SAP_SLD_ADMINISTRATOR</String> <String>SAP_XI_ADMINISTRATOR_J2EE</String> <String>UDDI_Admin</String> <String>SERVICES_REGISTRY_READ_WRITE</String> <String>NWA_READONLY</String>

Clear the AEX directory cache

Start the Integration Builder in the Integration Directory .
After registration, choose Environment Clear SLD Data Cache.

Configure SLD destinations and trigger the self-registration of the technical system

Create Java HTTP destination_SLD DataSupplier. See Configuring the SLD Data Supplier Destination .
Create Java HTTP destination SLD_Client. See Configuring the SLD Client Destination .
Call SLD DataSupplier to create the technical system.

Register Adapter Engine in SLD: Restart Adapter Framework Application synchronously.