On AS ABAP, you have to create PI dialog and service users.
Procedure
Perform the following steps in your AS ABAP system:
-
Log on using an administration user (for example, DDIC).
-
Call transaction SU01 (User Maintenance).
-
Create the following users and define them (except PISUPER) as system users (user type System):
-
PILSADMIN
User for the Change Management Server.
-
PIDIRUSER
User for the Integration Directory.
-
PIREPUSER
User for the Enterprise Services Repository.
-
PILDUSER
User for the System Landscape Directory.
-
PIAPPLUSER
User for sender applications.
-
PIRWBUSER
User for the Runtime Workbench.
-
PIAFUSER
User for the Advanced Adapter Engine (communication between SLD, Integration Server, and Adapter Framework).
NOTE
The Advanced Adapter Engine is simply referred to as Adapter Engine in the subsequent documentation.
-
PIISUSER
User for the Integration Server.
-
PISUPER
Super user with authorization for all involved tasks.
-
PI_JCO_RFC
User for RFC communication between ABAP and Java.
-
PIPPUSER
User for principal propagation.
-
PI3RDAPIUSER
User for calling a Java Web service used to set up point-to-point connections.
NOTE
The names of the users as well as their passwords can be changed as required. Ensure, however, that they are always assigned the roles as listed under Assigning ABAP Roles.
If you make changes to user names and passwords, you have to make them in transaction SU01 first and then again in the exchange profile. More information: SAP Note 999962.
For sender ABAP applications, name and password changes must also be made in the involved HTTP destinations.
-
