Messaging
Risk Management uses messaging for communication. Several queues need to be set up and configured for communication between the Transaction Server and Risk. It is recommended that all queues be persistent and sized appropriately for the expected volume.
| Queue | Default | Description |
|---|---|---|
| RISK MANAGEMENT QUEUE | FXH.RISK.INPUT.QUEUE | The main work queue for receiving risk work requests. This queue is mainly used by the Transaction Server for sending requests to process batches (ICLs). |
| ASYNC DISTRIBUTION | FXH.TRANSSERVER.INPUT.QUEUE | This queue is used for sending unsolicited messages to the Transaction Server from the Risk Management engine. These messages are responses to
messages from the Transaction Server to process a particular batch (ICL). These messages are not time-dependent and the responses do not need to be received in a particular time interval. An example of the Risk message types configured in the Transaction Server Scheduler.xml that need to use this queue in their jmsReplyQueue parameter is performRiskCheck. Note: The response message received from the Risk Management engine for processing a
particular batch (ICL) is used for completing the Work In Progress (WIP) record created by the
Transaction Server.
|
| SYNC REPLY QUEUE | FXH.TRANSSERVER.SYNC.REPLY.QUEUE | This queue is used for receiving synchronous replies from the Risk Management engine. Examples of synchronous replies received from the Risk Management engine would be end of day query results and end of day actions. Synchronous messaging between the Transaction Server and Risk 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 out the synchronous queues from the queues that receive
unsolicited asynchronous messages.
|