Communication Destinations
Find below an overview of the communication destinations used by SAP NetWeaver PI.
Destinations for Technical Communication
Destination |
Name |
Type |
User and Client |
Role |
Points from the Integration Server to the mapping runtime |
AI_RUNTIME_JCOSERVER |
T |
Anonym; can use SAP logon ticket; no client |
SAP_BC_JSF_COMMUNICATION_RO |
Required for the connection to the SLD and used to read the exchange profile |
LCRSAPRFC |
T |
Anonym; can use SAP logon ticket; no client |
SAP_BC_JSF_COMMUNICATION_RO |
Required for the connection to the SLD Bridge and used by the ABAP API |
SAPSLDAPI |
T |
Anonym; can use SAP logon ticket; no client |
SAP_BC_JSF_COMMUNICATION_RO |
Used for the cache update |
INTEGRATION_DIRECTORY_HMI |
H |
PIISUSER; client of Integration Server |
SAP_XI_IS_SERV_USER |
Destinations for Messaging
Destination |
Name |
Type |
User and Client |
Role |
Points from an application system to the associated Integration Server and is used for the XI and WS protocol as well as for the HTTP adapter |
User-defined with transaction SXMB_ADM → Integration Engine Configuration |
H |
Copy of PIAPPLUSER; client of Integration Server |
SAP_XI_APPL_SERV_USER SAP_BC_WEBSERVICE_CONSUMER SAP_BC_WEBSERVICE_PI_CFG_SRV |
Points from the Integration Server to the receiver system and is used for the XI and WS protocol as well as for the HTTP adapter |
User-defined in receiver channel in the Integration Directory |
H |
Copy of PIAPPLUSER; client of receiver system |
SAP_XI_APPL_SERV_USER or SAP_BC_WEBSERVICE_CONSUMER |
Points from a sender IDoc system to the Integration Server and is used for the IDoc adapter |
User-defined |
3 |
Copy of PIAPPLUSER; client of Integration Server |
SAP_XI_APPL_SERV_USER SAP_BC_WEBSERVICE_PI_CFG_SRV |
Points from the Integration Server to a receiver IDoc system and is used for the IDoc adapter |
User-defined in receiver channel in the Integration Directory |
3 |
Client of IDoc receiver system |
Authorization object B_ALE_RECV For non-unicode receivers, also authorization object S_RFC with ACTVT = 16, RFC_NAME = SCP5 and RFC_TYPE = FUGR |
Destinations for Monitoring
Destination |
Name |
Type |
User and Client |
Role |
Required for the Process Monitoring Infrastructure (PMI) and used for monitoring Advanced Adapter Engines on Java servers |
PMISTORE (Java EE destination on each Advanced Adapter Engine) |
HTTP |
PIRWBUSER; client of Integration Server |
SAP_XI_RWB_SERV_USER_MAIN |
Used for PMI monitoring on central monitoring server |
PMI* (one for each business system monitored with PMI) |
HTTP |
PIRWBUSER; client of Integration Server |
SAP_XI_RWB_SERV_USER_MAIN |
Used for GRMG scenarios like heartbeat and self test on central monitoring server |
User-defined with transaction GRMG using XI_* entries |
G |
PIRWBUSER; no client |
SAP_XI_RWB_SERV_USER_MAIN |
Destinations for Special Purposes
Destination |
Name |
Type |
User and Client |
Role |
Self-referencing destination used for principal propagation on Integration Server and on each business system with Integration Engine |
SAPXIPP<client> |
3 |
PIPPUSER; client of Integration Server or of business system with Integration Engine |
SAP_XI_IS_SERV_USER |
Points from an application system to the associated Integration Server and is used for receiver pre-identification and value mapping |
AI_INTEGRATION_SERVER |
3 |
Copy of PIAPPLUSER; client of Integration Server |
SAP_XI_APPL_SERV_USER |
Required for message-level security and used to call up Web service security services |
User-defined with transaction LPCONFIG, proxy class CO_WSSEWSSPROCESSOR_VI_DOCUMEN |
G |
PIISUSER; no client |
SAP_XI_IS_SERV_USER |
Used on the Integration Server for the retrieval of IDoc metadata |
User-defined with transaction IDX1 |
3 |
Client of IDoc system where metadata are kept |
As of SAP Release 6.20, role SAP_XI_IS_SERV_USER For SAP Releases 4.0A to 6.10, function groups SDTX and EDIMEXT For SAP Release 3.1H, function groups SDTX, EDI8, RFC1, and EDIT |