Bypasses the StreamServer, and sends the input data directly to a designated output connector. See Bypass filter.This filter is used to apply a code page for the input data. See About code pages and Unicode support for more information.
Note: If you use the CollectorArchive Filter, you must create and configure the Collector archive in Control Center. You must also configure an Archiver application, which will transfer the documents to the Collector archive. For more information, see Control Center documentation > StreamStudio Collector configurations.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.This filter archives output data in an external archive. Any metadata is archived in an index file together with the data. See GenericArchive 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.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.This filter enables the StreamServer to identify and extract AFPDS (Advanced Function Presentation Data Stream) formatted input. See The AFPIN filter for more information.This filter enables the StreamServer to identify and extract PDF formatted input. See The PDFIN filter for more information.This output filter is used to integrate Adobe LiveCycle ES processes into the StreamServer pipeline when processing documents. See LiveCycle filter.
| OpenText StreamServe 5.6.2 | Updated: 2018-01-26 |