Show TOC

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

 

To configure a consumer proxy to access a particular service, you need to create and configure one or more logical ports.

A logical port is created for a specific consumer proxy to access one particular binding on the provider system. You can create more than one logical port for the same consumer proxy. However, each logical port can point to only one binding.

You can create a logical port in two ways:

You can create a logical port based on a WSDL document or manually. Depending on the way you choose to create a logical port, you need the following information:

Method to Create a Logical Port

What You Need to Know

Based on the WSDL document for a service

  • The URL that points to the WSDL document for the service. This is the URL for the binding that was generated for the Web service provider.

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

Manually If a WSDL document is not available, you need to create a logical port manually.

  • The URL of the binding

  • The configuration settings that the provider expects

Procedure

Creating a Logical Port
  1. From the main screen of SOA Manager, go to the Service Administration tab.

  2. Select Web Service Configuration.

  3. Specify or search for a consumer proxy.

    More information:

    Generating a Consumer Proxy

  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.

    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 binding 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 binding 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.

    The following configuration options are available:

    Consumer Security

    User and password for authentication with the service provider

    Event Provider Settings

    This tab displays an overview of the operations and messages for the proxy.

    Operations for specially created event proxies can be service enabled to allow applications in a landscape to communicate with each other using business events.

    To event enable an operation, select Enable Event.

    If an event is subsequently triggered and a message is sent, the proxy recognizes that message. If an operation is not event enabled, the proxy ignores such messages.

    Note Note

    This tab is only displayed if you are working with an event proxy. With SOA Manager, event proxies are configured in the same way as consumer proxies.

    More information:

    Event Enabling for Communication Across Systems in Distributed Landscapes

    End of the note.

    Messaging

    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.

    Compress Response: 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 Service Administration tab and select Web Service Configuration.

  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.

    More information: Creating a Logical Port(above)

  6. Save.

More Information

Generating a Consumer Proxy

Web Service Fallback Solution