test

Oracle iPlanet Web Server 7.0.9 Installation and Migration Guide

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.

ProcedureTo Create a State File

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

  2. 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)

  3. 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.

ProcedureTo Run the Installer in Silent Mode

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

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

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

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

  5. 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.