Configuring Web Service Proxies

Use

The configuration of the client-side SOAP runtime, such as the access URL or security settings, is contained in the consumer configuration. These are required if Web service calls are executed using proxies.

The Web service port is part of the WSDL description. This defines a URL where the service is to be called. As a rule, this URL is generated directly into the proxy object. However, this can cause problems whenever the proxy is transported into a system landscape (for example, from the test system into the productive system). In this case, the proxy would still attempt to call the Web service on the test server although the proxy should point to the productive system. The proxy could be re-generated or the coding could be changed manually. Due to the risk of errors with this method, the configuration data in the Web Service Framework is separated from the implementation. After the proxy is transported or redeployed, the URL and other important parameters can be adapted using a simple editor.  

The consumer configurations provided correspond to the configurations created for the Web service.

Procedure

...

       1.      In the Client Explorer of the Enterprise Service perspective, open a consumer configuration by double-clicking it.

       2.      The following features are provided for configuration:

○     Target Address – contains the WSDL file of the Web service.

You can get the Web service’s WSDL documents using the Web Service Homepage.

○     Communication Type

■      Stateless Communication

■      Use HTTP cookie-based sessions – if you want to use stateful communication

■      Use SAP Web AS 6.20 sessions – if you want to access the SAP Web Application Server (Release 6.20).

       3.      If necessary, make the required settings on the Security tab page to ensure security when data is exchanged. You can set the following security configuration:

○     No Authentication

○     SAP Logon Ticket – Single Sign-On mechanism with SAP Logon Tickets

○     SAML – Security Assertion Markup Language for standard Single Sign-On functions

○     Defined Later in the Web Admin.

You can specify the authentication data for deployable proxies at runtime in the SAP NetWeaver Administrator. For more information, see Authentication.