Start of Content Area

Background documentation Quality of Service  Locate the document in its SAP Library structure

The sender of a message uses the attribute Quality of Service (QoS) to determine how a message is delivered. The following types of quality of service are supported:

      BE (Best Effort):

The message is sent synchronously. The sender waits for a response before it continues processing.

      EO (Exactly Once):

The message is sent asynchronously. The sender does not wait for a response. The Integration Engine and the Advanced Adapter Engine  guarantee that the message is sent and processed exactly once.

      EOIO (Exactly Once In Order):

Messages are delivered with the same queue names (supplied by the application) in the same sequence that they were sent from the sender system. Message processing is asynchronous in this case.

In the case of quality of service BE an error occurs if more than one receiver is determined for a message. In the case of delivery types EO and EOIO, the message is copied correspondingly and sent to the individual receivers.

Synchronous Message Processing (BE)

The message is only persisted by the Integration Engine in case of error (as an error version). Once a message has been processed in the target system it performs an implicit database commit.

Asynchronous Message Processing (EO, EOIO)

The message is persisted by the Integration Engine at a predefined time and scheduled for processing using the queued RFC (qRFC).

To do this, the qRFC requires the technical names of the inbound and outbound Integration Engine queues.

 

 

End of Content Area