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://edocs.bea.com/platform/suppconfigs/configs_al10gr3/oer10gr3/oer10gr3.html
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. |
For information on supported application servers and databases, see Oracle Enterprise Repository 3.0 Supported Configurations.
Note: | If the installation process is aborted before it is completed, manually clear the database before running the installer again. The installer does not clear data from the database when an installation is aborted. The existing data causes an error when the installer runs for the second time. |
This section describes how to start the installation program on Windows Platforms:
To start the graphical-mode installation process on a Windows platform, perform the following steps:
filename
.exe
[-log=full_path_to_log_file]
OER10XX_win32.exe [-log=full_path_to_log_file]
Note: |
To start the console-mode installation process on a Windows platform, perform the following steps:
filename.exe -mode=console
OER10XX_win32.exe -mode=console
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: |
OER10XX_win32 -mode=console -log=C:\logs\OER_install.log
For more information on generating a verbose log, see Generating a Verbose Installation Log.
After a few moments, a 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 installation in silent-mode 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, Oracle recommends 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 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: | OER10XX_win32.exe -mode=silent -silent_xml=C:\silent.xml -log=C:\logs\OER_install.log |
For more information, see Generating a Verbose Installation Log.
A 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 in the Silent Mode
The Oracle Enterprise Repository 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.
Note: | 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. |
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 in the Silent Mode. The section describes how to start the installation using the following types of installers:
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 using the installation files with names ending in .bin
, do the following:
Note: | OER10XX_linux32.bin -log=/home/logs/OER_install.log |
Note: | For more information, see Generating a Verbose Installation Log. |
To continue the installation in the graphic mode, see Running the Installation Program in Graphical Mode.
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,
chmod a+x OER10XX_linux32
.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: |
OER10XX_linux32
.bin -mode=console -log=/home/logs/OER_install.log
For more information on generating a verbose log, 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, Oracle recommends 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,
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: |
OER10XX_linux32
.bin -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/OER_install.log
For more information on generating a verbose log, see Generating a Verbose Installation Log.
A Installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.
For more information on Silent-Mode installation, see Running the Installation in the 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:
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 [-log=full_path_to_log_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: | al30_generic.jar -log=/home/logs/OER_install.log |
For more information on generating a verbose log, see Generating a Verbose Installation Log.
The installation program begins the graphical mode.
To start the installation in the console mode using the installation files with names ending in .jar
, follow these steps:
PATH=<JAVA_HOME>/bin:$PATH
export PATH
where, <JAVA_HOME>
represents the full path to the JDK directory.
java -jar filename.jar -mode=console [-log=full_path_to_log_file]
where, filename.jar
is the name of the installation file, for example,
oer_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 oer_generic.jar -mode=console -log=/home/logs/OER_install.log |
Note: | For more information on generating a verbose log, 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 you specify in 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, Oracle recommends that you create a log file when you start the installation. |
PATH=<JAVA_HOME>/bin:$PATH
export PATH
where, <JAVA_HOME>
is the full path of the JDK directory.
java -jar filename.jar
-mode=silent -silent_xml=/path_to_silent.xml [-log=full_path_to_log_file]
where, filename.jar
is the name of the installation file for example,
oerXX_generic.jar
where, XX 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: | oer_generic.jar -mode=silent -silent_xml=/home/silent.xml -log=/home/logs/OER_install.log |
For more information on generating a verbose log, see Generating a Verbose Installation Log.
A Installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.
For more information on silent-mode installation, see Running the Installation in the Silent Mode.
For details about running the installation program, see one of the following, depending on your selected installation mode: