Configuring Web Service Connectivity Options to Logical Ports

Configure Web service Security.

Caution

Currently, it is not possible to configure a consumer proxy to use WS-RM together with Web service Secure Conversation (WS-SC). You have to either configure WS-RM, or enable the use of WS-SC for a consumer proxy.

On the Security tab, specify the relevant options.

Option	Description
User ID/Password (Basic)	Authentication with user ID and password in HTTP header
User ID/Password (Digest)	User name 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.

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)	User name 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.

Configure Transport Settings

On the TransportSettings tab you specify the transport between the provider side and the consumer side. The table below lists the available options and explains their meaning.

Option	Description
Use 'Connection: KeepAlive' http header	Enables multiple requests and responses through a single HTTP connection. The provider system keeps the connection alive so that you can use the same connection for multiple request and response cycles.
Support gzip responses	Enables the provider side to return compressed responses to the consumer and in this way improves performance. This option is useful when you expect the provider to return responses whose size is several megabytes. Note If you want to set this option, the provider system has to support compressed responses (gzip).
Max wait-time for http response	Denotes how long the consumer waits for a response from the provider. If you expect huge load on the provider system that would delay the responses to consumers, increase the default value.
Issue chunked requests	Optimizes the method in which the client communicates to the provider the size of its own requests. If the option is selected, the client communicates the size of the message directly in the stream, and does not write it in memory.
Local transport	Optimizes the way in which the Web service client communicates with the Web service when both reside on a same system. If the option is selected, the client calls the service directly. The system does not create a dedicated http connection as a communication channel and does not obey any explicitly configured security settings. Instead, to consume the service, the client uses the same credentials and thread with which you invoked the client. Note You configure Local transport only for Web service clients that are created for Local transport enabled Web services.

Configure Web service addressing

On the Web Service Addressing , specify the protocol for Web service Addressing.

Configure stateful communication

On the StateManagement tab, choose the method for session handling. Currently, only HTTP cookies are supported.

Configure Web Service Reliable Messaging

You configure WS-RM on the Messaging tab. The messaging tab appears only for Web service clients created for WS-RM-enabled Web services.

On the Messaging tab, set the relevant options. The table below lists the available options and explains their meaning.

Caution

Currently, it is not possible to configure a consumer proxy to use WSRM together with Web service SecureConversation (WS-SC). You have to either configure WSRM, or enable the use of WS-SC for a consumer proxy.

Option	Description
RM Protocol	Sets the protocol for reliable messaging.
Exponential Backoff	Exponential backoff sets an algorithm used by the client when it resends messages. If you choose this option, the retransmission interval increases exponentially after each unsuccessful transmission.
Retransmission interval	The interval at which the Web service client tries to resend each message that has not been acknowledged by the Web service.
Inactivity Timeout	If the Web service receives no messages within this interval, it considers the sequence terminated due to the lack activity.
Lifetime of a sequence	The time period for which a sequence remains active.

Configure idempotency

The idempotency enables Web service operations to safely control multiple requests from Web service clients. Before sending the idempotent operation request to the Web service, the Web service client saves the request on the consumer system under a unique ID. At a later stage, if the provider system does not respond, the consumer system resends the request automatically. The retransmission continues until the Web service client receives a response or until the number of retries expires.

Caution

You configure idempotency settings on the Idempotency tab. The Idempotency tab appears only for Web service clients created for idempotency enabled Web services.

On the Idempotency tab, set the relevant options. The table below lists the available options and explains their meaning.

Option	Description
Enable idempotency	Enables idempotency for the particular Web service client.
Retries count	Sets the number of retries of an idempotent request.
Retry interval (in milliseconds)	The interval at which the Web service client tries to resend the idempotent request for which the Web service has not returned a response.

Configure service metering settings. More information: Service Metering

In the Data transfer scope screen area, choose the amount of service metering data transferred:

Option	Description
Minimal Data Transfer	Choose this option when you want the consumer application to send only Calling Application Type to the provider.
Basic Data Transfer	Choose this option when you want the consumer application to send Calling Application Type, Calling Component, and Calling Application ID to the provider.
Enhanced Data Transfer	Choose this option when you want the consumer application to send all caller information attributes to the provider. 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 service providers residing in your internal network.
Transfer via HTTP header	In the Transfer Protocol screen area, choose this option to use the HTTP protocol to transfer service metering data.
Transfer via SOAP header	In the Transfer Protocol screen area, choose this option to use the SOAP protocol to transfer service metering data.

Configuring Web Service Connectivity Options to Logical Ports

Context

Procedure