Transaction Server User's Guide

Overview
Starting the Transaction Server
Transaction Server properties files
Groups and Permissions
Integrating the Transaction Server in Payment Feature Services
Transaction Server User Interface
Task Scheduler
Events and communication with external applications
Business day overview
Extracting data
Trackable Item Support
Unload Inbound Transmission
Inbound and processing batch (ICL) overview
There are two levels of batches (ICLs), inbound and processing batches (ICLs). Each inbound batch (ICL) contains one or more processing batches (ICLs).
Batch (ICL) status transitions
Cancel batch (ICL)
Undo cancel batch (ICL)
Delete Batch (ICL)
Cancel transaction
Services Framework task registration and configuration
The tasks must be added to the Services Framework runtime engine, registered, and configured before they can be used.
Services Framework task status and actions
Business day activation task
A business day represents the processing date and category of the work that is being received. The category can be used to separate work for the same business date. Before a business day is used, it must be opened and activated.
Entry Allocation Tasks
File Tracking Purge Task
Input File Creation (ICRE) Task
User Exits
Available commands
Troubleshooting
The following topics describe how to debug or resolve common problems that might occur with Transaction Server.
Database Schema
Database views for extracting runtime data
Aggregation Example
File Name Patterns and Custom File Formatters
Utilities
Recommendations
Transmission File Format
Installing the Transaction Server Host Applications

Parent topic: Payment Feature Services