Overview

The Transaction Server manages the flow of work that is loaded into Common Services.

The Gateway Server ingests transmissions and stores the data in the database for other processes to use. As records are written to the database or manipulated during processing, events are generated and sent to the Transaction Server. Interactions with the Control Center can also cause more events to occur, which are also sent to Transaction Server. The Transaction Server determines whether the event warrants further action based on the scheduled configuration. Many events cause messages to be sent to other components for further processing. Those components might modify the data in the database during processing and cause more events to be sent to the Transaction Server for further evaluation.

The Transaction Server is also responsible for managing business days, including the business day state, database table partitioning by business day or date, and purging of data for a business day.

Transaction data can originate from any of the following sources (with or without images):

Electronic transaction files such as image cash letters (ICLs).
Branch capture devices
Automated Teller Machines (ATMs)
Other item capture and exchange applications.

Typically, Gateway loads these transactions into Transaction Server.

All the transaction information that is used by Transaction Server is indexed by site, business day date, and business category. This indexing allows for the retention of several days worth of transaction information. The retention period is entirely at the discretion of the customer, but is primarily driven by storage availability.