ABAP Proxy Generation
|
ABAP |
Java |
Use
Using ABAP the proxy generation function (transaction SPROXY) you can generate ABAP proxy objects in an SAP system from an interface description in the Integration Repository.
Prerequisites
ABAP proxy objects can only be generated for an SAP system for which SAP Exchange Infrastructure Add-On 2.0 has been installed.The proxy generation functions fetch the WSDL description of the interface from the Integration Repository, using HTTP. The address of the corresponding server is taken from the exchange profile (parameter 1, 2, and 3. See below). Queries to the repository undergo an authentication procedure. User and password for these queries are also taken from the exchange profile (parameter 5 and 6). Information from the exchange profile (parameters 1, 2, and 4) is also required to navigate from transaction SPROXY to the Integration Builder start page.
Example Configuration for Accessing Interfaces in the Integration Repository (Exchange Profile)
|
Nr. |
Section |
Parameter |
Value (Example) |
|
1 |
Connections |
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 XI system landscape.
You must also have created interfaces in the interface maintenance of the Integration Repository before you can generate for these proxies.
Features
The system displays a navigation tree when you call transaction
SPROXY. In the tree you can view the interface objects from the Integration Repository. If no connection to the Integration Repository exists, the tree presents an overview of those interface objects for which a proxy object already exists in the system. You can display or generate objects from the context menu in the navigation tree. The system displays the properties of the proxy objects on the right-hand side of the screen:Tab Pages for Transaction SPROXY
|
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. |
|
Problems |
The system only displays this tab page directly after generation. You can correct the names of labels that had to be abbreviated, or due to a naming conflict, had to be changed during generation. |
|
Generation |
All objects generated for the object as a list. |
|
Structure |
Similar to generation, except that here objects are ordered in a tree structure according to their use. ->Method MYMETHOD ->Importing OUTPUT |
|
Documentation |
The system displays the documentation from the Integration Repository for the outbound object. |
|
Warning Messages |
Even if proxy generation was successful, there may be cases where generation was only possible on the basis of implicit assumptions (for example, restrictions to the value range are checked by the programmer). If cases such as these occur during generation, the system lists them in an application log. |
Navigation Tree Views
Default
The navigation tree only displays those software component versions for SAP components that are available locally in the system. The selection of software component versions in the tree is therefore a subset of the software component versions in the Integration Repository.
While all imported CRM, ABA or APO software component versions are displayed in the Integration Builder, the SAP system has the corresponding components of a particular version, for example ABA 6.20 and CRM 3.0. For this reason, only these software component versions are displayed in the navigation tree.
Displaying Namespaces Known in the System
Transaction SPROXY structures the default navigation tree using information from the Integration Repository. If namespaces are deleted in the Integration Repository then they are no longer visible in the navigation tree in transaction SPROXY, however it is possible that proxy objects already exist in the system for these namespaces. To display these proxy objects, choose Goto ® View ® Only Local Objects and display all namespaces for which ABAP proxy generation has ever generated proxy objects. Even proxy objects that have already been deleted in the Integration Repository are visible. To return to the default setting, choose Goto ® View ® All Objects.
Activities