Duplicate Detect Ingestion Unload

If you are using the Transaction Server to send items to Duplicate Detect, configure the Transaction Server to send an unloadDepositGroup message to Duplicate Detect. This message causes Duplicate Detect to remove any units of work from the Duplicate Detect database for any inbound transmissions that are being unloaded. To successfully unload an inbound transmission from Duplicate Detect, the Transaction Server must be configured to only aggregate items from a single inbound transmission (file) or batch (cash letter) and not aggregate items across inbound transmissions (files). The Transaction Server scheduler XML must also be configured to send the unloadDepositGroup message to Duplicate Detect.

<EVENT>
  <NAME>Dup Detect - Unload Deposit Group</NAME>
  <TYPE>UnloadDepositGroup</TYPE>
  <EXEC>com.ibm.paydir.ima.txsvr.event.appbridge.UnloadDepositGroupEventHandler</EXEC>
  <PARAMETER name="msgType">unloadDepositGroup</PARAMETER>
  <PARAMETER name="parmFileName">../profiles/DupProfile.properties</PARAMETER>
  <PARAMETER name="ABSvcPayload">DUP_PAYMENT</PARAMETER>
</EVENT>

The following list describes the information that is shown in this example event stanza.

NAME

A user-defined name that is given to the event stanza.

TYPE

Type of event. It must be UnloadDepositGroup.

EXEC

Name of the event handler to process the event. It must be entered exactly as shown.

PARAMETER name="msgType"

Type of message to send to Duplicate Detect. It must be entered exactly as shown.

PARAMETER name="parmFileName"

Qualified path and name of the file that contains the necessary properties to send a message to Duplicate Detect. For more information, see Setting up a Messaging API event handler.

PARAMETER name="ABSvcPayload"

Name of the payload sent with the message. For the unload message, this should be the name of the namespace from which to unload the inbound transmission.