Start of Content Area

Function documentation ABAP Proxy Generation  Locate the document in its SAP Library structure

ABAP

Java

Use

Using ABAP the proxy generation function you can generate ABAP proxy objects to an SAP system from an interface description in the SAP Exchange Infrastructure Integration Repository.

Prerequisites

ABAP proxy objects can only be generated for SAP systems that are based on SAP Web Application Server 6.40.

The proxy generation retrieves the WSDL description of the interface from the Integration 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 used to navigate from the ABAP Proxy Generation to the initial page of the Integration Builder is also taken from the exchange profile (parameters 1, 2, and 4).

Example configuration for accessing
interfaces in the Integration Repository (exchange profile)

No.

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

Note

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 message interfaces in the interface maintenance of the Integration Repository before you can generate for these proxies.

Integration

You can send and receive messages using the generated ABAP proxies. (See ABAP Proxy Runtime.)

Features

You can edit ABAP proxy objects either in the Object Navigator (transaction SE80) or in transaction SPROXY:

        The Object Navigator displays proxy objects created in the system in the navigation tree under Enterprise Services Web Service Library (client proxies, server proxies, and proxy Dictionary-objects). When you create new proxy objects, the hierarchy of software component versions from the Integration Repository is displayed in a dialog box.

        You can display the interface objects from the Integration Repository by using the navigation tree in transaction SPROXY. 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.

Both transactions show the following information on the right-hand side:

Tabs displayed when generating an ABAP proxy

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.
Example:
  Class
CO_X
    ->
Method MYMETHOD
      ->
Importing OUTPUT

Documentation

The system displays the documentation from the Integration Repository for the outbound 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.

Accessing Interface Objects

Object

SE80

SPROXY

Generated Objects

Navigation tree in object navigator

Navigation tree in transaction SPROXY

Integration Repository Objects

Popup with hierarchy of software component versions

Navigation tree in transaction SPROXY

Software component versions and namespaces of the Integration Repository are only displayed if they are available locally in the system. The selection of software component versions in the navigation tree in the SPROXY or SE80 dialogs is also a subset of the software component versions of the Integration Repository.

Example

All imported software component versions in CRM, ABA, or APO are displayed in the Integration Builder. Conversely, only the appropriate components of a particular version are installed in the SAP System (such as ABA 6.20 or CRM 3.0). Therefore, only these software component versions are offered.

Views in Transaction SPROXY

In transaction SPROXY, you access both Integration Repository objects and generated objects by using the navigation tree. If namespaces are deleted there, 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. For this reason, the navigation tree in transaction SPROXY has two views:

Proxy-Objects View (Menu Goto View)

View

Meaning

All Generated Objects

You can access all proxy objects that have ever been created in the system. You only require this view if namespaces or software component versions have been deleted in the Integration Repository. All generated objects are displayed in the navigation tree in transaction SE80.

Integration Repository Objects

(Default Setting)

You can access all interface objects that are currently visible in the Integration Repository, as well as the corresponding proxy objects.

Activities

...

       1.      Generate ABAP proxy objects for an interface or for other interface objects (see: Generating Proxies).

Note

If a connection to the Integration 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.

 

 

 

 

End of Content Area