Transaction Server components

Transaction Server also operates as a stand-alone application server.

Components of Transaction Server are shown in the following list.

Events: Events and their criteria are defined by using an event stanza in the Scheduler.xml file. An event is processed. It is then determined whether the criteria that are defined in the stanza were met to either act upon the event in Transaction Server or to send a message to another component.
Server: The server is the runtime component that manages the workflow. As work is loaded and processed by other components, the server determines which events need further processing. The server issues messages to notify other components what work needs to be done. Actions that are initiated from the user interface, such as business day management, holdover, or unload transmission, are processed by and coordinated by the server.
User interface: Transaction Server has a browser based user interface that runs in Control Center. Operational screens show the ingested transactions and provide business day management and other actions.