ABAP Proxy
Generation
Use
ABAP proxy generation generates ABAP proxy objects in an SAP system from an interface description in the Enterprise Services (ES) Repository.
Prerequisites
The proxy generation process retrieves the WSDL description of the interface from the ES Repository using HTTP. The address of the appropriate server is taken from the exchange profile (parameters 1, 2, and 3 – see below). Queries to the Repository are subject to authentication. The user and password for these queries are also taken from here (parameters 5 and 6). Information is also taken from the exchange profile to navigate from ABAP proxy generation to the Enterprise Services (ES) Builder start page (parameters 1, 2, and 4).
Example Configuration for Accessing
Interfaces in the ES Repository (Exchange Profile)
No. |
Section |
Parameter |
Value (Example) |
1 |
com.sap.aii.connect.repository.name |
pwdf0436 |
|
2 |
Connections |
com.sap.aii.connect.repository.httpport |
1080 |
3 |
Connections |
com.sap.aii.connect.repository.contextRoot |
rep |
4 |
Connections |
com.sap.aii.connect.integrationbuilder.startpage.url |
rep/start/index.jsp |
5 |
ApplicationSystem |
com.sap.aii.applicationsystem.serviceuser.name |
hugo |
6 |
ApplicationSystem |
com.sap.aii.applicationsystem.serviceuser.pwd |
hugopass |
These parameters are not to be set by developers but by the administrator responsible for the technical configuration of the PI system landscape.
You
must also have created a service interface (refer to
Developing Service Interfaces) in the interface maintenance of
the ES Repository.
Features
You can edit ABAP proxy objects in the Object Navigator (transaction SE80):
● The Object Navigator displays proxy objects created in the system in the navigation tree under Enterprise Services →Service Consumer. When you create new proxy objects, the hierarchy of software component versions from the ES Repository is displayed in a dialog box.
Tabs Pages of ABAP Proxy Generation
Tab Page |
Meaning |
Properties |
Generation attributes such as package, last changed by, and so on. For inbound proxies, specify the name of the implementing class here. |
Name conflicts |
This tab is only displayed immediately after the proxy is generated. It allows you to correct names that were truncated during generation, or that needed to be changed because a collision occurred. |
Generation |
A list of all the objects generated for an object |
Structure |
This
tab is similar to the Generation tab, except that here the objects are
sorted according to their use in a tree structure. |
Documentation |
The system displays the documentation from the Integration Repository for the source object. |
Type mappings |
Even if a proxy was generated successfully, there are cases when generation was only possible due to implicit acceptance (for example, restrictions to the value range are checked by the programmer). If such situations arose during generation, they are listed in an application log. |
Activities
...
1. Generate ABAP proxy objects for an interface or for other interface objects (see: Generating Proxies).
If a connection to the Repository could not be established at the start of the transaction, you can ascertain more exactly what went wrong, and fix this problem (or have it fixed), by choosing Goto → Connection Test.
2. Check whether you need to make any changes following the automatic naming of proxy objects.
3. If the description was changed in the Integration Repository, you must regenerate the proxy objects.