Defining Receiver and Routing Conditions

Use

With the following steps you define the receiver of the message within the integrated configuration. Here you can also specify conditions under which the message is to be forwarded to the specified receiver.

The following options are available:

Specify “Local” Rules

You define the rules for a specific integrated configuration. This then also applies for messages where the address field in the header matches the key of the integrated configuration.
Insert (Reusable) Rules

You use a separately-defined rule that can be reused in multiple integrated configurations. A rule such as this is defined as a standalone object in the Integration Directory and identified as a receiver rule.

Note
A receiver rule applies to all messages whose address header matches the object keys of the integrated configurations in which the receiver rule is used. We recommend using receiver rules if you want to use the same rule in different scenarios.

Caution
Note that you cannot specify expressions using XPath when you define conditions in receiver rules.

In comparison to the routing configuration in which the Integration Engine is used as runtime environment, the following restrictions apply:

You cannot configure any scenarios where the receiver components are determined dynamically at runtime.
You cannot select any communication components of type Integration Process in an integrated configuration.

Procedure

Specify Receivers and Conditions for Local Rules

Choose the Receiver tab page.
Specify whether the receivers are to be configured operation-dependently or operation-independently (radio button).
If you want to specify the receivers operation-dependently, all operations are displayed that were defined for the outbound interface in the key of the integrated configuration.

In this case, first select the operation for which you want to specify the receivers and then proceed with the next step.

Note
It is not possible to make operation-specific receiver specifications for interfaces with the interface pattern Stateless (XI 3.0 Compatible) or for imported interfaces (for example IDocs or RFCs).
Specify a receiver (new table row under Configured Receiver).

To do this select the arrow symbol on the pushbutton for adding a new row and call the Add Receiver function.

In the Communication Component column, call the input help. You can then select the communication component of the receiver. If you want to select a communication component that is assigned to a communication party for the receiver, you can first select this in the Communication Party column.
To add a condition to the specified receiver, select the input help in the Conditions column for the row that contains this receiver.

The condition editor is called with which you can define the condition.

More information: Using the Condition Editor

To specify a further receiver for a condition that has already been specified, select the arrow symbol on the pushbutton for adding a new row and call the Add Condition function.

A new row is added to the table for the same condition in which you can specify the receiver (communication component with or without communication party).
To add a further receiver either for which no condition or another condition than previously specified is to be specified, choose the arrow symbol on the pushbutton for adding a new row and call the Add Receiver function.

Insert Receiver Rule

If a specific receiver rule exists for the configuration you want, you can use this and add it to the integrated configuration.

To do this within the Configured Receivers frame, choose the arrow beside the Insert Line Below Selection ([PICT]) icon and choose Insert Receiver Rule. Call input help for the Rule column and select the receiver rule.

More information: Defining a Receiver Rule

Caution

Unlike an integrated configuration, you define a receiver rule independently of an outbound interface. Therefore, the structure of a corresponding outbound message is not displayed for a receiver rule. The specification of expressions using XPath is therefore not supported during the definition of conditions in receiver rules. You can only access the content of a message by using context objects. If a required context object is not available, you must create it in the Enterprise Services Repository.

More information: Using the Condition Editor

Caution

A receiver rule can only be used in integrated configurations if the receiver parties and communication components have a fixed target value. Context objects are not possible for parties and communication components because integrated configurations require static information about receivers.

If you add a new receiver to a receiver rule, you must adapt all dependent integrated configurations. That is, you must configure the receiver interface and the receiver communication channel for the new receiver. If, on the other hand, you change conditions or remove receivers from a receiver rule, you do not have to adapt the dependent integrated configurations.

Procedure if No Receiver Found at Runtime

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

Example

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.

Setting	Behavior at Runtime
Error message	Message processing is terminated with an error. You can correct the configuration and restart the message processing. Recommendation 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.
Ignore	Message processing is ended as defined by your configuration settings. Since no receiver is determined, the subsequent pipeline steps (determining the inbound interface, mapping, outbound processing) are not processed. An error message is not sent to the sender. When you select this setting, you cannot execute the message again. Recommendation 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).

Setting

Behavior at Runtime

Error message

Message processing is terminated with an error.

You can correct the configuration and restart the message processing.

Recommendation

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.

Ignore

Message processing is ended as defined by your configuration settings. Since no receiver is determined, the subsequent pipeline steps (determining the inbound interface, mapping, outbound processing) are not processed. An error message is not sent to the sender. When you select this setting, you cannot execute the message again.

Recommendation

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).

Note

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