You need the jacson.jar and the additional
jars in classpath. Note that the built in
jacson.jar meta informations
suggests to look for these additional jars in a lib
directory relative to the jacson.jar . This is
the file layout how Jacson is distributed.
File filtering
With the provided jacson.jar and
when you have the needed jars in path, calling Jacson
(with the LineChunkSource ) is
as easy as:
java -jar jacson.jar ConfigurationFile [ParamName=ParamValue]* DataFiles+
|
A configuration file name as first parameter is required.
Subsequent name=value pairs can be used to override
<se:param se:name="otto" se:value="waalkes">
settings in that configuration. Following these pairs
(recognized by the "=" character) follows a list
of input files which are to be filtered by Jacson
Examples can be found in the batchfiles in the
samples directory.
Internally above line starts the static method
main() of
de.spieleck.app.jacson.Jacson .
When you want to start the TailSource (log) file watching facility you need
the jacsontail.jar in the same directory as
jacson.jar and use
java -jar jacsontail.jar ConfigurationFile [ParamName=ParamValue]* LogFiles+
|
Parameters work similar as above. The difference is that the
listed files are not treated in an particular order, but watched
for changes.
This call will not return, it will
continue running until you stop it.
Internally above line starts the static method
main() of
de.spieleck.app.jacson.JacsonTail .
When you want to use
GenericSources you need
the jacsongeneric.jar in the same directory as
jacson.jar and use
java -jar jacsongeneric.jar ConfigurationFile
|
Notice that there are no longer any parameters since the
configuration of the GenericJacsonChunkSource is done in the
ConfigurationFile.
Internally above line starts the static method
main() of
de.spieleck.app.jacson.JacsonGeneric .
|