Java filter

You can create Java classes to be executed in order to process data delivered to input connectors as well as to output connectors. 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. For example, use a Java input filter to rearrange data before it is processed by the StreamServer application.

The filter reads input from the input stream and writes output to the output stream. If an exception is thrown from the filter, the result is as follows:

•	If used as input filter, no data is sent to the Event for processing. The processing job is not marked as failed by the filter.

•	If used as output filter, no data is sent to any subsequent filters or to the connector. The output job is marked as failed.

Filter settings

Java filter class name	The name of the Java filter class to invoke. This class must implement the streamserve.filter.Execute interface included in jstrs.jar. For information about how to create Java filter classes, see the Java Connectors and Filters SDK documentation.
Java configuration class name	The name of an optional Java configuration class to invoke. This class must implement the streamserve.service.Configuration interface included in jstrs.jar. The configuration is global and shared between all running instances of the same filter. The configuration is loaded once at startup of the StreamServer application. For information about how to create Java configuration classes, see the Java Connectors and Filters SDK documentation.
Configuration file name	Optional configuration file used by the configuration class. The file can be in any format that can be handled by the configuration class, and must be available in a resource set connected to the platform. The file is supplied as a stream to the configuration class readConfiguration method which is called during initialization.