Show TOC Start of Content Area

Background documentation Service Users for Internal Communication  Locate the document in its SAP Library structure

These service users are used for internal communication between PI components, which is usually triggered by interaction of dialog users. The service users provide dialog-free access to the involved PI components. They have SAP user roles in SAP NetWeaver Application Server ABAP (AS ABAP) that are available as user groups in SAP NetWeaver Application Server Java (AS Java). For an overview of the internal communication within a PI landscape, refer to Communication.

The following general principles apply for internal communication:

      Each PI component that communicates with other PI components identifies itself by means of a dedicated service user. Therefore, each required service user must be created in each target component.

      The name, password and language of all the service users are defined in the exchange profile.

      This service user has all the necessary authorizations to access the required services on the addressed PI components.

Example

The Enterprise Services Repository is associated with service user PIREPUSER. Since the Enterprise Services Repository needs to communicate with the Integration Directory (for the cache refresh mechanism) and the System Landscape Directory (to obtain physical channel data), the user PIREPUSER needs to be known by each of these components.

For each component, service users representing the respective components are created with the appropriate roles in the target components during basic configuration. The passwords of the service users have to be defined during the basic configuration process.

The following table shows the created service users, together with the relevant component and their ABAP role.

Note

The names of the service users listed here are only samples created during basic configuration. They should be changed as required.

Service Users

Component

Service User Role

Service User (Created during Installation)

Exchange Profile, System Landscape Directory

SAP_BC_AI_LANDSCAPE_DB_RFC

PILDUSER

Enterprise Services Repository

SAP_XI_IR_SERV_USER_MAIN

SAP_SLD_CONFIGURATOR

PIREPUSER

Integration Directory

SAP_XI_ID_SERV_USER_MAIN

SAP_SLD_CONFIGURATOR

SAP_BC_WEBSERVICE_PI_CFG_SRV

PIDIRUSER

Advanced Adapter Engine

SAP_XI_AF_SERV_USER_MAIN

SAP_SLD_CONFIGURATOR

SAP_BC_WEBSERVICE_PI_CFG_SRV

PIAFUSER

Integration Server

SAP_XI_IS_SERV_USER_MAIN

SAP_SLD_CONFIGURATOR

PIISUSER

Runtime Workbench

SAP_XI_RWB_SERV_USER_MAIN

SAP_SLD_CONFIGURATOR

PIRWBUSER

Change Management Server

SAP_XI_CMS_SERV_USER

PILSADMIN

User for RFC communication between ABAP and Java

SAP_BC_JSF_COMMUNICATION_RO

PI_JCO_RFC

User for principal propagation

SAP_XI_APPL_SERV_USER

PIPPUSER

User for calling a Java Web service used to set up point-to-point connections

SAP_XI_CONFIGURATOR

SAP_XI_CONFIGURATOR_EXT_J2EE

PI3RDAPIUSER

For further details on these roles, call the Role Maintenance transaction (PFCG).

Note

This concept implies that all Advanced Adapter Engines of a PI landscape are represented by the same user PIAFUSER.

The next table shows users that must be available in the corresponding PI components.

Note

The Integration Server components include the Enterprise Services Repository, the Integration Directory, and the central Advanced Adapter Engine.

Service Users and Their PI Components

Service User

SLD

Integration Server Components

Non-Central Adapter Engine

PILDUSER

 

X

 

PIREPUSER

X

X

 

PIDIRUSER

X

X

X

PIAFUSER

X

X

 

PIISUSER

X

X

X

PIRWBUSER

X

X

X

PILSADMIN

 

X

 

 

End of Content Area