Filters and filter chains > Filter reference

Filter reference
Bypass filter
Bypasses the StreamServer, and sends the input data directly to a designated output connector. See Bypass filter.
Note:
Code page filter
This filter is used to apply a code page for the input data. See About code pages and Unicode support for more information.
CollectorArchive filter
This filter archives output data in the storage for Collector. Any metadata intended for archiving is archived together with the data.
Note:
Archiving via the CollectorArchive filter is an alternative to archiving via the output connector. When using the filter, you must assign a document type to the data to be archived. You assign the document type in the Runtime Output Connector dialog box, on the Archiving tab.
To avoid double archiving, make sure that No is selected in the Collector Archive area. The options Device independent copy and Compress documents in archive are not available for the CollectorArchive filter.
Compression filter
This filter compresses the output data.
Decompression filter
This filter decompresses the input data.
External filter
This filter reads data from standard input, sends it to the specified filter, and delivers the filtered data back on standard output. The specified filter can be any executable.
File filter
This filter converts characters in the input data using a conversion table. See File filter.
GenericArchive filter
This filter archives output data in an external archive. Any metadata is archived in an index file together with the data. See GenericArchive filter.
Archiving via the GenericArchive filter is an alternative to archiving via the Generic Archive output connector. When using the GenericArchive filter, you can use any type of output connector for the final delivery of the output data.
You must assign a document type to the data to be archived. You assign the document type in the Runtime Output Connector dialog box, on the Archiving tab.
Internal filter
This filter handles escape codes (HpPcl, Esc0, and URL) in the input data. See Internal filter.
Java filter
You can create Java classes to be executed in order to process data delivered to connectors, e.g. to clean up or rearrange data before it is processed by the StreamServer application. By adding the Java filter to a connector you can call the appropriate Java class to use for processing the data delivered to this connector. The Java filter can be used both as an input and output filter. See Java filter.
Job filter
This filter enables the StreamServer to divide large input jobs into several small jobs. Sequences in the input data determine the size of each job. See Job filter.
AFPIN filter
This filter enables the StreamServer to identify and extract AFPDS (Advanced Function Presentation Data Stream) formatted input. See The AFPIN filter for more information.
PDFIN filter
This filter enables the StreamServer to identify and extract PDF formatted input. See The PDFIN filter for more information.
LiveCycle filter
This output filter is used to integrate Adobe LiveCycle ES processes into the StreamServer pipeline when processing documents. See LiveCycle filter.
PDF signature filter
This output filter is used to create locally signed PDF documents. See PDF signature filter.
Resource filter
This output filter is used to store output from the connected Process as resources in the runtime repository. See Resource filter.
Service call filter
This filter is used to call StreamServer applications exposed via Service Request input connectors. The Service call filter can be used both as an input and output filter. See Service call filter.
OpenText StreamServe 5.6.2 Updated: 2018-01-26