Receiver Determination 

Purpose

You use a receiver determination to specify which receivers a message is to be sent to. You have the option of defining conditions for forwarding the message to the receivers. You specify services as receivers of messages.

Features

Assigning Receivers

You can choose between two options for determining receivers (radio buttons):

●     Standard

Choose this option if you want to specify the receivers of the message manually (with optional routing conditions). You can define conditions that relate to the content of the message.

●     Enhanced

Choose this option if you want to have the receivers of the message determined dynamically by a mapping at runtime.

Behavior at Runtime If a Receiver Is Not Found

Even if you have defined the receiver determination correctly, it is possible that the receiver of a message cannot be determined at runtime.

If you define a condition depending on the contents of a message, it can happen that the current inbound message does not contain the application data required to determine a particular receiver.

You can specify what is to happen at runtime if this occurs. You have the following options. In the Configured Receiver frame, select the relevant radio button under If No Receiver Is Found, Proceed as Follows.

Options for Behavior at Runtime If a Receiver Is Not Found

Radio Button	Behavior at Runtime
Terminate Message Processing with Error (Restart Possible)	Message processing is terminated with an error. You can correct the configuration and execute the message again on the Integration Engine (see Displaying XML Message Versions). Select this setting when the underlying scenario is modeled in such a way that a receiver must always be found at runtime. If a receiver is not found at runtime, it is the result of a possible configuration error.
End Message Processing Without Error (Restart not Possible)	Message processing is ended as defined by your configuration settings. Since no receiver is determined, the subsequent pipeline steps (interface determination, mapping, receiver agreement) are not processed. An error message is not sent to the sender. When you select this setting, you cannot execute the message again. Select this setting when messages for which no receiver can be found can typically occur in the underlying scenario.
Continue Message Processing with the Following Receiver:	The message is sent to a fixed predefined receiver. You can specify the receiver in the Party and Service fields (using the input help).

These settings apply to asynchronous messages only. If a receiver cannot be found in synchronous communication, an error always occurs.

Receiver-Dependent Routing

You can define receiver determinations as receiver-dependent.

You can use this property when configuring cross-company processes where not all communication parties know the entire system landscape description. In this case, you can release an external view of your system landscape for your communication parties. Your communication party then knows the externally released virtual receiver to which he can send his messages. By defining one receiver determination that is dependent on a virtual receiver, you can define the internal receiver system to which the message is to be forwarded.

If you want to create a receiver-dependent receiver determination, select the Sender Uses Virtual Receiver checkbox in the create dialog. The system then displays the input fields for the receiver (party, service).

Configuration Overview

The configuration overview that is calculated from the data specified (in the Configured Receiver frame) is displayed in the Display/Edit Receiver Determination editor in the Configuration Overview for this Receiver Determination frame.

Example

See Example of a Receiver Determination.