Basics
Launching Veduta
Veduta™ can be run direct from the supplied
.jar file. Veduta requires 3 configurations, and these can be specified individually or implicitly by specifying a directory name. e.g.
> java -jar veduta-complete.jar {system config} {consumer config} {report config}
or
> java -jar veduta-complete.jar -d {configuration_directory}
(in both cases assuming that
java is on your path). If the
-d option is used then the directory has to be named and the individual configuration names are implicit.
Warning: if you get the following error:
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/oopsconsultancy/veduta/main/Veduta (Unsupported major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
...
then your Java virtual machine is too old a version. See here for Java information.
Once invoked, Veduta will run until explicitly killed. It will monitor log files every second and generate reports as the log files are updated. Veduta doesn't need to be prompted to regenerate reports, nor scheduled etc.
If you're running Veduta in a server environment and you have no display (e.g. you're running on a headless server) then you need to specify a further flag.
> java -Djava.awt.headless=true -jar veduta-complete.jar ...
so that Java doesn't expect a display where there isn't one.
Veduta Configurations
Veduta has three configuration files. These are discussed briefly below (in sufficient detail to be able to run up Veduta) and later on in further detail.
The three configurations are:
- veduta.xml. This is the system configuration and is used to configure system-wide properties. e.g. the location of the underlying database to use.
- consumers.xml. This specifies the log files or systems that Veduta will read to generate its reports
- report.xml. This specifies the report to output and the formats to use
For example, in the
examples/apache directory,
veduta.xml specifies a database to use.
consumers.xml specifies that Veduta will read the access and error logs.
report.xml specifies how those reports are to be presented - e.g. colours, formats etc.
Veduta can thus be run using either:
> java -jar veduta-complete.jar \
examples\apache\veduta.xml \
examples\apache\consumers.xml \
examples\apache\report.xml
(all on the same line)
or
> java -jar veduta-complete.jar -d examples\apache
(the latter assumes the configuration file naming i.e.
veduta.xml / consumers.xml / report.xml)