This documentation corresponds to a historical version of Yellowfin


Access the latest release, or view a list of available versions of the documentation.

Skip to end of metadata
Go to start of metadata


The Yellowfin Installer supports three modes of operation:

  1. Standard Graphical Installer
  2. Command-line Installer
  3. Silent Installer

The installer is distributed both as a Windows Executable (.exe) or a Java Archive (.jar) file. The Windows Executable installer only supports the graphical installation mode. When using the .jar installer, the default behaviour is to launch the graphical installer. If no graphical environment is detected, for example a headless linux/unix server, the command-line installer will be launched instead. The installation mode can be specifically selected by adding a switch argument to the command used to run the installer.

If the graphical installer is requested with -gui, but no graphical environment is available, an error message will be displayed.

Each installation mode performs the same tasks, and requires the same parameter values to be entered. However, the way they are displayed is quite different.

The general process undertaken by the installer is:

  1. Obtain values for user options
  2. Install distribution files
  3. Setup Yellowfin database
  4. Perform post-installation tasks

The installer provides a high level of customisation. Parameters may be set which can be used to customise the text and images displayed during the installation, pre-population user options, hide or show different options, and perform post-installation tasks to change the default behaviour of Yellowfin. These parameters can be set in different ways. In order of precedence, these are:

  1. Default options provided by the installer where appropriate
  2. Custom properties file bundled with the installer
  3. Command-line arguments provided to the installer
  4. Silent installer properties file (silent installation only)
  5. Options entered by the user during the installation (graphical and command-line installation)

For example, an option specified on the command line will override the same option specified in the custom properties file.