Typically, the end-user just executes the package.

On Windows platforms for example, he only has to double-click on the file in Windows Explorer.

On Unix, he goes to the directory containing the file, and executes it in a xterm.

Then, the installer tries to detect available Java virtual machines. If it succeeds, it lists the possibilities, and the user just selects the first one or the most recent one. If it fails, the user is asked to enter a path pointing to a Java virtual machine.

Note: with the Unix/Linux ".sh" installer, java is supposed to be in the user's path, and is directly run without prompting the user. That's why this "unix" target is preferred to "linux-i386" native target.

The user then enters the installer's interface. This interface may be graphic or not, depending on the packager's choice. In graphic mode, a back root panel is painted behind the installer's main window, if it has been enabled by the packager. The user can avoid this panel by launching the installer on the command-line with the "--bluescreen no" argument.

Windows executable example:

  C:\> ExampleSetup.exe --bluescreen no
  

Linux executable exemple:

  $ ./ExampleSetup.lin --bluescreen no
  

Unix/Linux executable shell script:

  $ ./ExampleSetup.sh --bluescreen no
  

For the Java class and Jar targets, the syntax is different:

  $ java -cp . ExampleSetup -Dbluescreen=no
  $ java -Dbluescreen=no -jar ExampleSetup.jar
  

On the same way, the user can force a text user interface mode, by adding the "--uimode" option on the command-line. The uimode can be "ansi" or "text".

Unix/Linux executable shell script:

  $ ./ExampleSetup.sh --uimode text
  

For the Java class and Jar targets, the syntax is different:

  $ java -cp . ExampleSetup -Duimode=text
  $ java -Duimode=text -jar ExampleSetup.jar