Messaging

Distribution uses messaging for communication. Several queues need to be set up and configured for communication between the Transaction Server and Distribution.

It is recommended that all queues be persistent and sized appropriately for the expected volume.

Table 1 describes the queue definitions that are needed for product communication.
Table 1. Distribution Queue definitions
Queue Default Description
DISTRIBUTION QUEUE FXH.DISTRIBUTION.INPUT.QUEUE The main work queue for receiving outbound work requests. This queue is primarily used by the Transaction Server for sending requests to process batches (ICLs). This queue also receives requests for processing individual transactions as they become available after processing through an exception component such as:
  • Image Compliance
  • Payment Repair
DISTRIBUTION BACKOUT QUEUE FXH.DISTRIBUTION.INPUT.BACKOUT.QUEUE Used for automated recovery of incoming Distribution requests if a database failure occurs.
FILE QUEUE FXH.DISTRIBUTION.FILE.QUEUE An internal processing queue that is used only by the Distribution engine. It handles requests for creating transmissions, but is not intended to receive work from any other applications. If prioritization is used when building transmissions, configure the transmission queue so the message delivery sequence property is set to priority and not FIFO. For more information, see Transmission Creation Prioritization.
FILE BACKOUT QUEUE FXH.DISTRIBUTION.FILE.BACKOUT.QUEUE Used for automated recovery of outbound transmission build requests if a database failure occurs.
BATCH QUEUE FXH.DISTRIBUTION.BATCH.QUEUE An internal processing queue that is used only by the Distribution engine. This queue handles requests for creating batches and is not intended to receive work from any other application other than the Distribution engine.

This queue is only used when outbound batches for transmissions whose messaging standard is NACHA are created.
BATCH BACKOUT QUEUE FXH.DISTRIBUTION.BATCH.BACKOUT.QUEUE Used for automated recovery of outbound batch build requests if a database failure occurs.
BUNDLE QUEUE FXH.DISTRIBUTION.BUNDLE.QUEUE An internal processing queue that is used only by the Distribution engine. This queue handles requests for creating segments and is not intended to receive work from any other application other than the Distribution engine.
ASYNC DISTRIBUTION FXH.TRANSSERVER.INPUT.QUEUE This queue is used for sending unsolicited messages to the Transaction Server from the Distribution 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. Examples of the Distribution message types that are configured in the Transaction Server Scheduler.xml that need to use this queue in their jmsReplyQueue parameter are presStatesReached and paymentReady.

Note: The response message that is received from the Distribution engine for processing a particular batch (ICL) is used for completing the Work In Progress (WIP) record that is created by the Transaction Server.
SYNC REPLY QUEUE FXH.TRANSSERVER.SYNC.REPLY.QUEUE This queue is used for receiving synchronous replies from the Distribution engine. Examples of synchronous replies that are received from the Distribution engine would be end of day query results and end of day actions.

Synchronous messaging between the Transaction Server and Distribution means that a response is required in a configured time interval. If the reply is not received in the interval, the process that is 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.