Receiver Agreement 

Use

In a receiver agreement, you define how the message is to be transformed so that it can be processed by a receiver.

You must specify a receiver agreement for all adapter types to ensure that outbound processing is executed correctly.

Prerequisites

When you create a new receiver agreement, you must at least specify the party or service and the inbound interface for the sender and receiver.

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

Features

Assigning a Communication Channel

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

Header Mapping

You use a header mapping to map the values of the following key fields in the receiver agreement to other values: Sender and receiver party, sender and receiver service. The address fields (sender, receiver) in the message header are then transformed correspondingly during outbound processing.

The header mapping is important when configuring cross-company processes in which the business partners want to replace the names of their internal business systems with neutral representatives (party, business service).

If you want to replace the internal name of a sender business system in the outbound message with a neutral name of a party and service, specify the fields for Sender Party and Sender Service in the header mapping.

You can do the following in the header mapping:

●      Specify fixed values

●      Define that the conversion of the field values is to be determined dynamically from the message payload

To specify the header mapping for an address field, select the check box for the field name (for example, sender service) and choose Display List of Permitted Values ().

There are different editors for specifying the party and service:

●      Use the party editor to specify a party

●      Use the service editor to specify a service

Header mappings are only supported by the following receiver adapters at runtime:

-          IDoc adapter

-          Plain HTTP adapter

-          RNIF adapter 2.0

-          RNIF adapter 1.1

-          CIDX adapter

Principal Propagation

If you want the Integration Server to propagate principals to the receiver, select the Propagate Principal checkbox.

This function is only supported for receiver 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 receiver 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.

Refer to

●      Security Settings for Receiver XI Adapter

●      Security Settings for the Receiver SOAP Adapter

●      Security Settings for the Receiver Mail Adapter

●      Security Settings for RNIF Adapter

●      Security Settings for CIDX Adapter

Data Scope for Service Metering

For scenarios where communication takes place using the XI or SOAP adapter, statistical information is transferred automatically to the receiver (service provider) using all the senders that call it (service consumers). Data transfer is constantly activated, however during configuration you can specify the data scope that is to be transferred to the receiver as part of service metering.

In the receiver agreement you specify the scope in which consumer data is to be sent to the receiver using the Integration Server.

The receiver agreement must be assigned a communication channel with adapter type XI or SOAP for the input fields intended for this are shown.

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

●      Minimal data transfer

●      Elementary data transfer

●      Extended data transfer

The data transfer scope is set to minimal by default.

If you have assigned a communication channel with adapter type SOAP to the receiver agreement then in addition to this you can define a specific protocol for transferring data.

More information: Service Metering