Sender Agreement 

Use

A sender agreement is used during inbound processing. In the agreement, you define how the message is to be transformed so that it can be processed by the PCK.

Prerequisites

You have created a new sender agreement or have opened an existing one.

You must at least specify the party or service and the interface on the sender side for both the sender and receiver.

You can use a wildcard character (*) for the receiver party, receiver service, and the sender interface (see Generic/Specific Definition of Sender Agreements).

Features

The Sender Agreement object comprises the following information:

Header Data

The object key is produced when you create an object; it consists of the following:

●      Sender

○       Party

○       Service

○       Interface (name and namespace)

●      Receiver

○       Party

○       Service

For more information, see Generic/Specific Creation of Sender Agreements.

Parameters Tab Page

Assigning a Communication Channel

You can specify a communication channel (sender channel). Use the input help () to select a communication channel. The input help displays the communication channels that are assigned to the sender.

Propagate Principals

If you want to propagate principals from the sender to the PCK, choose Propagate Principal.

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

More information: Service Users for Message Exchange

More information about the technical configuration of this function: Configuration of Principal Propagation

Security Settings

If you have assigned the sender agreement a communication channel of adapter type XI, SOAP, or Mail, you can make settings for message security.

The Web Services Security or S/MIME checkbox must be selected in the assigned communication channel.

More information:

●      Security Settings for Sender XI Adapter

●      Security Settings for the Sender SOAP Adapter

●      Security Settings for Sender Mail Adapter

Assigned Users Tab Page

If you have restricted the access to the runtime to particular service users for a sender service, you can refine these restrictions with respect to the sender interface. Assign the authorized users to the sender agreement that contains the service 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 in Service.

Obligatory Sender Agreements

You must specify a collaboration agreement if you want to make security settings for the processing of the message.

It is only obligatory to specify a sender agreement in particular cases (when using specific adapters). This depends which information from the adapter configuration in the sender channel is required for successful inbound processing.

 

The following table specifies the sender adapter types that always require the definition of a sender agreement (even if no security settings are made).

Obligatory Sender Agreements

Sender Adapter Type	Sender Agreement Required
File, JMS, JDBC	Yes, see below
RFC	Yes
XI	No
SOAP	No
Mail	No
SAP Business Connector (BC)	Yes

If you use adapters from third-party vendors, check the relevant documentation for the adapters to determine whether you need to define a sender agreement when using their third-party adapters.

Special Conditions when Using the Sender JMS, JDBC, or File/FTP Adapter

These adapter types determine the payload of the message based on their configuration. However, information about the fields of the message header is determined from the corresponding sender agreement for the communication channel. This results in the following conditions for the sender agreements for these adapter types (sender adapters):

●      There must be exactly one sender agreement for each communication channel.

●      At least the interface name and the sender service must be specified in the sender agreement, because these fields must be set uniquely in the message. All other fields are optional (see the section on key fields for sender agreements).

The sender agreement is determined from the sender channel at runtime. The information from the sender agreement is used to construct the address header of the message.