There are three installation modes: graphical, command-line, and silent. For more information about each mode, see Installation Modes. The setup command is used to specify the installation mode. The syntax is as follows:
./setup [--help] [--console] [--silent state_file] [--savestate] [--javahome java_dir] [--id]
Ensure that the required patches are installed before installation can complete successfully on Solaris. For more information on patch requirement see, Oracle iPlanet Web Server 7.0.9 Release Notes
The following table lists the setup command options.
Table 2–1 Options for the setup Command
Option |
Description |
---|---|
./setup --help |
Displays the options for the setup command. |
./setup |
Runs the installer in graphical mode. |
./setup --console |
Runs the installer in command-line mode. |
./setup --savestate |
Runs the installer in graphical mode and also creates an installation configuration file (state file) based on this installation, to be used for silent installation. The state file is created and saved in the installation directory, install-dir. The default name of the file is statefile, but the file name can be changed if desired. |
./setup --console --savestate |
Runs the installer in command-line mode and also creates an installation configuration file (state file) based on this installation, to be used for silent installation. |
./setup --silent state_file |
Runs the installer in silent mode. Installation parameters are read from the specified state file (state_file), which was first created using the --savestate option. |
./setup --javahome java_dir |
Defines the location of the JDK installation that should be used for the installer Java Virtual Machine (JVM), in graphical mode. |
./setup --console --javahome java_dir |
Defines the location of the JDK installation that should be used for the installer JVM, in command-line mode. |
./setup --id |
Shows the unique identifier for the installer build. This option is provided to simplify reuse of installer state files between builds, if necessary. Each installer build has a unique identifier. To reuse installer state files created by different installer builds, the unique identifier referenced in the installer state file must match the one in the current installer build. The --id option enables you to determine this value so you can edit the value in the state file. |