Select language:

Creating Web Service Physical Destinations

Use

This procedure enables you to create and configure a Web service physical destination. More information: Configuration of Destinations to Provider Systems

You have to create and configure a Web service physical destination for every Web service logical destination available in the consumer application. You can create only one physical destination for every logical destination.

You create Web service physical destinations on the system where the client application is running. This system can be only SAP NetWeaver Application Server Java (AS Java). You can create physical destinations that point to Web services available on AS ABAP, AS Java, or any external systems.

Note

We recommend that you use Service Groups to configure Web service clients that consume Web services on remote provider systems.

To establish a connection to a provider system, create a direct connection to a system in the landscape instead of creating a physical destination.

More information:

Connection to Provider Systems

Creating Connections to Provider Systems

Prerequisites
  • You have access to the SAP NetWeaver Administrator of your AS Java.

  • The client application is deployed.

  • The Web service logical destinations are available in the client application and you know their names.

  • Web services are deployed and configured on the provider system.

  • You know the way in which the client application is to find Web services on the provider system: by using WSDL, WSIL, or SR. When you use WSDL or WSIL, you have to know the correct URL to the WSDL or WSIL on the provider system.

  • If you want the client application to discover a Web service by querying the Service Registry (SR), a connection to the SR has to be configured. More information: Configuring the Services Registry

Procedure

1. Create a Destination

  1. Log on to SAP NetWeaver Administrator .

  2. Choose Start of the navigation path SOA Next navigation step Technical Configuration  Next navigation step Destination Template Management End of the navigation path

    Alternatively, you can use the quick link /DestinationTemplates as follows:

    http://<host>:<port>/nwa/DestinationTemplates

    The Destination Template Management window opens.

  3. Choose New .

2. Set Destination Type and Name

  1. In the Destination Type dropdown list, choose the type of destination.

    The destination type determines the way in which the client application searches for the Web service.

    The table below outlines the possible options, their meaning, and the necessary configuration:

    Destination Type

    Meaning

    Configuration

    WSDL

    The client application accesses the Web service on the provider system by directly using the WSDL file generated for the corresponding Web service.

    When you use this destination type, the whole provider system is viewed as a single Web service.

    In the URL field, enter the direct link to the WSDL file on the provider system.

    WSIL

    The client application locates and accesses the WSDL of the corresponding Web service by using the WSIL.

    Note

    WSIL is a standard containing information about the location of the WSDL of every particular Web service on the provider system.

    In the URL field, enter the direct link to the WSIL on the provider system. Depending on the provider system you can enter one the following:

    • AS Java

      http://<host_name>:<port>/inspection.wsil

    • AS ABAP

      http://<host_name>:<port>sap/bc/srt/wsil?sap-client=<client number>

    Services Registry

    The WSDL of the corresponding Web service is published in a Services Registry. The client application locates the WSDL file by querying the SR.

    Specify the system whose Web services you want to search for in the SR (see below).

  2. In the Destination Name field, enter the name of the physical destination. The name you provide here has to be identical with the name of the logical destination in the client application.

  3. In the Socket Timeout field, specify the socket timeout of the connection. The default value is 60,000 milliseconds.

  4. This step is required only for physical destinations of type Services Registry . The settings you apply specify the system whose Web services published in the SR you want to search for. Proceed as follows:

    1. Depending on the provider system, from the System options, choose Java or ABAP .

    2. In the System name field, enter the system ID <SID> of the provider system.

    3. In the Hostname field, enter the name of the database host of the provider system.

    4. If for System , you chose ABAP , the following additional fields are available:

      1. In the Installation Number field, enter the installation number.

        Note

        To check the installation number, in AS ABAP of the provider system start transaction SLICENSE.

      2. In the Client field, enter the number of the AS ABAP client in which the Web services are available.

  5. Choose Next .

3. Set Security Options

  1. In the Authentication dropdown list, choose the type of authentication you want to use for this destination.

  2. Set the security settings for HTTP authentication.

    Option

    Description

    User ID/Password (Basic)

    Authentication with user ID and password in HTTP header.

    User ID/Password (Digest)

    Username and password based authentication, in which the password is encrypted.

    X.509 Client Certificate

    Authentication with an X.509 certificate using Secure Sockets Layer (SSL).

    Logon Ticket

    Authentication with SAP authentication assertion ticket in the HTTP header, which authenticates the identity of the user.

  3. Set the security settings for message authentication.

    Option

    Description

    User ID/Password (Basic)

    Authentication with a WS-Security Username Token in the security header of the SOAP message.

    User ID/Password (Digest)

    Username and password based authentication, in which the password is encrypted.

    X.509 Client Certificate

    Authentication with an X.509 certificate using Secure Sockets Layer (SSL).

    SAML Assertion

    Authentication with a signed SAML 1.1 assertion in the message header, which authenticates the identity of the user.

  4. Choose Next .

4. Set Service Metering Options

  1. In the Data transfer scope screen area, choose the amount of service metering data transferred to this destination. More information: Service Metering

    • Choose Minimal Data Transfer when you want the consumer application to send only Calling Application Type.

    • Choose Basic Data Transfer when you want the consumer application to send Calling Application Type, Calling Component, and Calling Application ID.

    • Choose Enhanced Data Transfer when you want the consumer application to send all caller information attributes.

    Caution

    Increasing the service metering level may lead to a security risk. When choosing the amount of service metering data you should consider the trustworthiness of the Web service provider:

    • If you do not have information about where and how the Web service is provided, you should choose the Minimal Data Transfer level.

    • When you are sure that the Web service is provided by a trustworthy party you can increase the service metering level. For example, you can do this for destinations to systems residing in your internal network.

  2. In the Transfer Protocol screen area, choose the protocol you want to use for transfer of service metering data.

  3. Choose Finish .

Result

The destination is created and saved. You can see all destinations in the Destinations area of the Web Services Configuration: WS Destinations screen.

More Information