Show TOC

Procedure documentationDefining Receiver and Routing Conditions Locate this document in the navigation structure

 

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.

In comparison to the routing configuration in which the Integration Server is used, 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 Receiver and Conditions

  1. Choose the Receiver tab page.

  2. Specify whether the receivers are to be configured operation-dependently or operation-independently (radio button).

  3. 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 Note

    The option to specify receivers operation-specifically is only available for interfaces modeled in the ES Repository. For imported interfaces, such as IDocs or RFCs, you can not specify the receivers operation-specifically.

    End of the note.

  4. To specify a receiver, add a new row to the table (under Configured Receivers).

    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.

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

    For more information, see: 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).

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

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

End of the example.

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.

Behavior at Runtime If a Receiver Is Not Found

Setting

Behavior at Runtime

Error message

Message processing is terminated with an error.

You can correct the configuration and restart the message processing.

For more information, see: Displaying XML Message Versions

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

End of the recommendation.

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 Recommendation

Select this setting when messages for which no receiver can be found can typically occur in the underlying scenario.

End of the recommendation.

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 Note

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

End of the note.