Show TOC Start of Content Area

Procedure documentation Creating Web Service Physical Destinations  Locate the document in its SAP Library structure

Use

This procedure enables you to create and configure a Web service physical destination. More information: Configuration of Several Web Service Clients

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 (AS) Java. You can create physical destinations that point to Web services available on AS ABAP, AS Java, or any external 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.      Log on to the SAP NetWeaver Administrator.

       2.      Choose SOA Management Technical Configuration Destination Template Management.

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

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

The Destination Template Management window opens.

       3.      Choose Create Destination.

       4.      From the Destination Type dropdown box, 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, enter the following URL:

      AS Java

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

      AS ABAP

http://<host_name>:<port>?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).

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

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

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

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

Note

If you are defining a physical destination that you want to access from within Visual Composer, only systems of type ABAP are supported.

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

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

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

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

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

       8.      Set the security settings for the connection.

For more information, see Recommended WS Security Scenarios.

HTTP Authentication

Option

Description

User ID/Password (Basic)

Authentication with user ID and password in HTTP header

More Information: HTTP Transport Level Authentication

User ID/Password (Digest)

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

More Information: Basic Authentication (User ID and Password)

X.509 Client Certificate

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

More Information: HTTP Transport Level Authentication

Logon Ticket

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

More Information: HTTP Transport Level Authentication

Message Authentication

Option

Description

User ID/Password (Basic)

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

More Information: WS-Security UsernameToken

User ID/Password (Digest)

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

More Information: Basic Authentication (User ID and Password)

X.509 Client Certificate

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

More Information: HTTP Transport Level Authentication

SAML Assertion

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

More Information: SAML Token Profile

 

       9.      Choose the Messaging tab to set the service metering options. More information: Service Metering

                            a.      In the Data transfer scope screen area, choose the amount of service metering data transferred to this destination.

§         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 don't have information on 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.

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

   10.      Choose Save.

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

Services Registry

Services

 

End of Content Area