Show TOC

Procedure documentationConfiguring Individual Web Service Clients Locate this document in the navigation structure

 

A logical port is a reference to a service endpoint available at a unique service endpoint URL on the provider system. That is why, you create a logical port based on the service endpoint URL of the respective service endpoint. You can create a logical port in any of the following ways:

  • Based on the location of the WSDL document (WSDL URL) of the service, which holds the service endpoint of a configured service definition.

    The WSDL document of the service contains the service endpoint URLs of all the service endpoints grouped into the service. You can take the WSDL URL of the WSDL document from the details of the service definition (see the Prerequisites below).

  • Manually, by using the exact location of a particular endpoint (service endpoint URL).

    The endpoint URL is available in the WSDL document of a service. It is displayed in the location property of a port as the code excerpt below shows:

    Syntax Syntax

    1. <service xmlns="http://schemas.xmlsoap.org/wsdl/" name="service name">
 <port name="endpoint name" xmlns:bref="http://ip.test/" binding="bref:DefaultService_">
  <address xmlns="http://schemas.xmlsoap.org/wsdl/soap/" location="endpoint URL" />
 </port>
</service>
    End of the code.

    For every consumer proxy deployed on the application server, by default system creates a logical port. This logical port points to the URL on which the Web service was available when the proxy was generated for that Web service (Normally, this would be a development or a test system, not a productive one). If you want to use this default logical port, you have to manually edit by setting the service endpoint URL of the service endpoint that you want the logical port to call.

    Note Note

    In Single Services Administration application, the system does not display the following entities (consumer proxies):

    • Callable objects that are created with Guided Procedures framework

    • Automated activities and events that are created with Business Process Management framework

    • Adaptive Web service models that are created with Web Dynpro framework

    • Web service operations that are created with Visual Composer framework

    The system displays information about the following consumer proxies:

    • Consumer proxies which use RFC and XI connectivity.

    • Consumer proxies that are created with Composite Designer framework and contain extension points.

    You cannot configure these entities in Single Service Administration application.

    End of the note.

Procedure

  1. Locate the Web service client you want to review or modify.

    For more information, see Finding Web Service Clients.

  2. Add logical ports as necessary.

    For more information, see Creating Logical Ports.

  3. Modify existing logical ports as necessary.

    For more information, see Editing Logical Ports.