|Home • Trainings • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
ABAP Proxy Communication Scenario (Client Proxy)
By Neeraja Surapaneni, YASH PI Competency Core Team, YASH Technologies
This document is focused to give a better understanding on
ABAP client proxies.
From WAS 6.20 onwards, proxy generation feature enables
application systems to communicate with XI using proxies.
objects implement message interfaces from Integration Repository. Proxy
generation converts non-language-specific interface descriptions in WSDL into
executable interfaces in the application system. Proxies separate Business
Application logic from the integration logic of the Exchange infrastructure.
There are 2 types of proxies available.
1. Java Proxies:
- Java proxies are used when JAVA applications needs to send or receive messages
with other applications. JAVA proxies are generated from the WSDL description of
the interface in the Integration Repository, and the result is a .jar file
containing generated java classes corresponding to the integration objects.
2. ABAP Proxies:
- ABAP proxies are used when ABAP applications needs to send or receive
messages. ABAP proxies are generated on the Application server with transaction
SPROXY, based on the WSDL representation of the message interface.
The type of the message interface determines what type of
proxy is generated. The counterparts to outbound message interface in
application systems are client proxies,
these are called to send a message to inbound interface. And the counterparts of
inbound message interface in application systems are server proxies.
Advantages of ABAP
The rest of the document gives you pre-requisites and steps
that are necessary for generating and executing ABAP client proxies.
Also Read ABAP Proxy Communication (Server Proxy)
required for developing ABAP Proxies
a business scenario where in business (Source System) sends an Employee details
to their Payroll system for calculating the monthly salaries of their employees.
But here the source business is running on SAP R/3 and corresponding Payroll
system is not on SAP, hence the interpretation of data/communication is
different. Because source system sends employee information through proxy
communication and the target Payroll system is not aware of these proxy call, so
in order to provide a communication between these two we need some interface
mechanism which accepts proxy request and converts it into the format
understandable by the target payroll system and vice versa.
needed to be developed in IR
this scenario we need to create the corresponding Data types, Message types and
Message interfaces for source and target messages. Once the source Message
interface is created we can generate the interface in source R/3 system using
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards