Messaging
Suspect Image Review uses messaging for communication. Several queues must be set up and configured for communication between the Transaction Server and Suspect Image Review. It is recommended that all queues be persistent and sized correctly for the expected volume.
The following table describes the queue definitions that are needed for communication.
| Queue | Default | Description |
|---|---|---|
| REVIEW QUEUE | FXH.IMAGECOMPLIANCEINPUT.QUEUE | Main work queue for receiving suspect image review work requests. It is primarily used by the Transaction Server for sending requests for processing batches. |
| ASYNC REVIEW QUEUE | FXH.TRANSSERVER.INPUT.QUEUE | Used to receive asynchronous replies from the Suspect Image Review engine. The messages are responses to messages from the Transaction Server to process a particular batch. The Transaction Server scheduler configuration uses this name for the value of the jmsReplyQueue parameter. The Transaction Server listener profile configuration uses this name for the value of the receiveQueue parameter. |
| SYNC REPLY QUEUE | FXH.TRANSSERVER.SYNC.REPLY.QUEUE | Used for receiving synchronous replies from the Suspect Image
Review engine. Examples
of synchronous replies that are received from the Suspect Image
Review engine are end of day query results
and end of day actions. Synchronous messaging between the Transaction Server and Suspect Image Review means that a response is needed in a configured time interval. If the reply is not received in that interval, the process that is waiting for the reply times out and fails. Note: It is recommended to separate the synchronous queues from the queues that receive unsolicited
asynchronous messages.
|