Messaging
Duplicate Detect uses messaging for product communication. Several queues need to be set up and configured for communication between the Transaction Server and Duplicate Detect. It is recommended that all queues be persistent and sized appropriately for the expected volume.
Table 1 describes the queue definitions needed
for product communication.
| Queue | Default | Description |
|---|---|---|
| DUP DETECT QUEUE | FXH.DUPLICATEDETECT.INPUT.QUEUE | The main work queue for receiving duplicate detect work requests. It is used by the Transaction Server and host Duplicate Detect component for sending requests to perform duplicate checking. |
| ASYNC DUPDETECT QUEUE | FXH.TRANSSERVER.INPUT.QUEUE | Used for receiving asynchronous replies from the Duplicate Detect engine. The messages are responses to messages from the Transaction Server and host Duplicate Detect components to perform duplicate checking. The Transaction Server scheduler configuration uses this name for the value of the jmsReplyQueue parameter. The Transaction Server listener profile configuration uses the name for the value of the receiveQueue parameter. |