Professional Documents
Culture Documents
ABAP Proxy and PI PDF
ABAP Proxy and PI PDF
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
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.
Vikas Jain , LNT Infotech, Wiki on SDN
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
Http 400: - ICM_HTTP_CONNECTION_FAILED .........................................................................................17
Http 401: - HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized....................................................19
Http 403: - Forbidden ....................................................................................................................................19
Http 404: - HTTP_RESP_STATUS_CODE_NOT_OK 404 ..........................................................................20
Related Content................................................................................................................................................20
Disclaimer and Liability Notice..........................................................................................................................21
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
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.
Host name.
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.
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).
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)
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.
1. Goto SM59
2. Create new RFC destination of type T(TCP/IP connection).
3. Give the rfc name as SAPSLDAPI and description as PI71 SLD connection
4. Goto Technical Settings tab and check the radio button Registered Server program
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)
Purpose Of SLDAPICUST
Next Execute transaction SLDAPICUST to maintain the SLD access data.
This transaction is used for logging onto SLD using a browser.
7. Password: Password of PI
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.
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.
Test Connection. Connection test should return the HTTP response code as shown in the screenshot below.
Settings in SXMB_ADM.
Goto SXMB_ADM (On application system) and open Integration engine configuration
1. Goto Edit->change global configuration and give the RFC dest name like this: -
2. Corresponding Integration server: - dest:// PI_INTEGRATIONSERVER(This is the destination
created in the above step).
3. Also Role of Business system should be kept as Application system(its mandatory)
And then save it.
Select the checkbox for HTTP, and then ->Activate. This activates the http service
Check the dev_icm trace file of ICM monitor and see whether there are any errors.
Related Content
http://help.sap.com/saphelp_nw04/helpdata/en/3e/a35c3cff8ca92be10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/be/6e0f41218ff023e10000000a155106/frameset.htm
For more information, visit the SOA Management homepage.