Show TOC

Defining Sender AgreementsLocate this document in the navigation structure


To configure the inbound processing of a message, define a

Sender Agreement .


1. Creating a Sender Agreement

Create a sender agreement.

For more information, see Creating Objects

When you create a sender agreement, you must specify at least the sender interface and the party or communication component for the sender and receiver. You can enter a wildcard character ( * ) for the receiver party and receiver communication component (and sender interface).

For more information, see Using Sender Agreements

Receiver-Dependent Sender Agreement

You can enter specific values for the receiver. To do so, select Sender Uses Virtual Receiver in the create dialog. It is particularly useful to define a receiver-dependent sender agreement for cross-company processes.


Note the restrictions for sender agreements that are assigned a sender communication channel of adapter type File/FTP , JDBC , or JMS .

For more information, see Using Sender Agreements

2. Assign Communication Channel

On the Parameters tab page, select the communication channel in the Sender Communication Channel field. Use the input help. The input help displays the communication channels that are assigned to the sender (in the key for sender agreement).

3. Define Schema Validation

You can specify whether you want the structure of the payload of the inbound message to be checked.

If you want to have the message validated, you have the following options:

  • Validation by the sender adapter

  • Validation by the Integration Engine

    1. For XML validation to be executed correctly, you must specify the software component version of the interface that is entered in the key for the sender agreement. Only then is it possible to define the message structure uniquely. Use the input help for the Software Component Version field.

    2. If you want the message to be validated, select Validation by Adapter or Validation by Integration Engine .


f you change an object in the ES Repository that is required for validation (a data type, for example) the change is not automatically accepted in the runtime cache. To be sure that you are accessing the current object version in the runtime cache, activate the sender agreement again.

4. Define Principal Propagation

If you want the Integration Server to propagate principals from the sender (on the basis of authentication assertion tickets), on the Parameters tab page, select the Propagate Principal checkbox under Settings for Principal Propagation .


This function is only supported for sender channels with adapter type XI , RFC , or SOAP .

For more information, see Configuring Principal Propagation (Authentication Assertion Ticket)

5. Assign Authorized Service User

If you have restricted the access to the runtime to particular service users for a sender communication component, you can refine these restrictions with respect to the sender interface. Assign the authorized users to the sender agreement that contains the communication component and the interface in the object key.

To do this, in the Edit Sender Agreement editor, choose the Assigned Users tab page and enter the users.

For more information, see Access Control Using Assigned Users .

6. Defining the Scope of Data for Service Call Statistics

For scenarios where communication is based on the proxy runtime or Web service runtime, the service provider is automatically sent statistical information about all service consumers that call it. This function is also activated for scenarios where there is an Integration Server between service consumers and providers. The transfer of this data is always activated, but you can configure the scope of data that is to be transferred to the provider in the service call statistics.

In the sender aggreement you define the scope of the data that is to be provided by the sender (service consumer) and forwarded to the receiver (service provider) by the Integration Server.


To ensure the appropriate input fields are displayed, the sender agreement must be assigned a communication channel with adapter type SOAP or WS in version 7.11 .

You can choose between the following values for the scope of data:

  • Minimal Data Transfer

  • Elementary Data Transfer

  • Enhanced Data Transfer

The default setting for the scope of data is Minimal Data Transfer .

You can also define a protocol for data transfer.

7. Specify Adapter-Specific Attributes

If you have assigned the sender agreement a communication channel with adapter type XI , SOAP , Mail , RNIF , CIDX , oor WS you can specify further adapter-specific attributes on the Parameters tab page.

Which adapter-specific attributes are available depends on the adapter type of the assigned communication channel.

Using Adapter-Specific Attributes with a Communication Channel with Adapter Type WS

For more information, see Adapter-Specific Attributes


If you have assigned a communication channel with an older adapter type version, you can find more information under Adapter-Specific Attributes (Version 7.10) and Adapter-Specific Attribute (Version 7.11) .

Adapter-Specific Attributes when Using XI, SOAP, Mail, RNIF, or CIDX Adapters

If you have assigned the receiver agreement a communication channel with adapter type XI, SOAP, Mail, or CIDX, you can make settings for message security by using the adapter-specific attributes.

To be able to configure the security settings, the following settings must be set in the assigned communication channel:

  • For adapter types XI and SOAP : You must select the checkbox Choose Security Profile and the security profile Web Service Security .

  • For adapter types RNIF and CIDX : You must select the checkbox under Security Settings .

  • For adapter type Mail : Message log XIPAYLOAD message protocol and S/MIME checkbox must be set.

For more information, see

  • Security Settings for Sender XI Adapter

  • Security Settings for the Sender SOAP Adapter

  • Security Settings for Sender Mail Adapter

  • Configuring Security in the RNIF Adapter 1.1

  • Configuring Security in the RNIF Adapter 2.0

  • Configuring Security in the CIDX Adapter


    When you use the sender XI adapter, the sender SOAP adapter, and the plain HTTP sender adapter, you can specify which HTTP security level is to be assumed for incoming messages. Enter these security settings in the related communication channel (see Configuring the XI Sender Adapter ,

    Configuring the Sender SOAP Adapter ,

    Configuring the Sender Plain HTTP Adapter ). You do not need to make any changes in the sender agreement that references this channel.