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:
http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/index.html
.
The following sections describe how to start the installation program on a Windows platform:
Notes: | 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. |
Note: | If you want to install Node Manager as a Windows service, you must have Administrator privileges. For more information, see About Installing Node Manager as a Windows Service. |
To start the graphical-mode installation process on a Windows platform, follow these steps:
To start the console-mode installation process on a Windows platform, follow these steps:
|
platform920_win32.exe
(BEA Products installation program for WebLogic Server, WebLogic Integration, Workshop for WebLogic Platform, and WebLogic Portal)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: | platform920_win32.exe -mode=console -log=C:\logs\server_install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
After a few moments, a BEA Installer window opens and the installation program begins to install the software.
For details about silent-mode installation, see What Is Silent-Mode Installation?.
To start the silent-mode installation process 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. |
filename
.exe -mode=silent -silent_xml=
path_to_silent.xml
Here, filename.exe
is the name of the BEA software installation file, and path_to_silent.xml
is the full pathname of the silent.xml
file.
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: | platform920_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. |
A BEA 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 BEA Products 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 a Java-based GUI. If the installation program determines that your system cannot support a Java-based GUI, it automatically starts running in console mode. For details, 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 the installation program specific to your platform, for example, platform920_solaris32.bin
.
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: | platform920_solaris32.bin -log=/home/logs/BEA_install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
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 the installation program specific to your platform, for example, platform920_solaris32.bin
.
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: | platform920_solaris32.bin -mode=console -log=/home/logs/BEA_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, platform920_solaris32.bin
, and path_to_silent.xml
is the full pathname of the silent.xml
template file.
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: | platform920_solaris32.bin -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/BEA_install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
A BEA 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 filenames that end in .jar:
To start the graphical-mode installation process 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 server920_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: | server920_generic.jar -log=/home/logs/BEA_install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
The installation program begins to install the software.
To start the console-mode installation process 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.
Here, filename
.jar
is the name of the BEA Products installation file, for example, server920_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 server920_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 silent-mode installation process 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 BEA Products installation file (for example, server
XXX
_generic.jar
, where XXX
represents the version number of the software you are installing) and path_to_silent.xml
is the full path to the silent.xml
file.
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: | server920_generic.jar -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/BEA_install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
A BEA 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.
For details about running the installation program, see one of the following, depending on your selected installation mode: