Messaging

The Services Framework uses messaging for communication with other products or components. Several queues must be set up and configured for communication between Transaction Server and Services Framework engine.

It is recommended for queues to be persistent and appropriately sized for the expected volume. Table 1 describes the queue definitions required for product communication.

Services Framework retrieves the messages from the Services Framework queue based on the message priority. For additional information about message priority, see Installation.

Table 1. Messaging Queues
Queue	Default	Description
BASE SERVICES QUEUE	FXH.SERVICESFRAMEWORK. INPUT.QUEUE	Main work queue for receiving task initiation requests. The queue is used by Transaction Server for sending requests to start a configured task.
ASYNC SERVICES	FXH.TRANSSERVER.INPUT.QUEUE	Used to send unsolicited messages to the Transaction Server from the Services Framework engine. The messages are responses to the Transaction Server process task initiation request and are not time dependent (responses do not have to be received in a particular time interval). Note: The response message received from the Services Framework for processing a deposit is used to complete the work in progress (WIP) record created by the Transaction Server.
SYNC REPLY QUEUE	FXH.TRANSSERVER. SYNC.REPLY.QUEUE	Used to receive synchronous replies, such as end of day query results and end of day actions, from the Services Framework run time. Synchronous messaging 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.
TRANSACTION QUEUE	FXH.TRANSSERVER.INPUT.QUEUE	Used to notify the Transaction Server about task completion. Some custom tasks notify the Transaction Server that processing is complete by sending a message using this queue.