This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Internal Communication: ABAP Proxy and Process Integration
Applies to: Exchange Infrastructure. For more information, visit the Service Bus-based Integration homepage.
Summary Purpose of this article is to explain the significance of ABAP proxy configurations and also to explain the internal communication between the application systems and PI
Authors: Vikas Jain, Milan Thaker
Company: LNT InfoTech
Created on: 05 January 2009
Author Bio Milan Thaker, LNT InfoTech: Blogs on SDN Topics: Delivery modes of BPM, Transactional behavior of BPM, Block steps of BPM, Correlation in BPM.
Internal Communication: ABAP Proxy and Process Integration
Table of Contents Introduction .........................................................................................................................................................3 Concept: Internal Communication of PI..............................................................................................................3 Purpose of LCRSAPRFC:...................................................................................................................................3 Purpose of SAPSLDAPI .....................................................................................................................................8 Purpose Of SLDAPICUST................................................................................................................................10 Purpose of PI_INTEGRATIONSERVER ..........................................................................................................13 Issues in Proxy Configuration: ..........................................................................................................................17
Related Content................................................................................................................................................20 Disclaimer and Liability Notice..........................................................................................................................21
Internal Communication: ABAP Proxy and Process Integration
Introduction ABAP Proxy is one of the most remarkable forms of communication between SAP application system and SAP PI. Proxy provides both asynchronous and synchronous mode of communication. In order to utilize Proxy the application system should have WAS > 6.20. Proxies are used to connect the application system to the PI system. The role of Business system at the application side is LOC Application system and that at the PI side is HUB Integration server.
Following configurations are required on the application side to enable the proxy connection: -
1. TCP\IP connections
1.1. LCRSAPRFC
1.2. SAPSLDAPI
2. Settings are to be done in SLDAPICUST transaction
3. Http Connection: -
3.1. PI_INTEGRATIONSERVER
Concept: Internal Communication of PI The standard way in which one PI component connects to another is that the component that wants to establish a connection (the source component) gets its own specific username and password from the Exchange Profile and the host and port for the target to connect to either from the Exchange Profile or the SLD. If, for example, the Integration Server tries to setup a connection to the Adapter Engine it gets the integration server service user and password from Exchange Profile (EP) and the host and port of the adapter engine from the SLD.
Purpose of LCRSAPRFC: In order to get the interface details in SPROXY transaction, the application server needs to connect to integration repository. To connect to Integration repository, application system needs to fetch the host name and port from the exchange profile (i.e. the connection parameters for IR). Go to Exchange profile -> Connections. You will find the connection parameters for all the PI components. The figure below shows the connection parameters for repository. It includes hostname, port and context root.
Internal Communication: ABAP Proxy and Process Integration
Http port.
Context name.
Once the application system gets the connection parameters, it requires the authentication to login into the repository. The user name and password to login into repository is stored in the Application System node of exchange profile.
Internal Communication: ABAP Proxy and Process Integration
In order to obtain these connection and authentication parameters, application system needs to access the exchange profile. To connect to the EP, we need to configure LCRSAPRFC connection (i.e. type t connection on the application system).
Internal Communication: ABAP Proxy and Process Integration
4. Specify the Program Id: LCRSAPRFC_PIC (This program ID should match the program id maintained in the JAVA Stack of PI as shown in the below screenshot)
Internal Communication: ABAP Proxy and Process Integration
Purpose of SAPSLDAPI To connect to SLD and get the respective business system name maintained in SLD, application system uses a T type of connection, which is to be maintained in SM59 i.e. SAPSLDAPI and the data in transaction SLDAPICUST to get connection and own landscape data.
Internal Communication: ABAP Proxy and Process Integration
5. Specify the Program Id: SAPSLDAPI _PIC (This program ID should match the program id maintained in the JAVA Stack of PI as shown in the below screenshot)
6. and then Save it. Test the connection.
Purpose Of SLDAPICUST Next Execute transaction SLDAPICUST to maintain the SLD access data.
This transaction is used for logging onto SLD using a browser.
Internal Communication: ABAP Proxy and Process Integration
As shown in the above screen shot, RFC destination SAPSLDAPI gets all the business systems, which are maintained in the SLD, by calling function LCR_LIST_BUSINESS_SYSTEMS.
In the next function call, it identifies its own business system.
The reason behind getting the business systems is that whenever an XI message is sent to the integration engine via adapter engine, adapter engine specifies the business system name in the xml message. But in case of proxy since there is no processing in adapter engine involved and application system itself sends the message to integration engine, it needs to specify the name of business system and hence the RFC destination SAPSLDAPI is required.
Internal Communication: ABAP Proxy and Process Integration
Purpose of PI_INTEGRATIONSERVER Create a destination of type H in transaction SM59.This connection is used to send the message to the Integration server
Goto SM59.
Create new RFC destination of type H (HTTP connection to ABAP system).
1. Give the rfc name as PI_INTEGRATIONSERVER and description as P70 Connection
2. Goto Technical settings tab and specify the following details.
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.