Internal Communication: ABAP Proxy and Process Integration

21 Pages·2009·0.31 MB·English

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.
Vikas Jain , LNT Infotech, Wiki on SDN

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 1
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
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

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 2
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.

Host name.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 3
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.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 4
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).

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 5
Internal Communication: ABAP Proxy and Process Integration
1. Create new RFC destination of type T (TCP/IP connection).
2. Give the rfc name as LCRSAPRFC and description as PI71 SLD connection
3. Goto Technical Settings tab and check the radio button Registered Server program

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 6
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)

5. And then save it. Test the connection
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 7
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.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 8
Internal Communication: ABAP Proxy and Process Integration
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
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 9
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.

Goto transaction SLDAPICUST
1. Switch to change mode and click on create
2. Specify the Alias name as: SAP_CONFIG
3. Tick the checkbox PRIM
4. Host Name: IP address of PI system
5. Port: Java port of PI system
6. User Name: user id of PI system
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com
© 2009 SAP AG 10