Configuring Adapter Type WS Communication Channels (Old Version)

With the communication channel for which you have implemented the adapter type WS, you can configure the communication using Web service runtime.

More information: Communication Channel (Adapter Type WS)

Recommendation

For compatibility reasons the version of the adapter type WS is offered which was previously available in earlier support packages of SAP NetWeaver PI 7.1 (SAP BASIS 7.10). Use this older version if, for example, you have performed configuration work on the basis of such an earlier support package and you now want to proceed with this work on the basis of the current support package.

For more information on using different adapter type versions, see Configuring the Communication Channel with Adapter Type WS.

End of the recommendation.

Note that the security settings that you have to make in the communication channel only make sense in the context of a wide-ranging security scenario.

More information on the recommended security settings: Recommended WS Security Scenarios.

Note that the following security settings are not supported for a WS communication channel with adapter type version 7.10:

WS Security UsernameToken
WS Security Asymmetrical Encryption

Features

To configure a communication channel with adapter type WS, proceed as follows:

Note Note

To use the older version (SAP BASIS 7.10) of adapter type WS, you must first import the corresponding adapter metadata to the ES Repository.

More information: Importing ESR Content

End of the note.

1. Create a Communication Channel, Specify a Direction and Adapter Type

First create the communication channel, specify whether it is to be a sender or receiver channel and choose the adapter type WS (older version).

Call the create dialog box for communication channels and specify the necessary key values (party and communication components).
More information: Defining Communication Channels
Select the adapter type in the communication channel editor.
Select the input help for Adapter Type.

For the older version of the adapter type WS, select the entry with the following values:

Name: WS

Namespace: http://sap.com/xi/XI/System

Software component version: SAP BASIS 7.10
Choose Copy.
These are the default attributes:
- Transport Protocol: HTTP 1.0
- Message Protocol: WS 1.0
- Adapter Engine: Integration Server

2. Define Type of Web Service Call

The type of Web service call specifies whether the call is made locally (same logical system), or remotely (different logical system). Depending on your choice, select or deselect the checkbox Local Call.

Note Note

You can only configure this setting for a receiver channel.

End of the note.

The call type you select determines which other attributes you can define.

3. Specify Further Attributes for Local or Remote Calls

Configuring Local Calls

Specify the following attributes for a local call:

Technical Transport Settings
Input Field	Description
Transport Binding	The default value isSOAP 1.1 Using HTTP. More information: http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383526.

Settings for Web Service Addressing

You use these settings to determine how the Web service call can be addressed independently of a transport protocol.

Input Field	Description
Protocol	Specifies protocol for Web service addressing The default value is WS-A
Reference Parameters (Server)	Input field for parameters that are to be specified with the Web service call and that can be used to identify the Web service call. The information specified here is in the SOAP header of the message. Enter the parameters as strings. You can specify a reference parameter if necessary.

Input Field

Description

Protocol

Specifies protocol for Web service addressing

The default value is WS-A

Reference Parameters (Server)

Input field for parameters that are to be specified with the Web service call and that can be used to identify the Web service call.

The information specified here is in the SOAP header of the message.

Enter the parameters as strings.

You can specify a reference parameter if necessary.

For more information about Web service addressing, see: http://www.w3.org/TR/ws-addr-core/.

Settings for Handling Message Attachments
Input Field	Description
Process Non-Modeled Attachments checkbox	Specifies whether non-modeled attachments are to be transferred with the message. Non-modeled attachments are attachments that are appended to the message as an HTTP or MIME attachment. Modeled attachments are appended directly in the message.

Configuring Remote Calls

Specify the following attributes for a remote call:

Security Settings
Input Field	Description
Authentication Method field	Specifies whether the sender has to authenticate itself with the service provider, and if so, how. You can choose between the following authentication methods: User ID/Password (Authentication on HTTP Level) Authentication with X.509 SSL Client Certificate (Using HTTPS) More information: Client Certificates Authentication with logon ticket (HTTP Level) More information: Logon Tickets Authentication with X.509 SSL Client Certificate (authentication in message) More information: Client Certificates Authentication with X.509 SSL Client Certificate SAML 1.1 Sender Vouches Assertion (authentication in message) More information: Configuring Principal Propagation (SAML)

Technical Transport Settings
Input Field	Description
Transport protocol	Specifies the required transport protocol (HTTP or HTTPS).
Target host	Specifies the name of the target machine
Service Name/Port	Specifies the port for the target machine
URL Access Path or Target Client	If the target system is an SAP system (ABAP-based), specify the client (field Target Client (ABAP stack)). In this case you must also enter the logon language in the target system. Note If you configure a sender channel, this attribute is set for the input of a target client (ABAP stack) because in this case you are addressing the Integration Server in the channel. End of the note.
URL Access Path or Target Client	If the target system is not an SAP system (ABAP-based), enter the URL (access path) for the target system (field URL Access Path). Caution Either enter the URL as WSDL URL or as an access URL, depending on how you want to implement the channel. Enter a WSDL URL if you want to use the communication channel to configure the outbound processing of the Integration Server. In this case assign the channel later to a receiver agreement. The Integration Server functions at runtime as Web service consumer and requires the WSDL URL at configurations time to be able to access the WSDL document. The web service consumer configuration for the Integration Server is basically based on the information in the WSDL document. Enter an access URL if you want to use the communication channel for direct communication. In this case assign the channel later to a direct connection. The sender functions at runtime as Web service consumer and required the access URL to be able to execute the call to the Web service provider (receiver). End of the caution.
Access Path Points to a WSDL (Use of Channel in Receiver Agreement)	Select this checkbox if you want to use the communication channel for enhanced communication. The URL is then categorized as a WSDL URL. Caution If you select this checkbox, the communication channel cannot be used for direct connection. End of the caution.
Optimized XML Transfer	Specifies whether the message is to be converted to a special format to speed up transfer. The following values are possible: No Optimization Binary MTOM XML Format If you select this entry, the message will be transferred using the MTOM (Message Transmission Optimization Mechanism) standard. This means that binary data of type base64Binary is stored in a message attachment (XOP attachment) for transferal, and does not need to be decoded separately. More information: SOAP Message Transmission Optimization Mechanism (MTOM) More information: http://www.w3.org/TR/soap12-mtom/ Binary SAP-XML Format If you choose this entry then the message will be optimally transferred based on an SAP-own format. The performance improvement can be seen like this: If the same day appears repeatedly in the payload then the day is only given completely in the first position. In all further positions in the payload only a reference to the day is given. If the payload contains binary parts then, according to base64Binary, these must not be converted separately. This is because when using the binary XML format XML data is not transferred, only binary data.
Transport Binding	The default value isSOAP 1.1 Using HTTP. More information: http://www.w3.org.
Server Side Session Timeout	Specifies time (in seconds) after which the connection in state management is canceled.

Reliable Messaging Settings

You use these settings to define the reliable transferal of asynchronous messages, based on the standard WS-RM protocol.

Input Field	Description
Acknowledgement Interval	Specifies a time interval (in seconds) in which the receiver (Web service provider) has to confirm receipt of a message.
Protocol	Specifies the protocol for Web Services Reliable Messaging (WS-RM). The default value is WS-RM 2005/02. More information: http://specs.xmlsoap.org/ws/2005/02/rm/ws-reliablemessaging.pdf.

Input Field

Description

Acknowledgement Interval

Specifies a time interval (in seconds) in which the receiver (Web service provider) has to confirm receipt of a message.

Protocol

Specifies the protocol for Web Services Reliable Messaging (WS-RM).

The default value is WS-RM 2005/02.

More information: http://specs.xmlsoap.org/ws/2005/02/rm/ws-reliablemessaging.pdf.

Settings for Web Service Addressing

Proceed as described for the local call.

Settings for Handling Message Attachments

Proceed as described for the local call.