Messaging
The Gateway engine uses messaging for product communication. Several queues need to be set up and configured for communication between the Transaction Server and Gateway. 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 |
|---|---|---|
| GATEWAY ENGINE QUEUE | FXH.GATEWAY.INPUT.QUEUE | Main work queue for receiving Gateway engine work requests. It is mainly used by the Transaction Server for sending requests for processing opened business days. |
| ASYNC | FXH.TRANSSERVER.INPUT.QUEUE | Used to send unsolicited messages from the Gateway engine
to Transaction Server. The messages are responses to requests from the Transaction Server to
process an opened business day. These messages are not time dependent,
which means the responses do not need to be received in a particular
time interval. Examples of Gateway engine message types that need to
use this queue in the jmsReplyQueue parameter
are
|