The following sections describe how to start the installation program on Windows and UNIX platforms:
Before you start installing the software, please review the following information:
The following sections describe how to start the installation program on a Windows platform:
Note: | If you are installing the software on a Windows system that supports more than one monitor, you must disable all but one monitor before starting the installation program. |
To start the installation program in graphical-mode on a Windows platform, follow these steps:
For example, the name of the installation program for WebLogic Server net installer is net_server103_win32.exe.
The installation program begins to install the software.
To start the installation program in console-mode on a Windows platform, follow these steps:
|
For example, to launch the installation of WebLogic Server in console mode, enter net_server103_win32.exe -mode=console
Note: | You can include the -log= full_path_to_log_file option in the command line to create a verbose installation log. |
Note: | For example, for WebLogic Server, enter: net_server103_win32.exe -mode=console -log=C:\logs\server_install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
After a few moments, the installation program begins to install the software.
For information about silent-mode installation, see What Is Silent-Mode Installation?
Note: | You must use the package installer for silent-mode installation. Silent-mode installation is not supported with the net installer. |
To start the installation program in silent-mode on a Windows platform, follow these steps:
silent.xml
file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For information about creating a silent.xml
file, see Creating a silent.xml File for Silent-Mode Installation.Note: | Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation. |
server103_win32.exe -mode=silent -silent_xml=
path_to_silent.xml
Here, path_to_silent.xml
is the full pathname of the silent.xml
file.
Note: | You can include the -log= full_path_to_log_file option in the command line to create a verbose installation log. |
Note: | For example, for WebLogic Server installer: server103_win32.exe -mode=silent -silent_xml=C:\silent.xml -log=C:\logs\server_install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
An Oracle Installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.
For more information, see Running the Installation Program in Silent Mode.
The installation program requires a Java run-time environment (JRE) to run. A JRE is bundled in the Windows installation program, and in some UNIX installation programs (those with filenames ending in .bin
). For other UNIX platforms, the installation program does not include a JRE. Filenames for these installation programs end in .jar
. To run the .jar
installation programs, you must have an appropriate version of a JDK installed on your system, and include the bin
directory of the JDK at the beginning of your PATH
system variable.
Notes: | It is important that you use a JDK because the installation process assigns values to JAVA_HOME and related variables to point to this directory. All scripts installed by your installation program use this JDK by default, including scripts to start sample applications, the Configuration Wizard, and other development tools. |
Note: | To run graphical-mode installation, your console must support Java-based GUIs. If the installation program determines that your system cannot support Java-based GUIs, it automatically starts running in console mode. For more information, see Running the Installation Program in Console Mode. |
The following sections describe how to start the installation program on UNIX platforms, using filenames that end in .bin
:
To start the graphical-mode installation process for installation files with names ending in .bin
, follow these steps:
chmod a+x <
filename
.bin>
./<filename
.bin>
In these commands, filename
.bin
is the name of your installation program. For example, for WebLogic Server the file name is: net_server103_solaris32.bin
.
Note: | You can include the -log= full_path_to_log_file option in the command line to create a verbose installation log. |
Note: | For example, for WebLogic Server: net_server103_solaris32.bin -log=/home/logs/install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
Note: | The installation program begins to install the software. |
To start the console-mode installation process for installation files with names ending in .bin
, follow these steps:
chmod a+x
<filename
.bin>
./<filename
.bin> -mode=console
Here filename
.bin
is the name of your installation program. For example, for WebLogic Server: net_server103_solaris32.bin
.
Note: | You can include the -log= full_path_to_log_file option in the command line to create a verbose installation log. |
Note: | For example, for WebLogic Server, enter: net_server103_solaris32.bin -mode=console -log=/home/logs/install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
For details about silent-mode installation, see What Is Silent-Mode Installation?.
To start the silent-mode installation process for installation files with names ending in .bin
, follow these steps:
silent.xml
file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For information about creating a silent.xml
file, see Creating a silent.xml File for Silent-Mode Installation.Note: | Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation. |
chmod a+x
filename
./<filename
.bin>
-mode=silent -silent_xml=/<
path_to_silent.xml>
Here, filename
.bin
is the name of the installation file (for example, for WebLogic Server: server103_solaris32.bin
), and path_to_silent.xml
is the full pathname of the silent.xml
template file.
Note: | You can include the -log= full_path_to_log_file option in the command line to create a verbose installation log. |
Note: | For example, for WebLogic Server, enter: server103_solaris32.bin -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
An Installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.
For more information, see Running the Installation Program in Silent Mode.
The following sections describe how to start the installation program on UNIX platforms using generic installers (filenames that end in .jar
):
To start the installation program in graphical-mode for installation files with names ending in .jar
, follow these steps:
bin
directory of the appropriate JDK to the beginning of the PATH
variable definition on the target system.
For example: PATH=$
JAVA_HOME
/bin:$PATH
export PATH
Here JAVA_HOME
represents the full path to the JDK directory.
java -jar net_server
<version>_generic.jar
Note: | You can include the -log= full_path_to_log_file option in the command line to create a verbose installation log. |
Note: | For example: net_server <version>_generic.jar -log=/home/logs/install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
The installation program begins to install the software.
To start the installation program in console-mode for installation files with names ending in .jar
, follow these steps:
bin
directory of the appropriate JDK to the beginning of the PATH
variable definition on the target system. For example:
PATH=
JAVA_HOME
/bin:$PATH
export PATH
Here, JAVA_HOME
represents the full path to the JDK directory.
java -jar <
filename
.jar> -mode=console
Here, filename
.jar
is the name of the Products installation file, for example, net_server
<version>_generic.jar
.
Note: | You can also include the -log= full_path_to_log_file option in the command line to create a verbose installation log. For example: |
Note: | java -jar net_server <version>_generic.jar -mode=console |
Note: | For more information, see Generating a Verbose Installation Log. |
For details about silent-mode installation, see What Is Silent-Mode Installation?.
To start the installation program in silent-mode for installation files with names ending in .jar
, follow these steps:
silent.xml
file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For information about creating a silent.xml
file, see Creating a silent.xml File for Silent-Mode Installation.Note: | Incorrect entries in the silent.xml file can cause installation failures. To help you determine the cause of a failure, we recommend that you create a log file when you start the installation. |
bin
directory of the appropriate JDK to the beginning of the PATH
variable definition on the target system. For example:
PATH=
JAVA_HOME
/bin:$PATH
export PATH
Here, JAVA_HOME
is the full path of the JDK directory.
java -jar
<filename
.jar> -mode=silent
-silent_xml=/path_to_silent
.xml
Here, filename
.jar
is the name of the Products installation file (for example, server
<version>_generic.jar
, where, path_to_silent.xml
is the full path to the silent.xml
file.
Note: | You can include the -log= full_path_to_log_file option in the command line to create a verbose installation log. |
Note: | For example: server <version>_generic.jar -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
An Installer window is displayed, indicating that the files are being extracted.
For more information, see Running the Installation Program in Silent Mode.
For details about running the installation program, see one of the following, depending on your selected installation mode: