Defining a 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.

Procedure

To define a receiver agreement, perform the following tasks:

1. Create a Receiver Agreement

Create a receiver agreement.

More information: Creating Objects

Specify at least the party or communication component and the inbound interface for the sender and receiver.

You can enter a wildcard character (*) for the sender party, sender communication component, and receiver interface if the receiver agreement is to apply for multiple instances (for example, for all interfaces of the receiver).

More information: Generic/Specific Definition of Configuration Objects

2. Assign Communication Channel

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 receiver (in the key for the receiver agreement).

3. Define Schema Validation

You can specify whether you want the structure of the payload of the outbound message to be checked.

...

       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 receiver 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 Integration Engine.

More information: XML Validation

4. Specify Adapter-Specific Attributes

If you have assigned the receiver agreement a communication channel with adapter type XI, SOAP, Mail, CIDX, or WS you can specify further adapter-specific attributes.

Which adapter-specific attributes are available depends on the adapter type of the assigned communication channel.

Using Adapter-Specific Attributes with a Communication Channel with Adapter Type WS

More information: Adapter-Specific Attributes

Adapter-Specific Attributes when Using XI, SOAP, Mail, RNIF, or CIDX Adapters

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 Receiver XI Adapter

●      Security Settings for the Receiver SOAP Adapter

●      Security Settings for the Receiver Mail Adapter

●      Configuring Security in the RNIF Adapter 1.1

●      Configuring Security in the RNIF Adapter 2.0

●      Configuring Security in the CIDX Adapter

5. Define Header Mappings

If you want to define that the values of the address fields (party, communication component) be transformed in the header of the outbound message, define a header mapping.

More information: Defining Header Mapping

6. Define Principal Propagation

If you want the Integration Server to propagate principals to the receiver (based on authentication assertion tickets), select the Propagate Principal checkbox under Settings for Principal Propagation.

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

When you copy a receiver agreement, the users and passwords that are specified there are not copied as well for security reasons. Note that you therefore need to specify the users and passwords again after the copying process.