Configuration Options - Report Configuration FAQs

Configuration Options - Command Line Options

The following list the command-line options that Veduta uses. For configuration on reading files, see the consumers documentation. For information on generating reports, see the reports documentation.

Command Line Options

Veduta command line options are specified in the following fashion: i.e. following the veduta-complete.jar. The exception is the memory option -Xmx which is a JVM option. See below for more details.

The following is a list of supported Veduta options:

• -d {directory name}

  specifies the directory that Veduta will read the main configuration files (veduta.xml, consumers.xml and report.xml) from. e.g.

  > java -jar veduta-complete.jar -d path\to\configs ...
• -client

  runs Veduta in client mode. See the client/server documentation for further information. e.g.

  > java -jar veduta-complete.jar -client -d path\to\configs
• -webserver

  runs Veduta in its webserver mode. Note that running as a webserver implicitly runs Veduta as a server for client processes. e.g.

  > java -jar veduta-complete.jar -webserver -d path\to\configs
• -port

  specifies the port that Veduta listens on for HTTP requests. This option only applies when running as a webserver. e.g.

  > java -jar veduta-complete.jar -webserver -port 9090 -d path\to\configs
• -host

  specifies the interface that Veduta listens on for HTTP requests. Normally Veduta will listen for HTTP on all machine interfaces. This option only applies when running as a webserver. e.g.

  > java -jar veduta-complete.jar -webserver -host hostnameA -d path\to\configs
• -server

  runs Veduta in server mode. See the client/server documentation for further information. e.g.

  > java -jar veduta-complete.jar -server -d path\to\configs
• -clearDb

  forces Veduta to clear out its database of log file information and re-read according to current consumer configurations. This is useful when a configuration changes and the information stored in the db is no longer current/valid. See the database and consumer documentation for more information. e.g.

  > java -jar veduta-complete.jar -clearDb -d path\to\configs
  Note how we still have to specify the configuration (or the path to the configuration) for Veduta to determine which database to clear.

• -Xmx{memory size}m

  configures the maximum amount of memory that the Java virtual machine consumes. This is actually a JVM option - not a Veduta option - but we include this here since it affects running Veduta. Veduta will run with a default maximum memory setting of 64Mb. To change this to (say) 512Mb, simply run using the following option.

  > java -Xmx512m -jar veduta-complete.jar ...
  Note that this option is unlike the Veduta options and is specified directly after the java invocation.

• -h

  displays usage information.