When I first scoped out the capabilities for RPM Remote Print Manager® ("RPM"), I planned text print, raw print, and the filter for program execution. The program option was based on an earlier experience where having a program to translate a file from one format to another made it printable in my environment. In Unix, these were "filters".
A common use for a filter is to transform the print job from one format to another, perhaps plaintext or the nroff markup language into PostScript. Another typical use we find in RPM is to inject a print job into a database. Obviously, that's the work of a custom program.
History of the Filter
What we call a "filter" is just a program. Read more
What programs are candidates to be RPM filters
Not every program would be a good candidate to run as an RPM filter. Read more
Basic filter program setup
About standard output
About standard input
What "Launch as a Shell Program" is about
The option to "launch as a Shell Program (cmd.exe)" primarily makes a more stable environment for running Windows batch files.
We have supported customers who used this and found their processing went according to their plan. If you want to try it, please take note of your results with and without the setting.
Once in a while, we run into a vendor program with behavior that is a little puzzling. Read more
Let’s take a closer look at the Arguments field in the filter setup. Read more
When RPM executes your command, it passes the command line to Windows as a string. Read more
Let’s say you are not getting the results from your filter action that you expect. Read more
If you are running the 32-bit RPM on 64-bit Windows, you may run into problems. Read more
Differences between the system account and a desktop user
Migrating your filter program to a new server
At the bottom of the filter setup form is the error handling setting. Read more