Receiving Messages from Duplicate Detect

Transaction Server receives and processes messages from the Duplicate Detect engine using a JMS listener. Set up a listener profile to listen on the queue you designated as the replyQ for Duplicate Detect in the Duplicate Detect extraction profile. Figure 1 is an example of a listener profile to be used with Duplicate Detect.

Figure 1. Duplicate Detect listener profile

<listenerProfile name="DupDetect" enabled="true">
   <numListeners>2</numListeners>
   <client>true</client>
   <hostname>MYHOST</hostname>
   <channel>SYSTEM.DEF.SVRCONN</channel>
   <port>1419</port>
   <queueManager>FTM.QMANAGER</queueManager>
   <receiveQueue>FXH.TRANSSERVER.INPUT.QUEUE</receiveQueue>
   <errorQueue>FXH.TRANSSERVER.ERROR.QUEUE</errorQueue>
</listenerProfile>

Note: Ensure that the queue specified in the receiveQueue element in the listener profile matches the reply queue specified in the extraction profile. Otherwise, the Duplicate Detect engine will send responses to a queue that the Transaction Server is not monitoring.

When started, the listener monitors the queue specified in the receiveQueue element for messages. Messages coming from Duplicate Detect are parsed and, if transactions were found to be duplicates, the duplicate processor in the Transaction Server sets the DUPLICATE column in the PAYMENT table to either Y – duplicate, N – not a duplicate, or P – potential duplicate. (The transaction was flagged as a possible duplicate by the engine but has not yet been reviewed by an operator.)

Once all results have been processed for a batch (ICL), the batch (ICL) is marked as having been duplicate checked by recording the current timestamp in the DUP_DETECTED column of the PRESENTMENT table. A PresentmentStateChange event is then executed.