Sender Agreement 

Use

In a sender agreement, you define how the message is to be transformed so that it can be processed by the Integration Engine (see Inbound Processing).

Prerequisites

When you create a sender agreement, you must specify at least the sender interface and the party or service for 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 Configuration Objects).

To enter specific values for the receiver, select the checkbox Sender Uses Virtual Receiver (see also 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 (see below).

Features

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.

Security Settings

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

To be able to configure the security settings, the appropriate checkboxes for message security must be selected in the assigned communication channel: for the adapter types XI and SOAP, select the Web Services Security checkbox; for adapter type RNIF and CIDX, select the checkboxes under Security Settings. In the case of the adapter type Mail, the message protocol must be XIPAYLOAD and the checkbox S/MIME must be selected.

See:

·        Security Settings for Sender XI Adapters

·        Security Settings for Sender SOAP Adapters

·        Security Settings for Sender Mail Adapter

·        Security Settings for RNIF Adapter

·        Security Settings for CIDX Adapter

Obligatory Sender Agreements

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

If you do not want to make any security settings, you must nevertheless always specify a receiver agreement for the definition of outbound processing of the message, regardless of the type of adapter that is used.

However, you only need to specify a sender agreement in particular cases (when using specific adapters). This depends on the information, which comes from the adapter configuration in the sender channel, that 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
JMS, JDBC, File/FTP	Required (see remarks below)
RFC	Required
IDoc	-
HTTP	-
XI	-
SOAP	-
RNIF	Required
CIDX	Required
Mail	-
Marketplace	Required
BC	Required

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

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 for sender agreements that use communication channels with these adapter types.

·        The sender channel must not be assigned to more than one sender agreement.

·        No key fields must contain the wildcard character (*).

·        At least the interface (name and namespace) and the sender service must be specified in the sender agreement because the corresponding address fields in the message must be set uniquely. The remaining fields are optional (see the key fields for the sender agreement).

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.