Installing in Silent Mode

Silent mode installation runs without any user input and uses the configuration file to obtain the installation information. This section contains the following topics:

• Creating the Installer Configuration File

• Example of an Installer Configuration File

• Modifying the Installer Configuration File

• Silent Installation Using the Installer Configuration File

Creating the Installer Configuration File

The installer configuration file is created when you use the savestate option with the setup command to start an interactive installation. During the interactive installation, your input is collected and stored in the configuration file you specified. This forms the template for silent installation, which you can use later to install the product on one or more systems. If needed, you can modify the installer configuration file.

The syntax for creating an installer configuration file is as follows:

For graphical method:

./setup --savestate

---

Note –

Type setup --savestate to create the installer configuration file using the GUI method on Windows.

---

For command-line method:

./setup --console --savestate

---

Note –

Type setup --console --savestate to create the installer configuration file using the CLI method on Windows.

---

Example of an Installer Configuration File

An installer configuration file in Windows looks similar to the following:

[STATE_BEGIN Oracle iPlanet Web Proxy Server 
4a5680c3c6f14d78d04ac0cc0ca24780ec56c5a6]
defaultInstallDirectory = C:\\Oracle\\Middleware\\ProxyServer4
currentInstallDirectory = d:\\ProxyServer4
INSTALLATION_OPTION = CUSTOM
USE_BUNDLED_JRE = FALSE
JRE_LOCATION = d:\\jdk\\jre
SELECTED_COMPONENTS = ProxyServer
ADMIN_UID = root
ADMIN_NAME = admin
ADMIN_PWD = admin123
ADMIN_PORT = 8888
SERVER_NAME = jupiter.india.sun.com
PROXY_UID = nobody
SERVER_PORT = 8080
START_ON_BOOT = false
[STATE_DONE Oracle iPlanet Web Proxy Server 
4a5680c3c6f14d78d04ac0cc0ca24780ec56c5a6]

Modifying the Installer Configuration File

You can modify the installer configuration file by editing the variables and values described in Modifying the Installer Configuration File.

Table 1–2 Installer Configuration File Variables

Variable Name	Valid values (if applicable)	Content
currentInstallDirectory		Selected installation directory path
SELECTED_COMPONENTS		List of product components selected for installation
JRE_LOCATION		Selected J2SETM installation directory path
ADMIN_UID	Valid user ID	Valid UNIX user ID to run administration server
ADMIN_PORT	1 - 65535	Valid port to run the administration server
ADMIN_NAME		Administrator user name for initial administrator server instance
ADMIN_PASSWD		Administrator password for initial server instance
PROXY_UID	Valid user ID	Valid UNIX user ID to run the proxy instance server
PROXY_PORT	1 - 65535	Valid default port to run the proxy instance server

Silent Installation Using the Installer Configuration File

Steps for installing Proxy Server in Silent Mode

1. Review the configuration file and verify that it contains what you want to use for your silent installation.

2. Copy your installer configuration file to each system where you plan to install the Proxy Server software.

3. Copy the Proxy Server installation files to each system where you plan to install the Proxy Server software.

4. Navigate to the directory where you copied the installation files and your installer configuration file.

5. Start silent installation at the command line using the following command format:

   ./setup --silent config_file

   ---

   Note –

   Type setup --silent config_file to start the silent installation on Windows.

   ---

   The installation program reads the specified config_file, checks for adequate disk space, then installs the product based on the data in config_file.

   When the prompt is returned, the silent installation is complete and the installation components are installed on your systems.

   You can view the installation log files. For information on the log file paths, see Installation Log Files.

   For information about starting the administration server, see Starting the Administration Server.