Defining Receiver Determinations 

Use

You use a receiver determination to define one or more message receivers for a sender and an outbound interface (and optionally for a virtual receiver). You also have the option of specifying the conditions to be applied when forwarding a message to the receiver. Generally, a condition relates to the contents of a message; if a specified condition is fulfilled for a particular payload element (the corresponding element has a certain value, for example), then the message is forwarded to the specified receiver.

Procedure

1. Create Receiver Determination

Create a receiver determination. Enter the object key.

More information:

Creating Objects

2. Assign Receivers and Specify Conditions

There are two options for determining how receivers are determined (checkbox):

●      Standard

If you want to specify the receivers of the message (and optionally routing conditions) manually, select this option. You can also specify conditions that refer to the content of the message.

More information: Entering Receivers Manually

●      Advanced

If you want to determine the receiver of the message dynamically at runtime by means of a mapping, select this option.

More information: Determining Receivers Dynamically

3. Procedure if No Receiver Found at Runtime

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 fulfill the condition.

You can specify what is to happen at runtime if this occurs. You have multiple 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. More information: 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 Communication Component fields (using input help).

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

Optional: Defining Receiver-Dependent Routing

You can define receiver determinations as receiver-dependent.

You can use this property when configuring business-to-business 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.

More information: Configuring Business-to-Business Processes

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, communication component).