If the source data is incorrect, Lobster_data throws an IllegalDataException. A class can be specified system-wide, which is called when this error occurs. This class has to implement the interface com.ebd.hub.datawizard.parser.ICorrectValue. Lobster_data provides a programming interface (API) that also allows you to develop your own components in Java. For this, we offer in-depth training. If you are interested, please contact our support or sales staff.

To do this, the Integration Server needs to be told that handling of bad source data is required. This is done by setting the following system property.

-Dhub.datawizard.handleIllegalData=true

Additionally, the following system property is expected to contain the fully qualified class name of the handler class without the file extension.

-Dhub.datawizard.IllegalDataClass

So this way, when Lobster_data is started, it will know which class to call if an IllegalDataException occurs. If the correction of the data does not succeed, the processing is finally terminated. This prevents Lobster_data from entering an endless loop.

Standard Class DefaultCorrectValue

Occasionally, due to a lack of data quality of the input data, there may be control characters that prevent the data from being parsed. You can specify a general handler for this kind of error. There already is a simple standard implementation that replaces all ISO control characters (hex code 0x00 to 0x1F) with an underscore.

com.ebd.hub.datawizard.parser.DefaultCorrectValue.

This class expects a properties file ./conf/invalid_data_settings.properties, which contains the names of all profiles (one name per line) in which the class is to be applied.

Note: If the profile name contains a space, comma, semicolon, colon, equal sign, or backslash, that character must be escaped in the file by a prefixed backslash.