Oracle iPlanet Web Server 7.0.9 Installation and Migration Guide

Chapter 2 Installing the Web Server

This chapter provides instructions for installing Web Server. Before you begin, make sure your system meets the requirements specified in the Oracle iPlanet Web Server 7.0.9 Release Notes.

Note –

UNIX installation supports both root and non-root user installations. Non-administrator installation is not supported on Windows. Windows users must have power user or administrator access.

This chapter contains the following sections:

Installation Requirements

Your system must meet the installation requirements specified in the Oracle iPlanet Web Server 7.0.9 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 Chapter 2, 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.

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 on 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, install-dir. 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, 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.

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 Chapter 2, 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: Server Core: Installs the core binaries needed to set up the Web Server environment. Server Core 64–bit Binaries: (Solaris SPARC, AMD64, and Linux only) The 64–bit binaries required for setting up the 64–bit runtime for Web Server instances. This option is available only if the system on which you are installing has 64-bit support. Both the 64- and 32-bit binaries are installed. Administration Command Line Interface: The command-line administration client used to manage and configure the Web Server and its hosted applications from the commandline. Sample Applications: Sample applications that demonstrate Web Server features and functionality. For more information about each component, see Web Server Components.
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.

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.

Installing in Graphical Mode

The graphical interface 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).

Installing in Graphical Mode on UNIX and Linux

The following procedure describes how to install the Web Server in graphical mode on 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. To install in command-line mode, follow the instructions in Installing in Command-Line Mode on UNIX and Linux.

To Install in Graphical Mode on UNIX and Linux

Download the installer file for your platform to a temporary directory. The file format is:

Oracle-iPlanet-Web-Server-7.0.9-platform.zip

Unzip the server files. You will see the following:
- Legal directory
- README.txt
- setup
- WebServer directory

Start the installation with the following command:

./setup

The graphical installation wizard displays. General navigation is as follows:
- Click Back to return to the previous screen.
- Click Next to move to the next screen.
- Click Cancel to cancel the installation.
- Click Help to display documentation specific to the current screen.

Specify the installation directory.

The default is /opt/oracle/webserver7 for the root user and user-home/oracle/webserver7 for non-root users.

Web Server components are installed in the directory specified. If the directory does not exist, you have the option to create it.

Select the installation type, Express (the default) or Custom. For more information about each type, see Installation Types.

Proceed based on installation type:
- For Express installations, specify the user name (admin by default) and password for the Administration Server user, click Next, and go to Step 13 to finish the installation. Steps 9-13 pertain to Custom installations only. For more information about the default settings used for Express installations, see Express Installation.
- For Custom installations, go to Step 7.

Select the components to install.

Note –
Server Core and Administration Command Line Interface (and Server Core 64–bit Binaries, if applicable for your system) are selected by default. You can install the administration command-line interface without installing server core, but you cannot install server core without installing the administration command-line interface. For more information, see Web Server Components.
- Server Core. Installs the core binaries needed to set up the Web Server environment.
- Server Core 64-bit Binaries. (Solaris SPARC, AMD64 and Linux only) Installs the 64–bit binaries required for setting up the 64–bit runtime for the default Web Server instance. This option is selected by default and displays only if the system on which you are installing has 64-bit support. If this option is selected, the 64- and 32-bit binaries are installed. For more information about 64-bit support in Web Server 7.0, see 64-bit Support.
- Administration Command Line Interface. Installs the command-line administration client used to manage and configure Web Server and its hosted applications from the command line. Specify Java configuration information as described in Step 8, and then go to Step 13 to finish the installation.
- Sample Applications. Installs the sample applications that demonstrate Web Server features and functionality.
For more information about each component, see Web Server Components.

Specify Java configuration information.

Choose to install the JDK bundled with Web Server 7.0 (the default) or specify the absolute path to an existing JDK.

Specify configuration settings.

Specify whether to configure the administration instance as the Administration Server (the default) or the Administration Node (as described in Server Core). For more information about these choices, see Web Server Components. For Custom installations performed as root, also specify whether the Web Server and its associated Administration Server should be started and stopped automatically on system startup and shutdown. The default is No (the option is not selected).
- If you select Configure Administration Instance as Administration Server (the default), go to Step 11.
- Enable SMF. Select this option to enable Service Management Facility in both Administration and default instance server. This flag is valid only for Solaris 10. For more information about Service Management Facility for Java Platform, see Integrating Service Management Facility for the Java Platform with Web Server in Oracle iPlanet Web Server 7.0.9 Administrator’s Guide
- If you select Configure Administration Instance as Administration Node, specify the Administration Node settings listed below and then go to Step 13 to finish the installation:
  - Host Name. Specify the fully qualified domain name of the computer on which you are installing the Administration Node instance.
  - SSL Port. Specify the SSL port for the Administration Node instance or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.
  - Runtime User ID. (UNIX, root) Specify the UNIX user name to use when running the Administration Server. For root installations, the default is root. For non-root installations, the default is the user name that you used at login.
  - Register Node with Remote Administration Server. Specify whether this Administration Node instance should be registered with the Administration Server instance at the time of installation (the default), or later (as described in Registering the Administration Node From the Command-Line). If registration is selected, specify the following settings and then go to Step 13 to finish the installation:
    
    Note –
    When registering an Administration Node with an Administration Server, ensure that the system date and time of the Administration Node is same as or later than that of the Administration Server.
    - Administration Server Host Name. Specify the fully qualified domain name of the remote host on which the Administration Server is installed.
    - Administration Server SSL Port. Specify the SSL port on which the remote Administration Server is listening. The default is 8989.
    - Administrator User Name. Specify the administrator user name used to log in to the remote Administration Server.
    - Administrator Password. Specify the administrator user password used to log in to the remote Administration Server.

For Custom installations performed as root, specify whether the Web Server and its associated Administration Server should be started and stopped automatically on system startup and shutdown (the default is No). For Custom installations performed as non-root, go to Step 11.

If configuring the administrations instance as the Administration Server, specify Administration Server settings.
- Host Name. Specify the fully qualified domain name of the computer on which you are installing the Administration Server.
- SSL Port. Specify the SSL port for the Administration Server or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.
- Non- SSL Port. Specify the non-SSL port for the Administration Server. The default is 8800 unless that port is unavailable, in which case this defaults to the next highest available port.
  
  Note –
  SSL port is default for Administration Server. However, you can also choose to use the Non-SSL port. When you choose to install through SSL port, use https:// to access the Administration Server.
- Runtime User ID. (UNIX, root) Specify the UNIX user name to use when running the Administration Server. For root installations, the default is root. For non-root installations, the default is the user you logged in as to perform the installation.
- Administrator User Name. Specify the Administration Server user name. The default is admin.
- Administrator Password. Specify the Administration Server user password.
- Retype Password. Retype the Administration Server user password.

Specify Web Server settings.
- Server Name. Specify the fully qualified domain name of the computer on which you are installing the default Web Server instance.
- HTTP Port. Default value depends upon the runtime user ID of the 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.
  
  Note –
  root user can bind to any port in Solaris 10 OS. However, on other version of Solaris root only can bind to ports lesser than 1024. Solaris 10 provides an alternative way for non-root users to bind to ports less then 1024. On Solaris 10, you need to provide net_privaddr privileges to a non-root user and start the server. For example, you can start the server as webservd. Log in as root and execute the following command: /usr/sbin/usermod -K defaultpriv=basic,net_privaddr webservd. To start the server as another user, you need to change the user name in the above command. For more information on usermod see, http://docs.sun.com/app/docs/doc/816-5166/6mbb1kqk6?a=view. For more information on privileges see, http://docs.sun.com/app/docs/doc/816-5175/6mbba7f30?a=view.
- Runtime User ID. (root only) If the Administration Server instance's runtime user ID is non-root, the default is the same as Administration Server instance's runtime user ID. If the Administration Server instance's runtime user ID is root, the default is webservd.
- Enable a 64–bit runtime. Specify whether the 64–bit runtime should be enabled for the default Web Server instance. The default is No (the option is not selected).
- Create a document Root. Specify whether the default document root should be created during installation. The default is install-dir/https-server_name/docs. The server's content files reside in this directory.
- Use the following directory as document Root. Specify a document root other than the default.

On the Ready to Install screen, click Install Now to install the Web Server software.

A progress bar displays status. Click Stop at any time to stop the installation.

When the installation process is complete, a screen indicates whether installation succeeded or failed, and provides information about using the Administration Server and reviewing the installation log file. Make note of this information for future reference.

Installing in Command-Line Mode on UNIX and Linux

The command-line interface 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).

The following procedure describes how to install the Web Server in command-line mode on UNIX and Linux.

To Install in Command-Line Mode on UNIX and Linux

Download the file for your platform to a temporary directory. The file format is:

Oracle-iPlanet-Web-Server-7.0.9-platform.zip

Unzip the server files. You will see the following:
- Legal directory
- README.txt
- setup
- WebServer directory

Start the installation with the following command:

./setup --console

The command-line installation interface displays. General navigation is as follows:
- Press Enter or Return to move forward in the installation.
- Type < to move back in the installation.
- Type ! to exit the installation.
- Default values are shown in brackets: [ ]. To accept the default, press Enter or Return. To provide a different value, type the value at the command prompt and then press Enter or Return.

Proceed through the introductory information and then specify the installation directory.

The default is /opt/oracle/webserver7 for the root user and user-home/oracle/webserver7 for non-root users.

Web Server components will be installed in the directory specified. If the directory does not exist, you have the option to create it. If a Web Server installation exists in the directory, you have the option to upgrade that installation or specify a different directory.

Specify the installation type, Express (the default) or Custom. For more information about each type, see Installation Types.

Proceed based on installation type:
- For Express installations, specify the user name (admin by default) and password for the Administration Server user, press Enter, and then go to Step 13 to finish the installation. Steps 9–14 pertain to Custom installations only. For more information about the default settings used for Express installations, see Express Installation.
- For Custom installations, go to Step 7.

Specify the components to install, separated by commas.

Note –
You can install the administration command-line interface without installing server core, but you cannot install server core without installing the administration command-line interface.
- Server Core. Installs the core binaries needed to setup the Web Server environment.
- Server Core 64–bit Binaries. (Solaris SPARC, AMD64 and Linux only) Installs the 64–bit binaries required for setting up the 64–bit runtime for the default Web Server instance. This option is available only if the system on which you are installing has 64-bit support. If this option is selected, the 64- and 32-bit binaries are installed. For more information about 64-bit support in Web Server 7.0, see 64-bit Support.
- Administration Command Line Interface. Installs the command-line administration client used to manage and configure Web Server and its hosted applications from the command line. If Administration Command Line Interface is selected and Server Core is not, specify Java configuration information as described in Step 8, and then go to Step 13 to finish the installation.
  
  Note –
  wdeploy command only supports the backward compatibility with Web Server 6.0 and 6.1 releases. This command will work only on the Administration Node.
- Sample Applications. Installs the sample applications that demonstrate Web Server features and functionality.
For more information about each component, see Web Server Components.

Specify Java configuration information.

Choose to install the JDK bundled with Web Server 7.0 (the default) or specify the absolute path to an existing JDK.

Specify configuration settings.

Specify whether to configure the administration instance as the Administration Server (the default) or the Administration Node (as described in Server Core). For more information about these choices, see Web Server Components.

Note –
This option is available only for UNIX custom installation performed as root. Specify whether the Web Server and its associated Administration Server should be started and stopped automatically on system startup and shutdown, (default is No).
- If you select Configure Administration Instance as Administration Server (the default), go to Step 10.
- Enable SMF. Select this option to enable Service Management Facility in both Administration and default instance server. This flag is valid only for Solaris 10. For more information about Service Management Facility, see
- If you select Configure Administration Instance as Administration Node, specify the Administration Node settings listed below and then go to Step 13 to finish the installation:
  - Host Name. Specify the fully qualified domain name of the computer on which you are installing the Administration Node instance.
  - SSL Port. Specify the SSL port for the Administration Node instance or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.
  - Runtime User ID. Specify the UNIX user name to use when running the Administration Server. For root installations, the default is root. For non-root installations, default is the user name that you used at login to perform the installation.
  - Register Node with Remote Administration Server. Specify whether this Administration Node instance should be registered with the Administration Server instance at the time of installation (the default), or later (as described in Registering the Administration Node From the Command-Line). If registration is selected, specify the following settings and then go to Step 13 to finish the installation:
    
    Note –
    When registering an Administration Node with an Administration Server, ensure that the system date and time of the Administration Node is same as or later than that of the Administration Server.
    - Administration Server Host Name. Specify the fully qualified domain name of the remote host on which the Administration Server is installed.
    - Administration SSL Server Port. Specify the SSL port on which the remote Administration Server is listening. The default is 8989.
    - Administrator User Name. Specify the administrator user name used to log in to the remote Administration Server.
    - Administrator Password. Specify the administrator user password used to log in to the remote Administration Server.

For Custom installations performed as root, specify whether the Web Server and its associated Administration Server should be started and stopped automatically on system startup and shutdown (the default is No). For Custom installations performed as non-root, go to Step 11.

Specify Administration Server settings.
- Server Host. Specify the fully qualified domain name of the computer on which you are installing the Administration Server.
- SSL Port. Specify the SSL port for the Administration Server or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.
- Non-SSL Port. Specify the non-SSL port for the Administration Server. The default is 8800 unless that port is unavailable, in which case this defaults to the next highest available port.
  
  Note –
  SSL port is default for Administration Server. However, you can also choose to use the Non-SSL port. When you choose to install through SSL port, use https:// to access the Administration Server.
- Runtime User ID. (UNIX, root only) Specify the UNIX user name to use when running the Administration Server. For root installations, the default is root. For non-root installations, default is the user name that you used at login to perform the installation.
- Administrator User Name. Specify the Administration Server user name. The default is admin.
- Administrator Password. Specify the Administration Server user password.
- Retype Password. Retype the Administration Server user password.

Specify Web Server settings.
- Server Name. Specify the fully qualified domain name of the computer on which you are installing the default Web Server instance.
- HTTP Port. Default value depends upon the runtime user ID of the 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.
  
  Note –
  root user can bind to any port in Solaris 10 OS. However, on other version of Solaris root only can bind to ports lesser than 1024. Solaris 10 provides an alternative way for non-root users to bind to ports less then 1024. On Solaris 10, you need to provide net_privaddr privileges to a non-root user and start the server. For example, you can start the server as webservd. Log in as root and execute the following command: /usr/sbin/usermod -K defaultpriv=basic,net_privaddr webservd. To start the server as another user, you need to change the user name in the above command. For more information on usermod see, http://docs.sun.com/app/docs/doc/816-5166/6mbb1kqk6?a=view. For more information on privileges see, http://docs.sun.com/app/docs/doc/816-5175/6mbba7f30?a=view.
- Runtime User ID. Specify the UNIX user name to use when running the default instance of the Web Server. For root installations, the default is webservd on all UNIX platforms. For non-root installations, default is the user name that you used at login to perform the installation.
- Document Root Directory. Specify the document root directory. The default is install-dir/https-server_name/docs. The server's content files reside in this directory.

Specify whether you want to install the product (the default), start over, or exit the installation.

Following installation, text displays indicating whether the installation succeeded or failed, and providing information about using the Administration Server and reviewing the installation log file. Make note of this information for future reference.

Installing in Graphical Mode on Windows

The following procedure describes how to install the Web Server in graphical mode on Windows. You must be logged in with administrator privileges. Non-administrator installation is not supported on Windows.

Note –

On Windows XP SP2 and Windows server 2003 SP1 onwards, only one instance listens on the same port.

To Install in Graphical Mode on Windows

Download the installer file to a temporary directory. The file format is:

Oracle-iPlanet-Web-Server-7.0.9-windows.zip

Unzip the server files. You will see the following:
- Legal directory
- README.txt
- setup.exe
- WebServer directory

Start the installation by double-clicking setup.exe, or by typing setup from the command line.

The graphical installation wizard displays. General navigation is as follows:
- Click Back to return to the previous screen.
- Click Next to move to the next screen.
- Click Cancel to cancel the installation.
- Click Help to display documentation specific to the current screen.

Proceed from the Welcome screen and specify the installation directory.

The default is C:\Program Files\Oracle\Webserver7.

Web Server components are installed in the directory specified. If the directory does not exist, you have the option to create it. If a Web Server installation exists in the directory, you have the option to upgrade that installation. Otherwise, you must uninstall the existing installation. Only one Web Server 7.0 installation is permitted.

Select the installation type, Express (the default) or Custom. For more information about each type, see Installation Types.

Proceed based on installation type:
- For Express installations, specify the user name (admin by default) and password for the Administration Server user, click Next, and go to Step 12 to finish the installation. Steps 8–12 pertain to Custom installations only. For more information about the default settings used for Express installations, see Express Installation.
- For Custom installations, go to Step 7.

Select the components to install.

Note –
You can install the administration command-line interface without installing the server core, but you cannot install the server core without installing the administration command-line interface. For more information, seeWeb Server Components.
- Server Core. Installs the core binaries needed to set up the Web Server environment.
- Administration Command Line Interface. Installs the command-line administration client used to manage and configure Web Server and its hosted applications from the command line. If Administration Command Line Interface is selected and Server Core is not, specify Java configuration information as described in Step 8, and then go to Step 12 to finish the installation.
- Sample Applications. Installs the sample applications that demonstrate Web Server features and functionality.
For more information about each component, see Web Server Components.

Specify Java configuration information.

Choose to install the JDK bundled with Web Server 7.0 (the default) or specify the absolute path to an existing JDK.

Specify configuration settings.

Specify whether to configure the administration instance as the Administration Server (the default) or the Administration Node (as described in Server Core). For more information about these choices, see Web Server Components. Also specify whether the Web Server and its associated Administration Server should be started and stopped automatically on system startup and shutdown. The default is No (the option is not selected).
- If you select Configure Administration Instance as Administration Server (the default), go to Step 10.
- If you select Configure Administration Instance as Administration Node, specify the Administration Node settings listed below and then go to Step 12 to finish the installation:
  - Host Name. Specify the fully qualified domain name of the computer on which you are installing the Administration Node instance.
  - SSL Port. Specify the SSL port for the Administration Node instance or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.
  - Register Node with Remote Administration Server. Specify whether this Administration Node instance should be registered with the Administration Server instance at the time of installation (the default), or later (as described in Registering the Administration Node From the Command-Line). If registration is selected, specify the following settings and then go to Step 12 to finish the installation:
    
    Note –
    When registering an Administration Node with an Administration Server, ensure that the system date and time of the Administration Node is same as or later than that of the Administration Server.
    - Administration Server Host Name. Specify the fully qualified domain name of the remote host on which the Administration Server is installed.
    - Administration Server SSL Port. Specify the SSL port on which the remote Administration Server is listening. The default is 8989.
    - Administrator User Name. Specify the administrator user name used to log in to the remote Administration Server.
    - Administrator Password. Specify the administrator user password used to log in to the remote Administration Server.

Specify Administration Server settings.
- Server Host. Specify the fully qualified domain name of the computer on which you are installing the Administration Server.
- SSL Port. Specify the SSL port for the Administration Server or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.
- Non-SSL Port. Specify the non-SSL port for the Administration Server. The default is 8800 unless that port is unavailable, in which case this defaults to the next highest available port.
  
  Note –
  SSL port is default for Administration Server. However, you can also choose to use the Non-SSL port. When you choose to install through SSL port, use https:// to access the Administration Server.
- Administrator User Name. Specify the Administration Server user name. The default is admin.
- Administrator Password. Specify the Administration Server user password.
- Retype Password. Retype the Administration Server user password.

Specify Web Server settings.
- Server Name. Specify the fully qualified domain name of the computer on which you are installing the default Web Server instance.
- HTTP Port. Default value depends upon the runtime user ID of the 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.
- Create a default document root. Specify whether the default document root directory should be created during installation. The default is install-dir\https-server_name\docs. The server's content files reside in this directory.
- Use the following directory as document Root. Specify a document root other than the default.

On the Ready to Install screen, click Install Now to install the Web Server software.

A progress bar displays status. Click Stop at any time to stop the installation.

When the installation process is complete, a screen displays indicating whether installation succeeded or failed, and providing information about using the Administration Server and reviewing the installation log file. Make note of this information for future reference.

Click Finish to exit the installation wizard.

Installing in Command-Line Mode on Windows

The following procedure describes how to install the Web Server in command-line mode on Windows. You must be logged in with administrator privileges. Non-administrator installation is not supported on Windows.

To Install in Command-Line Mode on Windows

Download the installer file to a temporary directory. The file format is:

Oracle-iPlanet-Web-Server-7.0.9-windows.zip

Unzip the server files. You will see the following:
- Legal directory
- README.txt
- setup.exe
- WebServer directory

Start the installation with the following command:

setup --console

The command-line installation interface displays. General navigation is as follows:
- Press Enter or Return to move forward in the installation.
- Type < to move back in the installation.
- Type ! to exit the installation.
- Default values are shown in brackets: [ ]. To accept the default, press Enter or Return. To provide a different value, type the value at the command prompt and then press Enter or Return.

Proceed through the introductory information and then specify the installation directory.

The default is C:\Program Files\Oracle\Webserver7.

Web Server components are installed in the directory specified. If the directory does not exist, you have the option to create it. If a Web Server installation exists in the directory, you have the option to upgrade that installation. Otherwise, you must uninstall the existing installation. Only one Web Server 7.0 installation is permitted.

Specify the installation type, Express (the default) or Custom. For more information about each type, see Installation Types.

Proceed based on the installation type:
- For Express installations, specify the user name (admin by default) and password for the Administration Server user, press Enter, and then go to Step 13 to finish the installation. Steps 8–13 pertain to Custom installations only. For more information about the default settings used for Express installations, see Express Installation.
- For Custom installations, go to Step 7.

Specify the components to install, separated by commas.

Note –
You can install the administration command-line interface without the installing server core, but you cannot install server core without installing the administration command-line interface.
- Server Core. Installs the core binaries needed to set up the Web Server environment.
- Administration Command Line Interface. Installs the command-line administration client used to manage and configure Web Server and its hosted applications from the command line. If Administration Command Line Interface is selected and Server Core is not, specify Java configuration information as described in Step 8, and then go to Step 13 to finish the installation.
- Sample Applications. Installs the sample applications that demonstrate Web Server features and functionality.
For more information about each component, see Web Server Components.

Specify Java configuration information.

Choose to install the JDK bundled with Web Server 7.0 (the default) or specify the absolute path to an existing JDK.

Specify configuration settings.

Specify whether to configure the administration instance as the Administration Server (the default) or the Administration Node (as described in Server Core). For more information about these choices, see Web Server Components.
- If you select Configure Administration Instance as Administration Server (the default), go to Step 10.
- If you select Configure Administration Instance as Administration Node, specify whether the Web Server and its associated Administration Server should be started and stopped automatically on system startup (the default is No), specify the Administration Node settings listed below, and then go to Step 13 to finish the installation.
  - Host Name. Specify the fully qualified domain name of the computer on which you are installing the Administration Node instance.
  - SSL Port. Specify the SSL port for the Administration Node instance or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.
  - Register Node with Remote Administration Server. Specify whether this Administration Node instance should be registered with the Administration Server instance at the time of installation (the default), or later (as described in Registering the Administration Node From the Command-Line). If registration is selected, specify the following settings and then go to Step 13 to finish the installation. If registration is not selected, go to Step 13 to finish the installation.
    
    Note –
    When registering an Administration Node with an Administration Server, ensure that the system date and time of the Administration Node is same as or later than that of the Administration Server.
    - Administration Server Host Name. Specify the fully qualified domain name of the remote host on which the Administration Server is installed.
    - Administration Server SSL Port. Specify the SSL port on which the remote Administration Server is listening. The default is 8989.
    - Administrator User Name. Specify the administrator user name used to log in to the remote Administration Server.
    - Administrator Password. Specify the administrator user password used to log in to the remote Administration Server.

Specify whether the Web Server and its associated Administration Server should be started and stopped automatically on system startup and shutdown (the default is No).

Specify Administration Server settings.
- Server Host. Specify the fully qualified domain name of the computer on which you are installing the Administration Server.
- SSL Port. Specify the SSL port for the Administration Server or accept the default. The default is 8989 unless that port is unavailable, in which case this defaults to the next highest available port.
- Non-SSL Port. To create Non-SSL port, select the checkbox Create non-ssl port for the Administration Server. The default is 8800 unless that port is unavailable, in which case this defaults to the next highest available port.
  
  Note –
  SSL port is default for Administration Server. However, you can also choose to use the Non-SSL port. When you choose to install through SSL port, use https:// to access the Administration Server.
- Administrator User Name. Specify the Administration Server user name to use for authentication. The default is admin.
- Administrator Password. Specify the Administration Server user password to use for authentication.
- Retype Password. Retype the Administration Server user password.

Specify Web Server settings.
- Server Name. Specify the fully qualified domain name of the computer on which you are installing the default Web Server instance.
- HTTP Port. Default value depends upon the runtime user ID of Admin 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.
- Document Root Directory. Specify the document root directory. The default is install-dir\https-server_name\docs. The server's content files reside in this directory.

Specify whether you want to install the product (the default), start over, or exit the installation.

Following installation, text displays indicating whether the installation succeeded or failed, and providing information about using the Administration Server and reviewing the installation log file. Make note of this information for future reference.

If you have completed installation successfully. For more information see Chapter 3, Getting Started

Windows Entries

Start menu and registry entries are created during installation, as described in the following sections.

Start Menu

The following Start menu folder is created:

Start > All Programs > Oracle Corporation > Web Server 7.0

If you configure it as Admin Server, the folder contains the following:

Start Admin Server
Start Admin Console
Uninstall

If you configure it as Admin Node, the folder contains the following:

Start Admin Node
Start Admin Console
Uninstall

Registry Entries

Registry entries are modified as follows:

A registry key is created under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall, which adds Web Server to the list of applications that can be uninstalled using the Add or Remove Programs functionality accessed from the Control Panel. This key is removed when the product is uninstalled using the uninstaller.
Entries are added for the Web Server service key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\https-admserv70 for the Administration Server, and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\https-config_name (for example, https-config_name would be https-test for a configuration named test).

Upgrading Web Server from 7.0 to 7.0.9

You can upgrade from Web Server 7.0 to Web Server 7.0.9 using the installation program (setup). While executing the installation program it will detect the existing installation directory, and prompt you to confirm the installation location. Click Yes to continue the upgrade. The remaining steps are similar to the installation steps for more information, see Installing in Graphical Mode.

You can only upgrade Web Server 7.0 to Web Server 7.0 update releases.
In express installation, only existing components are upgraded. For more information on express installation, see Express Installation. In custom installation, existing components are upgraded and you can also install components, which were not installed during Web Server 7.0. You cannot deselect the existing components. For more information on custom installation, see Custom Installation.
During upgrade, installer stops the server instances. You must restart the server instances once the upgrade is done.
If you have installed JDK, which was bundled with Web Server 7.0 and trying to upgrade to Web Server 7.0.9, installation program installs the new version of JDK and it overwrites the existing JDK installation. Ensure to take a backup of the existing JDK installation folder, if you have made any changes to it. If you have used your existing JDK installation during 7.0, then upgrade will continue to use the same JDK.
During upgrade, no change is made to configuration. If you have configured the Administration Server in the Web Server 7.0 installation, then no change is made to it. Only the bits are upgraded.

Advanced Installation Options

The following procedure describes how to install Web Server in silent mode.

Installing in Silent Mode

Silent installation is a non-interactive mode that enables you to run the installer on multiple hosts using an installer configuration file (state file). To install in silent mode, generate a state file as described in Creating a 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 user input.

Creating a State File

The installer configuration file (state file) is created when the savestate option is used with the setup command to start an interactive installation. Settings are captured during the interactive installation and saved in a state file. This file forms the template for silent installation, which can be used to install the product on one or more systems. The state file can be modified later if necessary, as described in Changing the State File.

To Create a State File

Navigate to the directory that contains the setup script and other installation files.

Start the installation program.
- Graphical installation mode:
  - ./setup --savestate (UNIX)
  - setup --savestate (Windows)
- Command line installation mode:
  - ./setup --console --savestate (UNIX)
  - setup --console --savestate (Windows)

Perform the installation as described in the installation steps in Installing in Graphical Mode or Installing in Command-Line Mode on UNIX and Linux.

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. For information about using the state file for silent installation, see Running the Installer in Silent Mode.

Example State File

A state file on the UNIX platform might look as follows. For details about variables in the state file, see Changing the State File.

# Install Wizard Statefile section for Oracle iPlanet Web Server
#
#
[STATE_BEGIN Oracle iPlanet Web Server ad59442e831d7bbf70ae3df748d67c910fca5296]
defaultInstallDirectory = /opt/oracle/webserver7
currentInstallDirectory = /export/home/user1/oracle/webserver7state
UPGRADE = false
SELECTED_COMPONENTS = svrcore,admincli,devsupport
USE_BUNDLED_JDK = true
JDK_LOCATION = 
IS_ADMIN_NODE = false
STARTUP_ONBOOT = false
ADMIN_HOST = amar
ADMIN_SSL_PORT = 8989
ADMIN_PORT = 8800
ADMIN_UID = vg157348
ADMIN_NAME = admin
ADMIN_PASSWD = a
NODE_HOST = 
NODE_SSL_PORT = 
REGISTER_NODE = 
WEB_SERVERNAME = amar
WEB_PORT = 8080
WEB_UID = vg157348
WEB_DOCROOT = 
SIXTYFOURBIT_INSTALL = false
CONFIG_NAME = amar
SKIP_INSTANCE_CREATION = 
[STATE_DONE Oracle iPlanet Web Server ad59442e831d7bbf70ae3df748d67c910fca5296]

Changing the State File

You can change the state file after it has been generated by editing its values and variables. The following table lists the variables in the state file, in alphabetical order.

Note –

Ensure you only edit the values and variables. The structure of the state file should not be modified.

In Web Server 7.0, the values supported for the selected components property were admincli_l10 and svrcore_l10n.

Table 2–3 Variables in the State File


Variable Name	Valid Values (If Applicable)	Description
`ADMIN_PORT`	0-65535	Valid port to run the Administration Server.
`ADMIN_SSL_PORT`	0–65535	Valid port for secure connections.
`ADMIN_UID`	Valid UNIX user ID	Valid UNIX user ID to run the Administration Server.
`CREATE_SERVICE`	True or false	Creates a SMF instance for the server instance. This flag is valid only for Solaris 10.
`NODE_HOST`		Fully qualified domain name of the computer on which you are installing the Administration Node.
`NODE_SSL_PORT`	0–65535	Valid port for secure connections.
`CONFIG_NAME`		Default configuration name used by the Web Server to create a configuration, associate it with a node, and create an instance. The default for the Administration Server is `https-config1`.
`IS_ADMIN_NODE`	True or false	Valid only for Administration Server and Administration Node installations; null for Administration Command Line installations.
`currentInstallDirectory`		Specified installation directory path.
`defaultInstallDirectory`	`/opt/oracle/webserver7` on UNIX; `C:\Program Files\Oracle\Webserver7` on Windows	Default installation directory path.
`JDK_LOCATION`		Selected Java Platform, Standard Edition (Java SE) installation directory path.
`REGISTER_NODE`	True or false	Specifies whether the Administration Node instance should be registered with the Administration Server instance at the time of installation or later.
`SELECTED_COMPONENTS`	`svrcore, svrcore64, admincli, devsupport`	Comma-separated list of product components selected for installation. Installs the following: Server Core: Installs the core binaries needed to set up the Web Server environment. In silent mode, it corresponds to `svrcore`. Server Core 64–bit Binaries: (Solaris SPARC,AMD64 and Linux only) The 64–bit binaries required for setting up the 64–bit runtime for Web Server instances. This option is available only if the system on which you are installing has 64-bit support. Both the 64- and 32-bit binaries are installed. In silent mode, it corresponds to `svrcore64`. Administration Command Line Interface: The command-line administration client used to manage and configure the Web Server and its hosted applications from the command line. In silent mode, it corresponds to `admincli`. Sample Applications: Sample applications that demonstrate Web Server features and functionality. In silent mode, it corresponds to `devsupport`.
`SIXTYFOURBIT_INSTALL`	True or false	Identifies a 64-bit installation.
`SKIP_INSTANCE_CREATION`	True or false	True will not create default instances.
`STARTUP_ONBOOT`	True or false	Start on system boot option.
`UPGRADE`	True or false	Identifies the existing installation.
`USE_BUNDLED_JDK`	True or false	Install the JDK bundled with the installer; if `false`, `JDK_LOCATION` cannot be empty.
`WEB_DOCROOT`		The primary document directory for the Web Server instance; if this is empty, a default document directory is created.
`WEB_PORT`	0–65535	Valid default port to run the Web Server instance server under HTTP mode.
`WEB_SERVERNAME`		Fully qualified domain name of the computer on which the default Web Server instance is installed.
`WEB_UID`	Valid UNIX user ID	Valid UNIX user ID to use when running the default Web Server instance.

Variables such as ADMIN_HOST ADMIN_PORT ADMIN_NAME and ADMIN_PASSWD act differently based on the configuration. The table below has more information that you have installed.

Table 2–4 Configuration for Administration Server Instance


Variable name	Valid values (if applicable)	Description
`ADMIN_HOST`		Fully qualified domain name of the computer on which the Administration Server is installed
`ADMIN_PORT`	0-65535	Non-SSL port for the Administration Server
`ADMIN_NAME`		Administrator user name for the initial server instance
`ADMIN_PASSWD`		Administrator user password for the initial server instance, stored as plain text

The following fields are displayed when you configure Administration Node to an Administration Server.

Table 2–5 Configuration for Administration Node Instance


Variable name	Valid values (if applicable)	Description
`ADMIN_HOST`		Fully qualified domain name of the computer on which the Administration instance is installed
`ADMIN_SSL_PORT`	0-65535	SSL port for the Administration Server
`ADMIN_NAME`		Administrator user name to log in to remote admin server
`ADMIN_PASSWD`		Administrator user password to log into remote admin server

Running the Installer in Silent Mode

The following procedure applies to all supported platforms.

To Run the Installer in Silent Mode

Review the installer configuration file (state file) and verify that it contains the settings you want to use for silent installation.

Copy the state file to each system on which you plan to install the Web Server software.

Copy the Web Server installation files to each system on which you plan to install the Web Server software.

Navigate to the directory where you copied the state file and the installation files.

Start silent installation at the command line using the following syntax:
- ./setup --silent state_file (UNIX)
- setup --silent state_file (Windows)
where state_file is the installer configuration file. The installer program reads thestate_file, checks for adequate disk space, and then installs the product based on the data in state_file.

When the prompt is returned, silent installation is complete and the installation components have been installed.

Configure Later Mode (Java ES Only)

To change the configuration settings after Java Enterprise System (Java ES) installation, edit the configuration.properties file in the path install-dir/webserver7/setup/configurator.properties

Note –

Ensure you only edit the values and variables. The structure of the properties file should not be changed. Do not edit WS_IS_JES and WS_JDK_HOME values.

Table 2–6 Post Installation Configuration Settings


Variable	Valid values (if applicable)	Description
`WS_IS_JES`		Set this flag to true (Java ES environment only).
`WS_JDK_HOME`		Selected Java SE Installation directory path.
`WS_INSTALL_ROOT`		(Required) Specify whether the default installation root should be created during installation.
`WS_INSTANCE_ROOT`		(Required) Specify whether the default instance root should be created during installation.
`WS_DOCROOT`		(Optional) Specify whether the default document root should be created during installation.
`WS_SERVER_NAME`		(Required) Fully qualified domain name of the computer on which the default Java ES instance is installed.
`WS_SERVER_USER`	Valid UNIX user ID	(Required only on UNIX/Linux platforms) Valid UNIX user ID to use when running the default Java ES instance. If the Administration Server instance's runtime userID is `root`, the default is `webservd`.
`WS_HTTP_PORT`	0–65535	(Required) Valid default port to run the Java ES instance server under HTTP mode.
`WS_ADMIN_SSL_PORT`	0–65535	(Required) Specify the SSL port for the Administration Server or accept the default.
`WS_ADMIN_HOST`		(Required) Fully qualified domain name of the computer on which the Java ES Administration server is installed.
`WS_CONFIG_NAME`		(Required) Default configuration name used by the Java ES to create a configuration and associate it with a node to create an instance.
`WS_ADMIN_SERVER_USER`		(Required only on UNIX/Linux platforms) Valid UNIX/Linux user ID to use when running the default Java ES instance.
`WS_ADMIN_LOGIN_USER`		(Required) Specify the administrator user name used to log in to the Administration Server.
`WS_ADMIN_LOGIN_PASSWORD`		(Required) Specify the administrator user password used to log in to the Administration Server.
`WS_ADMIN_HTTP_PORT`	0–65535	(Optional) Non-SSL port of the Administration server. The default is 8800.
`WS_CREATE_SERVICE`	True or false	True will create SMF instance for a server instance.
`WS_START_ON_BOOT`	True or false	(Optional) Start on system boot option.
`WS_SKIP_INSTANCE_CREATION`	True or false	(Optional) True will not create default instances.
`WS_64BIT_INSTALL`	True or false	(Optional) Identifies 64-bit installation. True will configure the server in 64 bit mode 6. False will configure the server in 32 bit mode .
`WS_ADMIN_IS_SERVER_MODE`	True or false	(Optional) True will configure server as Administration Server. False will configure server as Administration Node.
`WS_REGISTER_NODE`	True or false	(Optional) Specifies whether the Administration Node instance should be registered with the Administration Server instance at the time of installation or later. Required only if `WS_ADMIN_IS_SERVER_MODE` is set to false. If set to true, you must provide the name of the remote admin server host for registration.
`WS_NODE_SSL_PORT`	0–65535	(Optional) SSL port of the Administration server. Required only if `WS_ADMIN_IS_SERVER_MODE` is set to false.
`WS_NODE_HOST`		(Optional) Fully qualified domain name of the computer on which the Administration instance is installed.

Note –

When you configure in Configure Late Mode, you must execute configureServer script in the following location:

Solaris: install-dir/setup/configureServer

Linux/HP-UX: install-dir/setup/configureServer

Windows: jes_install_dir\webserver7\setup\

Disable Start on Boot Option

If you select Start on Boot during installation, the following scripts are created:

Solaris: /etc/init.d/webserver7–*
Linux:/etc/init.d/webserver7–*
AIX:/etc/rc.d/webserver7–*
HPUX/sbin/init.d/webserver7–*

An asterisk * in the script name refers to the unique hashcode generated during each installation, for example webserver7–99bbdd. The script contains the variable WS_INSTANCE_ROOT which is set to 1. To disable the Start on Boot option, –-set WS_START_ONBOOT to 0

Note –

Be careful to choose the correct script for your system. Each installation includes its own script with a different hashcode.

Viewing Installation Log Files

Log files are created during the installation process. All installation steps are logged, providing valuable troubleshooting information.

Install Log

The install log file is located in the following directory: install-dir/setup/Oracle_iPlanet_Web_Server_install.log

Install log file entries contain information about the attempted action, the outcome of the action, and the cause of failure if applicable. Entries fall into three categories: INFO, WARNING, and ERROR. The following table describes each category.

Table 2–7 Install Log Entry Categories


Category	Description
`INFO`	Marks normal completion of a particular installation task.
`WARNING`	Marks non-critical failures. Warning-level messages contain information about the cause and nature of the failure, and point to possible remedies.
`ERROR`	Marks critical failures and reports the installation status as failed. Error-level messages provide detailed information about the nature and cause of the problem.
`FINE` `FINEST`	Marks the extent of verbosity of debug messages. `FINEST` gives the maximum verbosity.

Low-Level Install Logs

Low-level install logs are located as follows, where timestamp is of the format mmddHHMM.

Solaris (root installation)

/var/sadm/install/logs/Oracle_iPlanet_Web_Server_install.timestamp
Solaris (non-root installation)

/var/tmp/Oracle_iPlanet_Web_Server_install.timestamp
Linux, HP-UX, AIX

/var/tmp/Oracle_iPlanet_Web_Server_install.timestamp
Windows

%tmp%\Oracle_iPlanet_Web_Server_install.timestamp