Receiver Determination 

The receiver of an XML message is determined during inbound processing in logical and technical routing. This determines how processing will continue, depending on the number of receivers found.

·        If the system cannot find a receiver, it displays an error and terminates processing.

·        If only one receiver is found, the message is placed in the corresponding outbound queue for outbound processing.

The quality of service Exactly Once (EO) has the following distinctive feature:

Using the configuration parameter EO_INBOUND_TO_OUTBOUND, you can specify the TUNING category so that a message is not placed in the outbound queue as usual; instead the message is processed and sent entirely in the inbound queue.

This improves performance, but there is the disadvantage that the inbound queue is blocked if the receiver cannot be reached. However, in the outbound case, the only queue that is blocked is the one where the messages for this receiver are located.

·        If multiple receivers are determined and the quality of service is Exactly Once (EO) or Exactly Once In Order (EOIO) then the message is branched.

A new message with a new message ID is created from the original message for each interface/receiver pair in the receiver list.

If the quality of service is Best Effort (BE), an error occurs.

Message Branching for EO

If multiple messages are going to the same receiver, an internal queue name is generated from the message ID of the original message, to ensure that the correct processing sequence is maintained. As a result, the quality of service switches from EO to EOIO.

Message Branching for EOIO

To ensure that the message branching can be tracked, the message ID of the original message is saved with each new message.

To guarantee that the processing sequence from the receiver list is maintained for messages with the same receiver, the queue name specified by the application is included in each new message.