Enabling Principal Propagation for ABAP Messaging Components

The context of the user to be propagated is impersonated again after a message restart or during batch processing only if principal propagation is enabled for the involved messaging component.

The ABAP messaging components are the Integration Server and the Integration Engines of the sender and receiver systems executing ABAP proxies.

On the Integration Server, principal propagation is enabled by the basic configuration wizard. More information: Creating RFC Destinations on AS ABAP .

To enable principal propagation on your sender and receiver systems, perform the following steps on each component:

1. From your SAP Easy Access user menu, choose  Exchange Infrastructure    Administration    Integration Engine - Administration    Configure Principal Propagation .

2. Choose Recreate .

   This executes the report RSXMB_CONFIG_PP. This report creates the type 3 RFC destination SAPXIPP<clnt>, where <clnt> represents the three-digit client of the respective messaging component. In addition, it generates the system user PIPPUSER with a random password and the role SAP_XI_APPL_SERV_USER.

   Note

   If you use a central user administration, you must create this RFC destination and user manually. For the RFC destination, specify the following values:

   • Name: SAPXIPP<clnt>

   • Connection type: 3

   • Client: <clnt>

   • User: PIPPUSER

   • Password: <password of PIPPUSER>

     Leave the technical settings Target Host and System Number empty.