|Home • Trainings •Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
ABAP Proxy communication (Server Proxy)
By Suraj Kumar Pabbathi, PI Competency Lead, YASH Technologies
Proxy objects implement message interfaces from Integration
Repository. Proxies are executable interfaces, which converts
non-language-specific interface descriptions into WSDL. i.e., you use proxies to
implement the actual message exchange that is described in the Integration
Types of Proxy objects: You can use message interfaces to create the following proxy objects:
During the process of ABAP proxy generation, it gets WSDL
(Web Service Description Language) description of message interfaces from the
Integration Repository by using HTTP communication.
As part of SAP Web AS 6.40
prerequisites to configure ABAP Proxy include: (landscape dependent)
required on the Business System:
Create a HTTP connection in the business system using transaction
Connection Type: H
Target Host: System name
Service Number: HTTP Port name
Path Prefix: /sap/XI/engine/?type=entry
On the Logon/Security tab page, enter the following logon data:
User: XIAPPLUSER (for example); this user should represent the
sending business system (see also the SAP XI Security Guide under Service Users
for Message Exchange).
Password: the password you have specified for this user
Client: SAP XI Integration server
Language: Language required
Configuration Business system as local Integration Engine.
1. Go to Transaction SXMB_ADM
2. Choose Edit --> Change Global Configuration Data.
3. Select Role of Business System: Application system
4. Corresponding Integration server: dest://<HTTPDESTINATION>. Here <HTTPDESTINATION> XI_XIR_CONNECTION created in step 1. Dest://XI_XIR_CONNECTION.
5. Under Specific Configuration Data you can specify additional configuration data
3. Connection between Business System and System Landscape Directory
Maintaining the SAP J2EE Connection Parameters for LCRSAPRFC and
SAPSLDAPI in SAP J2EE engine
Maintain SLD access details in Transaction SLDAPICUST
there is an HTTP error during connection, check the error using the transaction
SLDCHECK in the Business system. Also ensure that HTTP connection is working
In XI Adapter use HTTP connection rather than giving R/3 input details, as this is easier to transport and for maintenance. One receiver adapter can be used for all Interfaces connecting to a Business system.
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