How the FormTrap Server Works

FormTrap Server Structure FireBird DB Service FormTrap Service Application input via any or all of: LP/LPR Shared Folder Named Pipe Output to: Printer Email (including HTML) Fax or e-Fax File structure (no-charge archive) FormTrap Archive (SQL FireBird DB) Your own process (your unmodied batch programs as services) FTQueue 1 FTQueue 2 FTQueue 3 FTQueue .. FTQueue n

FormTrap Server Structure

FormTrap Server Structure FireBird DB Server FormTrap Server Once a file FINISHES being written to a Queue, Windows alerts FTServer (which is inactive without data). FTServer then: Renames the file Saves it to FireBird Processes the file FTQueue 1 FTQueue 2 FTQueue 3 FTQueue .. FTQueue n

FormTrap File Processing FireBird DB Server FormTrap Server I wrote Sent Name to FTQueue 1 Windows alerts FTServer (when the file is closed). Sent Name FTQueue 1 Please press Enter slowly for the next slide

FormTrap File Processing FireBird DB Server FormTrap Server Windows alerts FTServer (when the file is closed). I wrote Sent Name to FTQueue 1 … and saved to DB File is renamed … FTQueue 1 Sent Name FTNumber

FormTrap File Processing FireBird DB Server FormTrap Server This happens AHEAD of every process FTServer initiates. The recovery file is saved, THEN the process is initiated. The last process saves the last resulting file. Files in transition through processes are recoverable.

The original input is received at one of the iSeries Printer Queues The original input is received at one of the iSeries Printer Queues. The file runs through several Processes before being Replicated to the iSeriesProcessing Queue, where it is output to Print, File (long term archive) and to Email. Recovery pre-process files are saved in the DB.

The file is received (User interface) Converted to UTF-8 format (Western) Run through a filter to add Printer Name (Add-Printer-10)

The file is received (Replication) Extracted to XML (text extract), ready for Format Formatted as PostScript and printed (formtrap ps) Formatted as PDF and filed (formtrap pdf) Formatted as PDF and emailed (formtrap pdf)

Eight individual files are saved to Archive for this one transaction, which enters FormTrap at an equivalent Printer queue, then is output to print, file archive and to email.

Key Features FormTrap Server runs 24/7, it’s always READY Pre-process backup to FireBird DB for ALL PROCESSES Processes are requested, then FormTrap Server EXPECTS a reply from Process, if not, it errors Time until a reply is received defaults to 10 minutes (SMTP Server standards), and can be user-set higher FormTrap Server multi-threads, normally 8 or 16 or 32 processes in parallel (user-set number) Data loss is extraordinary and you need to be doing something unusual – like printing directly for huge jobs – where Process Output overlaps Printing and Printer fails Request the PDF article on FormTrap Server for additional details and commentary

Sales@FormTrap.com Support@FormTrap.com +61 2 8303 2400