Installation Requirements, Modes and Types
This section provides information on the installation requirements, modes of installation, how to determine which mode to use to install the Web Server 7.0 and the different types of installation. The following topics are covered:
Installation Requirements
Your system must meet the installation requirements specified in the Sun Java System Web Server Release Notes. Review that document before beginning the installation.
Installation Modes
There are three installation modes: graphical, command-line, and silent. These modes enable you to choose the interactive or non-interactive option that best suits your needs.
This section provides a brief overview of the installation modes. For installation instructions, see Installing the Web Server. Graphical, command-line, and silent modes are also available for uninstallation. For uninstallation instructions, see Chapter 4 Uninstalling the Web Server.
Graphical Mode
The graphical mode is an interactive graphical wizard that walks you through the installation process with a series of screens, prompting for installation information and preferences. This is the default mode when the installation program is started without options (./setup). For more information, see Installing in Graphical Mode - UNIX and Linux.
| Note - On UNIX systems, the installation interface defaults to command-line mode if the DISPLAY environment variable has not been exported to your local machine and if X Windows is not supported. |
Command-Line Mode
The command-line mode is an interactive, text-based interface that prompts for responses in a terminal window. To activate the command-line mode, start the installation program using the --console option (./setup --console). For more information, see Installing in Command-Line Mode - UNIX and Linux.
Silent Mode
Silent installation is a non-interactive mode that enables you to run the installer on multiple hosts using an installer configuration file called a state file. The state file is created when the --savestate option is used with the setup command. The state file is saved in the installation directory (/sun/webserver7 by default on UNIX, C:\Program Files\Sun\WebServer7 on Windows). The default name of the file is statefile, but the file name can be changed if desired.
To activate the silent mode, create the state file and then start the installation program using the --silent option (./setup --silent state_file). After the silent mode is activated, installation takes place without additional input. For more information about creating a state file and installing the Web Server using silent installation, see Installing in Silent Mode.
Selecting the Installation Mode
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 ]
| Note - Ensure that the required patches are installed before installation can complete successfully on Solaris. For more information on patch requirement see, Sun Java System Web Server 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 (/sun/webserver7 by default on UNIX, C:\Program Files\Sun\WebServer7 on Windows). 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. |
Installation Types
There are two types of installation: Express (the default) and Custom. The installation type is specified at the start of the installation process. This section briefly describes each type. For more information about specific settings, see the installation instructions in Installing the Web Server.
Express Installation
Express installation enables you to quickly install the Web Server using the most common options and predefined defaults. Express installation is the default installation type and makes assumptions regarding host name, port numbers, and Java Development Kit (JDK™) installation. If you select Express, you do not specify these settings during installation. Settings will be configured automatically using the defaults listed in the following table. Use Express installation if you are new to the Web Server or for evaluation purposes. Choose Custom installation if you want to customize your installation.
Table 2-2 Express Installation Defaults
| Setting | Default |
|---|---|
| Administration instance | Configured as Administration Server. |
| JDK | Installs the JDK bundled with the Web Server. |
| Components | Installs the following:
|
| Start on boot | No. |
Administration Server Settings
| Server host | Fully qualified domain name of the computer on which you are installing the Administration Server. |
| SSL port | 8989 if available; otherwise defaults to the next highest available port. |
| Non-SSL Port | 8800 if available; otherwise defaults to the next highest available port. |
| Runtime User ID (UNIX) | For root installation, default is root. For non-root installation default is the user that is performing the installation. |
Web Server Instance Settings
| Server name | The name of the computer on which you are installing the default Web Server instance. |
| HTTP port | Default value depends upon the run-time user ID of Administration Server instance. If the Administration Server instance's runtime user ID is non-root, the default is 8080. If the Administration Server instance's runtime user ID is root, the default is 80. |
| Runtime User ID (UNIX) | If the Administration Server instance's runtime user ID is non-root, the default is same as Administration Server instance's runtime user id. If the Administration Server instance's runtime user ID is root, the default is webservd. |
| Document root directory | install_dir/https-server_name/docs |
| 64–bit configuration (Solaris SPARC AMD64, and Linux only) | No. |
Registering with Sun Connection
You can register the Web Server with Sun Connection, when running the installation program. To register with Sun Connection, you need to have a Sun Online Account, select the I don't have a Sun Online Account option. This allows you create an account. If you already have an account with Sun Connection, select the I already have a Sun Online Account option and enter the username and password.
| Note - Registration with Sun Connection is not supported through CLI installation program. |
Registering with Sun Connection provides following benefits:
- Patch information and bug updates
- News and events
- Support and training offerings
Custom Installation
Custom installation provides more flexibility and enables you to configure settings that are not specified during Express installation, such as Administration Server and Web Server port numbers and which JDK to use. Use Custom installation if you are an experienced Web Server user and want to customize your installation.