Configuring Technical Transport Settings

Target Host

Specifies the name of the host.

On a sender channel this field specifies the name of the computer where the Integration is installed.

Service Name/Port

Specifies the ports used to called the Web service provider.

• Service Name/Port

  Specify this attribute if HTTPS is not set as communication security setting.

• HTTPS Service Name/Port

  Specify this attribute if HTTPS is set as communication security setting.

  If HTTPS and also Secure Conversation were set as enhanced security settings, then both fields are displayed. In this case both ports are required (in the sender channel). The reason for this is that Secure Conversation is first established using HTTPS. Once the connection is established, the communication is continued using the HTTP protocol (for performance reasons). That is why you have to enter the service name/port.

HTTPS Service Name/Port

URL Access Path

Specifies the URL of the target system.

If the target system is an SAP system, specify the client (field Target Client ).

In this case, you have to specify a logon language yourself.

The input field for the target client is always displayed for a sender channel since the Integration Server (SAP system) is always addressed using the channel.

Target client

Transport Binding

The following values are possible:

• SOAP 1.1 using HTTP

• SOAP 1.2 using HTTP

More information: http://www.w3.org/2003/06/soap11-soap12.html

Server Side Session Timeout

Specifies time (in seconds) after which the connection in state management is interrupted.

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) , 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.

(English channel only): Derive Optimized XML Transfer

If this option is activated (as standard), the settings for optimzed XML transfer are copied from the WSDL file of the Web service provider.

If this option is deactivated, you can manually specify the settings for XML transfer.