ABAP Proxy and PI

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 © 2009 SAP AG

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

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

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

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

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

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

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

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

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

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 10

Internal Communication: ABAP Proxy and Process Integration

7. Password: Password of PI

After making all these settings. Execute transaction SLDCHECK. Following screen will be displayed.

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 11

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.

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 12

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.

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 13

Internal Communication: ABAP Proxy and Process Integration

3. Target Host: IP address of PI system Path prefix: /sap/XI/engine/? type=entry

4. Goto Logon/Security tab and specify the following details 5. Client: 300 6. Username: Service user of Integration engine (maintained in Exchange profile)

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 14

Internal Communication: ABAP Proxy and Process Integration

7. Password: Service password of Integration engine ((maintained in Exchange profile)

Test Connection. Connection test should return the HTTP response code as shown in the screenshot below.

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 15

Internal Communication: ABAP Proxy and Process Integration

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.

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 16

Internal Communication: ABAP Proxy and Process Integration

Issues in Proxy Configuration Following are the list of errors and their solutions. Http 400: - ICM_HTTP_CONNECTION_FAILED Check whether the ICM is running and the HTTP port is active in transaction SMICM. Execute transaction SMICM.Check whether ICM status is running and a green light is shown beside it. Then GOTO services.

Select the checkbox for HTTP, and then ->Activate. This activates the http service

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 17

Internal Communication: ABAP Proxy and Process Integration

Check the dev_icm trace file of ICM monitor and see whether there are any errors.

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 18

Internal Communication: ABAP Proxy and Process Integration

Http 401: - HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized. 1. Check whether service user maintained in the SM59 destination is with Roles of std. user PIAPPLUSER, PIISUSER) 2. Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER 3. May be wrong password for user PIISUSER Http 403: - Forbidden 1. Path sap/xi/engine not active 2. Activate the service engine in transaction SICF as shown in the screenshot below

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 19

Internal Communication: ABAP Proxy and Process Integration

Http 404: - HTTP_RESP_STATUS_CODE_NOT_OK 404 1. Check whether the ICM server is running in transaction SMICM 2. Also check whether the port specified in the RFC destination is the ICM HTTP port and not the JAVA port and check whether the service is active.

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.

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 20

Internal Communication: ABAP Proxy and Process Integration

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.

SAP COMMUNITY NETWORK © 2009 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 21