Configure the BatchDelete Event Handler in Transaction Server

After the Transaction Server has finished its processing for a batch (ICL) delete, it issues a Messaging API BatchDelete event to notify applications about the delete request. As part of the delete process, applications add messages to the deposit group message table to be displayed on a report generated by the Transaction Server user interface. Any application that works with inbound batches (ICLs) should implement a event handler for the BatchDelete event. For more information about this event, see BatchDeleteEventHandler.

Depending on the number of applications that need to process the inbound batch (ICL) delete event, one or more BatchDelete event handler specifications must be added to the Transaction Server Scheduler.xml file. The event handlers should be added to Scheduler.xml in the order they need to be run. The handlers are run in the order they appear in the file and they are called one at a time. The next event is not initiated until the previous event completes.

Note:
  1. The delete event may also be handled by other event handlers or by writing a proprietary event handler. For more information about handling events, see Events and communication with external applications.