Sender Agreement 

Use

In a sender agreement, you define how the message is to be transformed so that it can be processed by the PCK (inbound processing).

Prerequisites

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

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: Defining Sender Agreements Generically/Specifically

More information: Creating Objects, Object Editors

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

○       Communication component

○       Interface (name and namespace)

●      Receiver

○       Party

○       Communication component

Parameters Tab Page

Assigning a Communication Channel

To assign a communication channel (sender channel), use the input help (). The input help displays the communication channels that are assigned to the sender.

For more information, see: Communication Channel

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.

You can find more information under:

●      Security Settings for the 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 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.

See: Communication Component under Access Control Using Assigned Users

 

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

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

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.

Notes for JMS/JDBC/File Adapters

In the case of these adapter types, the information about address fields of the message header is determined from the sender agreement that the communication channel is assigned to. The following conditions apply to sender agreements that use communication channels with these adapter types.

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

●      No key fields may contain the wildcard character (*).

●      At least the interface name and the sender communication component 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.