Show TOC

Procedure documentationConfiguring a Consumer Proxy Locate this document in the navigation structure


You can configure individual service consumers by applying the configuration settings for each proxy definition. To configure a consumer proxy to access a particular service, you need to create and configure one or more logical ports.

A logical port references an endpoint, which is available at a unique location on the provider system. For this reason, a logical port is created based on the requirements of the provider.

A logical port is a reference to runtime configuration on the consumer system to access the service endpoint. You can create more than one logical port for the same consumer proxy definition. Each logical port can have only one runtime configuration, and points to only one endpoint.

You can create a logical port in two ways:

  • Based on the WSDL document for a service.

    The WSDL document describes how to access the endpoint, and includes the URLs for all the endpoints defined for a service.

    You need to know:

    • The URL that points to the WSDL document for the service

    • The access parameters for the WSDL document (alternatively, you have the WSDL document stored as a file)

  • Manually

    Here, a WSDL document is not available.

    You need to know:

    • The URL of the endpoint

    • The configuration settings that the provider expects


Creating a Logical Port
  1. From the main screen of the SOA Manager, go to the Application and Scenario Communication tab.

  2. Select Single Service Administration.

  3. Specify or search for a consumer proxy.

    More information: Generating a Consumer Proxy

    You can locate a consumer proxy from the Search or Browse tab.


    You can search for service definitions, consumer proxies, or ServiceGroups, using either the internal or external name, or both.

    Advanced search allows you to search by classification.

    You can display the objects for selected classifications and subclassifications sorted either by DPB (deployment unit, process component, business object) or SPB (software component, process component, business object).


    Display all the services or consumer proxies for a classification (DPB Group or SPB Group).

    Objects are displayed with their internal and external names, namespace, and type (deployment unit, process component, or business object).

  4. Select the consumer proxy from the overview and choose Apply Selection to display design-time information about the consumer proxy.

  5. Go to the Configurations tab.

  6. To create a new logical port, choose Create Logical Port.

    A dialog box is displayed.

  7. Specify a name for the new logical port.

    To make this logical port the default logical port, select Logical Port is Default. If a consumer application is not configured to call a specific logical port, it calls the default logical port.

  8. Select the configuration type.

    WSDL-Based Configuration

    The system extracts the endpoint URL from the WSDL document for the service.

    Specify the WSDL access settings. You have the following options:

    • Via HTTP access

      Specify the path to the WSDL document and a user and password.

    • Via File

      Specify a file for WSDL Access

    Manual Configuration

    The system uses a user-specified endpoint URL to create a logical port. You need to specify a unique name for the logical port.

    Process Integration Runtime

    A proxy call is made to an Integration Server running SAP NetWeaver XI 3.0. (The integration server must first have been configured.)

    No values can be configured here.

  9. Choose Apply Settings.

    The default settings for the logical port are displayed. In the next step, you can change the settings.

  10. Check the configuration.

    Some options may not be available or complete. For example, passwords.

    The following configuration options are available:

    Consumer Security

    User and password for authentication with the service provider


    Reliable Messaging (Asynchronous)

    Specify the protocol for reliable messaging.

    If only 1 protocol is supported, the protocol is preset.

    If no protocols are supported, the field is empty.

    Message ID (Synchronous)

    Each message needs an ID for two protocols, WS-A Message ID and SAP Message ID. Suppress ID transfer – This option is for older releases.

    Metering of Service Calls

    Determine the volume of data transferred and the protocol to use to transfer metering data.

    The service metering feature allows SAP NetWeaver components involved in the provisioning and consumption of Web services to collect information about which consumer components are consuming which Web services. The information collected in the SOA back-end systems can be read by SAP EarlyWatch and analyzed to optimize SOA scenarios and the enterprise services.

    The following options determine which fields data is transferred from:

    • Minimal Data Transfer

      The consumer application sends only Calling Application Type to the provider.

    • Basic Data Transfer

      The consumer application sends Calling Application Type, Calling Component, and Calling Application ID to the provider.

    • Enhanced Data Transfer

      The consumer application sends all the caller information attributes to the provider except Calling User Code.

    Caution Caution

    Increasing the service metering level may lead to a security risk. When you set the service metering level, you should therefore consider the trustworthiness of the Web service provider:

    End of the caution.

    Note Note

    Service metering information is currently not used on the provider side.

    End of the note.

    Transport Settings

    The settings for transport between the provider and the consumer. The settings here are stored together in the complete URL.

    Make Local Call: A local call is only used if processing is done within the same provider system. If local only calls are made, unnecessary steps, such as authentication, can be omitted.

    Maximum Wait for WS Consumer: The http timeout determines how long the consumer waits for a response from the provider. If you expect a high load on the provider system that would delay the responses to consumers, consider increasing the default value.

    0 seconds is infinite.

    Optimized XML Transfer: Determines the XML transfer between consumer and provider. If both the consumer and the provider are ABAP systems, you can select Binary XML to reduce the conversion overhead between these systems.

    Compress HTTP Message: Allows the consumer to send zip-compressed requests. This option is only of interest if you are expecting very large message sizes. For normal message sizes, the compression would take too long for there to be any benefit.

    Accept Compressed HTTP Message: Allows the provider to return zip-compressed responses to the consumer. This option is useful if you expect the provider to return data volumes of several MB in size.

    Operation specific

    Transport Binding

    Specify a SOAP action.

    Transport Security

    If the corresponding transport security options are defined in the WSDL document, on which the logical port is based, the permitted numbers of signed and encrypted message elements are displayed.

    WS Addressing

    Specify the protocol for Web service Addressing. A reference parameter is optional.

    If only 1 protocol is supported, the protocol is preset.

    If no protocols are supported, the field is empty.

  11. Save.

    The consumer proxy is now generated and configured.

Editing a Logical Port
  1. Go to the Application and Scenario Communication tab and select Single Service Administration.

  2. Specify a consumer proxy.

  3. Select the consumer proxy and choose Apply Selection to display more design-time information.

  4. To edit a logical port, select it and choose Edit.

  5. Specify the settings that you require.

    For more information about the configuration options, refer to Creating a Logical Port above.

  6. Save.