|Top Previous Next|
The filter pack is a series scripts that allow you to modify any input from any API based on nearly any selection criteria of your choosing. These scripts also allows you to read any plaintext content generated by another application; whether that's another program's log files, XML or HTML content, delimited text or anything that can be read as plaintext.
The following files are required for this filter to function:
This filter works in conjunction with PageGate's GetAscii module and these files must reside within a directory that GetAscii is monitoring. When the GetAscii module goes through its normal polling routines and finds data that needs to be processed, it first checks for the existence of preproc.bat. If the batch file is found, it is executed, thereby pre-processing the data being read with the filter.
If preproc.bat doesn't exist in the folder, GetAscii will process the file normally based on the settings in the PageGate Admin, then check for the existence of pstproc.bat. If the batch file is found, it is executed, thereby post-processing the data with the filter.
Effectively, this filter allows you to modify any input fed in to PageGate based on nearly any selection criteria of your choosing so long as the raw data can be read as plaintext; whether that's another program's log files, XML or HTML content, delimited text or anything that can be read as plaintext.
Over the course of this documentation, we'll be going over how to configure each of the different XML flags that the filter uses and how each segment of the filter is implemented.
Before we begin, though, it's important to understand the technical environment in which the script functions.
First, you must own the GetAscii module for your PageGate license as the script directly relies on the module.
Second, you'll need to place certain files in specific locations to implement the script, as mentioned above.
Third, it's important to understand the chain of events that triggers the script to run.
For more detailed information, please see the How to Implement the Script section.
As an important note, due to the way this script is programmed, certain characters are treated as command characters instead of literal text characters. The following characters represent certain command functions in the script: