Non-Queued Delivery of Digital Events
If you configure a service group to have a single destination service, you can choose to bypass the local store-and-forward queue and instead use non-queued delivery. You can choose this option when you do not want events to accumulate in the store-and-forward queue.
You can use non-queued delivery for a service group that has a destination service of type Universal Messaging or Digital Event Persistence.
When you configure event type associations in the Command Central web user interface, you can specify a persistent or a non-persistent delivery mode. Bypassing the store-and-forward queue and using non-queued delivery does not affect the delivery mode preference you configure.
Note: When you use non-queued delivery, DES ignores the storage settings you specify for the store-and-forward queue.
Considerations for Using Non-Queued Delivery
When you use non-queued delivery and an event fails to reach the destination service, depending on the runtime where DES is embedded, DES either throws an exception that notifies the application that the destination service is unavailable or blocks the sending of further events until the destination service becomes available.
When you stop DES while it is in the process of sending events, DES does not guarantee that all events reach the configured destination service before it shuts down. After you restart DES, it does not deliver any events that you sent after DES stopped.
Related Topics