Acknowledgment Support in the Adapter Engine

Receiver Adapter

• System acknowledgments and system error acknowledgments

  • Receiver adapters that run on the Adapter Engine support system acknowledgments and system error acknowledgments if they are requested by the sender.

    The acknowledgments are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed.

    Multiple system error acknowledgments can be sent, followed by a system acknowledgment in the case of a successful retry.

  • The receiver JMS adapter is an exception to this rule.

    By using a parameter in the configuration, you can specify whether a system acknowledgment is sent like all other adapters or whether a DeliveryAckNotSupported is sent instead.

    This is recommended if the delivery of the message by the JMS adapter is considered to be too weak to trigger a system acknowledgment.

    More information: Configuring the Receiver JMS Adapter

• Application acknowledgments and application error acknowledgments

  • Receiver adapters of the Adapter Engine do not support any application acknowledgments.

  • The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application error acknowledgments.

• ApplicationAckNotSupported and ApplicationErrorAckNotSupported

  All receiver adapters send ApplicationAckNotSupported and ApplicationErrorAckNotSupported

Sender Adapter

• Sender adapters of the Adapter Engine do not request any acknowledgments.

• The RNIF and CIDX adapters also support system acknowledgments, system error acknowledgments, and application error acknowledgments, depending on the scenario.