Abap Proxy

ABAP Proxy communication (Server Proxy)
Sources http://www.saptechnical.com/Tutorials/XI/ABAPProxy/page1.htm Wikipedia for WSDL details
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 Builder. Types of Proxy objects: You can use message interfaces to create the following proxy objects:

ABAP Proxy objects JAVA 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.
Proxy Generation: As part of SAP Web AS 6.40

ABAP proxy generation enables you to generate proxies to communicate by using the Web service infrastructure and by using SAP Exchange Infrastructure ABAP proxies that were generated from message interfaces in the Integration Repository (IR) can be used in both infrastructures. This means that if none of the Integration Server services are available for a proxy-to-proxy communication scenario in ABAP, you can use a point-to-point connection using the Web service infrastructure instead.
The prerequisites to configure ABAP Proxy include: (landscape dependent)

1. 2. 3.
The business systems should be based on SAP Web AS 6.20 and SAP Web AS 6.20 kernel patch level above 1253 You have installed the XI Add-On in each of these business systems as described in the Installation Guide SAP Exchange Infrastructure 3.0 The business systems and your central Integration Server are maintained in the System Landscape Directory (SLD).
Configuration required on the (Majority of these are done by our BASIS/Security team)
1.
Business
System:
Create a HTTP connection in the business system using transaction SM59 Technical Setting: Connection Type: H
Target Host: System name Service Number: HTTP Port name Path Prefix: /sap/XI/engine/?type=entry
Logon Security
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
2.
Configuration Business system as local Integration Engine.

1. 2. 3. 4. Go to Transaction SXMB_ADM Choose Edit --> Change Global Configuration Data. Select Role of Business System: Application system Corresponding Integration server: dest://<HTTPDESTINATION>. <HTTPDESTINATION> XI_XIR_CONNECTION created in step Dest://XI_XIR_CONNECTION. Under Specific Configuration Data you can specify additional configuration data Here 1.
5.
Select the relevant category under Specific Configuration Data. Choose Change Specific Configuration Data. For ABAP Proxies, Add the following configuration: 1.Category RUNTIME 2.Parameters: IS_URL 3.Current Value: dest://XI_XIR_CONNECTION
3.
Connection between Business System and System Landscape Directory

Create RFC destination (TCP/IP) LCRSAPRFC and SAPSLDAPI for the SLD connection. To create RFC Destination: LCRSAPRFC o Connection Type: T o Choose the Technical settings tab page and do the following: In the Program ID field under Registered Server Program, enter LCRSAPRFC This program ID must correspond to a program ID specified in the RFC engine settings of the SAP J2EE Engine on the Integration Server host. Repeat the above step for RFC destination for SAPSLDAPI
4.
Maintaining the SAP J2EE Connection Parameters for LCRSAPRFC and SAPSLDAPI in
SAP J2EE engine
5.
Goto J2EE Engine Choose Cluster --> Server --> Services. JCo RFC provider Under RFC destination specify the following: Program ID: LCRSAPRFC Gateway Host: <Integration Server host> Gateway Service: <Integration Server gateway service> Number of process: 3 Under Repository specify the following: Application Server: <Integration Server host>
Maintain SLD access details in Transaction SLDAPICUST
If 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 fine.
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.
WSDL
WSDL is an XML-based language for describing Web services and how to access them.
What is WSDL?
WSDL WSDL WSDL WSDL WSDL WSDL stands for Web Services Description Language is written in XML is an XML document is used to describe Web services is also used to locate Web services is not yet a W3C standard
WSDL Describes Web Services

WSDL stands for Web Services Description Language. WSDL is a document written in XML. The document describes a Web service. It specifies the location of the service and the operations (or methods) the service exposes. A WSDL document is just a simple XML document. It contains set of definitions to describe a web service.
The WSDL Document Structure

A WSDL document describes a web service using these major elements: Element <portType> <message> <types> <binding> Defines The operations performed by the web service The messages used by the web service The data types used by the web service The communication protocols used by the web service
The main structure of a WSDL document looks like this:
<definitions> <types> definition of types........ </types> <message> definition of a message.... </message> <portType> definition of a port....... </portType> <binding> definition of a binding.... </binding>
</definitions>
A WSDL document can also contain other elements, like extension elements and a service element that makes it possible to group together the definitions of several web services in one single WSDL document.
WSDL Example
This is a simplified fraction of a WSDL document:
<message name="getTermRequest"> <part name="term" type="xs:string"/> </message> <message name="getTermResponse"> <part name="value" type="xs:string"/> </message> <portType name="glossaryTerms"> <operation name="getTerm"> <input message="getTermRequest"/> <output message="getTermResponse"/> </operation> </portType>
In this example the <portType> element defines "glossaryTerms" as the name of a port, and "getTerm" as the name of an operation. The "getTerm" operation has an input message called "getTermRequest" and an output message called "getTermResponse". The <message> elements define the parts of each message and the associated data types. Compared to traditional programming, glossaryTerms is a function library, "getTerm" is a function with "getTermRequest" as the input parameter and getTermResponse as the return parameter.

Abap Proxy

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Abap Proxy

Uploaded by

Copyright:

Available Formats

ABAP Proxy communication (Server Proxy)

Sources http://www.saptechnical.com/Tutorials/XI/ABAPProxy/page1.htm Wikipedia for WSDL details

Proxy Generation: As part of SAP Web AS 6.40

The prerequisites to configure ABAP Proxy include: (landscape dependent)

Configuration Business system as local Integration Engine.

Connection between Business System and System Landscape Directory

Maintain SLD access details in Transaction SLDAPICUST

WSDL Describes Web Services

The WSDL Document Structure

The main structure of a WSDL document looks like this:

You might also like