ABAP Proxies in XI(Client Proxy)

[Former Member]

ABAP Proxies in XI(Client Proxy)

The other way of interfacing XI is through proxies. From WAS 6.20, proxy generation feature enables application systems to communicate with XI using proxies. Proxy generation enables you to create proxies in application systems. Proxies encapsulate the creation or parsing of XML messages and the communication with the relevant runtime components required to send or receive the messages.



There are two types of Proxies.

1. Java Proxies.
2. ABAP Proxies.

Java proxies are used when java applications needs to send and receive data and ABAP proxies are used when ABAP applications needs to send and receive data. I am going to demonstrate a simple client proxy which sends the employee data to XI and it routes the information to a file.

We use two clients of XI here. Client 100 acts as XI server .Client 105 acts as a client ABAP proxy which sends employee information as a message to XI which routes the info to a file. Logical flow is depicted as shown below. Note that conversion of sending system format to XI specific format is not done at the outbound side of the XI server.

Demonstration of ABAP Proxy

Necessary integration repository objects are developed at the design time. The out bound client proxy message interface and message type is depicted as shown below.





After the message interface is developed in the integration repository, proxy is generated on the client 100 using SPROXY transaction. SPROXY transaction lists all the message interfaces in the integration repository. We have to choose our message interface Proxy_Interface_OB and click Create.



ABAP proxy will generate 3 objects :

1. ABAP Class ( ZBLOGCO_ Proxy_Interface_OB).

2. Structure for the message type in ABAP Data Dictionary (ZBLOGEMP_PROFILE_MSG).

3. Structure for the data type in ABAP Data Dictionary (ZBLOGEMP_PROFILE_DT).



Once the proxy objects are activated we can check the ZBLOGCO_Proxy_Interface_OB in the SE24 editor. Since the proxy message interface is asynchronous the ZBLOGCO_ Proxy_Interface_OB has EXECUTE_ASYNCHRONOUS and message type ZBLOGEMP_PROFILE_MSG as the importing parameter. With this proxy generation is over.









We need to develop an ABAP Report in 100 client to trigger a client proxy. The following report is executed in the SE38 Editor for triggering an ABAP Proxy request from client 105.

*&---------------------------------------------------------------------**& Report  ZBLOG_ABAP_PROXY*&*&---------------------------------------------------------------------**&*&*&---------------------------------------------------------------------*REPORT  zblog_abap_proxy.DATA prxy TYPE REF TO zblogco_proxy_interface_ob.*CREATE OBJECT prxy.DATA it TYPE  zblogemp_profile_msg.TRY.    it-emp_profile_msg-emp_name = 'Sravya'.    it-emp_profile_msg-empno = '80101'.    it-emp_profile_msg-DEPARTMENT_NAME = 'NetWeaver'.    CALL METHOD prxy->execute_asynchronous      EXPORTING        output = it.     commit work    .  CATCH cx_ai_system_fault .    DATA fault TYPE REF TO cx_ai_system_fault .    CREATE OBJECT fault.    WRITE <span class="lia-unicode-emoji" title=":confused_face:">😕</span> fault->errortext.ENDTRY.

Receiver adapter configurations should be done in the integration directory and the necessary sender/receiver binding should be appropriately configured. We need not do any sender adapter configurations as we are using proxies.

Triggering ABAP Proxy

We can trigger the ABAP proxy by logging into client 105 of XI server and executing the ABAP report through SE38 editor. Once the report is executed we can see the file on the XI server and contents of file by double clicking the file.





I hope this blog will be useful for trying out real time applications on ABAP Proxies.