Defining Sender Agreements
In a sender agreement, you define how the message of a sender is to be transformed so that it can be processed by the Integration Engine (see Inbound Processing).
Create a receiver agreement.
More information: 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).
More information: Using Sender Agreements
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.
More information: Configuring Cross-Company Processes

Note the restrictions for sender agreements that are assigned a sender communication channel of adapter type File/FTP, JDBC, or JMS.
More information: Using Sender Agreements
On the
Parameters tab page, select the communication channel in the
Receiver Communication Channel field. To do so, call input help (
). The input help displays the
communication channels that are assigned to the sender (in the key for sender
agreement).
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.
More information:
XML
Validation
If you have assigned the sender agreement a communication channel with adapter type XI, SOAP, Mail, CIDX, or 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.
More information:
Adapter-Specific
Attributes
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.
More information:
● Security Settings for the 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. You specify these security settings in the corresponding
communication channel (see
Configuring the Sender
XI Adapter,
Configuring the Sender
SOAP Adapter, and
Configuring the Sender
Plain HTTP Adapter). You do not need to make any changes in the sender
agreement that references this channel.
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.
More information: Configuring Principal Propagation (Authentication Assertion Ticket).
More information
about the technical configuration of this function:
Configuration of
Principal Propagation
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.