Destinations for Technical Communication

Use

The following destinations are relevant for technical communication between the involved Process Integration components.

Name	Description	Destination Target	Type
AI_RUNTIME_JCOSERVER	Points from the Integration Server to mapping runtime. Needs to be created on the system of the Integration Server (system with the same SAP system ID (SID) as the Integration Server) with both transaction SM59 (AS ABAP) and the SAP NetWeaver Administrator (AS Java). More information: Create Destinations on the Java Server	No client to be specified Logon and security: Anonym; can use SAP logon ticket	T
AI_VALIDATION_JCOSERVER	Points from the Integration Server to the XML validation service. The program ID corresponds to the entry configured for the destination on AS Java (used for XML validation). Needs to be created on the system of the Integration Server with both transaction SM59 (AS ABAP) and the SAP NetWeaver Administrator (AS Java). More information: Create Destinations on the Java Server	No client to be specified	T
LCRSAPRFC	Required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile. Needs to be created on the system of the Integration Server with both transaction SM59 (AS ABAP) and the SAP NetWeaver Administrator (AS Java). More information: Create Destinations on the Java Server	No client to be specified Logon and security: Anonym; can use SAP logon ticket	T
INTEGRATION_DIRECTORY_HMI	Used for the cache update (for business systems that communicate using the web services runtime). Needs to be maintained in the business system (based on AS ABAP). More information: Technical Communication under Cache Notification for Business Systems in the Web Services Runtime Configuring Business Systems (with Web Service Communication) Create Destinations on the ABAP Server	Client of Integration Server Logon and security: PIISUSER	H
XI_EXCHANGE_PROFILE	Defines the communication between the Java-based exchange profile user interface and the exchange profile table on the Integration Server (see figure below). Has to be maintained on the AS Java-based part of the SAP PI installation. It is recommended to secure the destination by applying SNC (Secure Network Connection). More information: Configuring SNC: AS Java ( AS ABAP	Logon and security: use PILDUSER as logon user.	RFC
SAP_PROXY_ESR	Enables business system to access ES Repository data. This is a prerequisite for proxy generation in the business system. Has to be maintained in the business system (based on AS ABAP). More information: Connecting ABAP Backend System to ES Repository	Logon and security: Basic Authentication	G
SAPXICACHE_<client>	Used for principal propagation. Needs to be maintained on the AS ABAP-based part of the SAP PI installation. More information: Create Destinations on the ABAP Server	Logon and security: PICACHEUSER	3
SAPXIPP<client>	Self-referencing destination used for principal propagation on Integration Server and on each business system with Integration Engine. More information: Create Destinations on the ABAP Server	Client of Integration Server or of business system with Integration Engine Logon and security: PIPPUSER	3
AI_INTEGRATION_SERVER	Points from a business system (based on AS ABAP) to the associated Integration Server and is used for receiver pre-identification and value mapping. More information: Creating Optional Destinations	Client of Integration Server Logon and security: Copy of PIAPPLUSER	3
User-defined with transaction LPCONFIG, proxy class CO_WSSEWSSPROCESSOR_VI_DOCUMEN	Required for message-level security and used to call up Web service security services. Needs to be maintained in the business system (based on AS ABAP). More information: Configuring Web Service Security in AS ABAP	No client to be specified Logon and security: PIISUSER	G

The following figure shows the communication paths specified by selected destinations listed above.

Selected Destinations for Technical Communication (Without SLD)

Communication With System Landscape Directory

The following destinations are relevant in particular for communication with the System Landscape Directory (SLD).

Name	Description	Destination Target	Type
SLD_DataSupplier	Used by a business system to provide data to the SLD. Needs to be maintained on the system of the Integration Server (AS ABAP and AS Java). More information: Setting Up the SLD Data Supplier for AS ABAP-Based Systems Setting Up the SLD Data Supplier for AS Java-Based Systems	SLD	HTTP
SAPSLDAPI	Used by the AS ABAP-based part of an SAP PI system (Integration Server) to provide data to the SLD via the SLD API. Needs to be created on the system of the Integration Server with both transaction SM59 (AS ABAP) and the SAP NetWeaver Administrator (AS Java). More information: Using SLD API for AS ABAP-Based Systems Create Destinations on the Java Server Creating an RFC Destination for the SLD ABAP API on the AS ABAP Creating an RFC Destination for the SLD ABAP API on the Java Sid	SLD Logon and security: Anonym; can use SAP logon ticket	T
SLD_Client	Used by a business system (as SLD client) to access the SLD. Needs to be maintained on the system of the Integration Server (AS ABAP and AS Java). More information: Configuring the SLD Client	SLD	HTTP

The following figure shows how the destinations SLD_DataSupplier and SAPSLDAPI are used in a PI landscape.

PI Landscape Showing the Communication With SLD

More Information

Technical Communication .
Connection Types (contains information in destination types in AS ABAP)