Messaging
Settlement uses messaging for product communication. Several queues need to be set up and configured for communication between the Transaction Server and Settlement. 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 |
|---|---|---|
| SETTLEMENT QUEUE | FXH.SETTLEMENT.INPUT.QUEUE | Main work queue for receiving inbound work requests. It is mainly used by the Transaction Server for sending requests for processing deposits. This queue processes prime, repair, and balance feeds from the Transaction Server. |
| ASYNC SETTLEMENT QUEUE | FXH.TRANSSERVER.INPUT.QUEUE | Used to send unsolicited messages from the Settlement engine
to Transaction Server. The messages are responses to requests from the Transaction Server to
process a particular deposit. These messages are not time dependent,
which means the responses do not need to be received in a particular
time interval. Examples of Settlement message types that need to use this
queue in the jmsReplyQueue parameter are
Note: The response message received from the Settlement engine
for processing a particular batch (ICL) is used to complete the work
in progress (WIP) record created by the Transaction Server.
|
| SYNC REPLY QUEUE | FXH.TRANSSERVER.SYNC.REPLY.QUEUE | Used for receiving synchronous replies from
the Settlement engine. Examples of synchronous replies received from the Settlement engine
are end of day query results and end of day actions.
Synchronous
messaging between the Transaction Server and Settlement means a response is required
in a configured time interval. If the reply is not received in the
interval, the process 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.
|