|
|
This section discusses the following topics:
This guide describes how to use the installation program to install WebLogic products.
The installation program can be used in the following modes:
Graphical-mode installation is an interactive, GUI-based method for installing your software. It can be run on both Windows and UNIX systems. For installation procedures, see Running the Installation Program in Graphical Mode.
| Note: | If you want to run the installation program in graphical-mode, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX systems do. If you attempt to start the installation program in graphical mode on a system that cannot support graphical display, the installation program automatically starts console-mode installation. |
Console-mode installation is an interactive, text-based method for installing your software from the command line, on either a UNIX system or a Windows system. For information about using this method, see Running the Installation Program in Console Mode.
Silent-mode installation is a non-interactive method of installing your software that requires the use of an XML properties file for selecting installation options. You can run silent-mode installation from either a script or from the command line. Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many machines. For more information about the silent mode installation, see Running the Installation Program in Silent Mode.
The installable product components vary depending on the installer that you are using. For example, the WebLogic Server Net installer includes the following components:
For more information about the product components, see Selecting the WebLogic Server Components in Getting Started With Installation.
You can download your software from the Oracle Web site.
The following types of installers are available for download:
The Net installer allows you to avoid installing the components that are not required in the specific environment in which the product is being used. For example, an experienced developer who has Eclipse and a suitable Java Runtime may need only the Core Application Server, the WebLogic JDBC drivers, and the examples. An administrator may choose to install only the Core Application Server, Administration Console, Configuration Wizard and Upgrade Framework, Web Server plug-ins, the third-party JDBC drivers, and the JRockit JDK.
Before the download begins, the net installer prompts you to provide the following information:
The net installer supports standard resume processing in the case of interrupted downloads. If the download is interrupted for any reason, either manually or by an unplanned network interruption, you can resume the download from the point at which it was interrupted. When the download is complete, the installation program performs an integrity check on the archive files that were downloaded to your system to verify that the files are downloaded correctly.
The WebLogic Server installation program contains WebLogic Server and related samples, Workshop and related samples as described in Installable Product Components, and the JRockit SDK and Sun JDK (for Windows and Linux platforms only).
| Note: | If you are planning to install the software in silent mode, you must download the package installer. Silent-mode installation is not supported by the net installer. |
The following sections describe the installation prerequisites:
The system requirements for running the installation program are listed in the following table.
A supported configuration of hardware, operating system, JDK, and database specific to the product you are installing. See
Supported Configurations.
|
|
The 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 install a JDK. Filenames for these installation programs end in .jar. To run the .jar installation programs, you must have the appropriate version of the JDK installed on your system, and include the bin directory of the JDK at the beginning of the PATH variable definition. It is important that you use a JDK because the installation process assigns values to JAVA_HOME and related variables to point to the JDK directory.
|
The installation program uses a temporary directory into which it extracts the files necessary to install the software on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java Run-time Environment (JRE) bundled with the installation program and an uncompressed copy of the JRE that is expanded into the temporary directory. The extracted files are deleted from the temporary directory at the end of the installation process. The files in the temporary directory require approximately 2.5 times the space that is ultimately required for the installation.
By default, the installation program uses the following temporary directories:
| Note: | If you do not have enough temporary space to run the installation program, you are prompted to specify an alternate directory or exit the installation program. |
To make sure that you have adequate temporary space, you may want to allocate an alternate directory for this purpose. To do so, follow the instructions provided in the following table.
When you are installing the software as a user with Administrator privileges, you are presented with the option to create the Start menu shortcuts in the All Users folder, or in the Local User’s Start menu folder. The following table describes the options available.
If a user without Administrator privileges installs the software, the Start menu entries are created in the user’s local Start menu folder.
During the installation process, you need to specify locations for the following directories:
When you install your WebLogic software, you are prompted to specify a home directory. This directory serves as a repository for common files that are used by multiple WebLogic products installed on the same machine. For this reason, the home directory can be considered a central support directory for all the WebLogic products installed on your system.
The files in the home directory are essential to ensuring that WebLogic software operates correctly on your system. They facilitate checking of cross-product dependencies during installation.
When you are installing WebLogic software, you are prompted to choose an existing home directory or specify a path to create a new home directory. If you choose to create a new directory, the installation program automatically creates it for you.
CLASSPATH may not be resolved properly.registry.xml, or if any of the product installation directories are not empty, the following messages will be displayed:The directories in the home directory vary depending on the installer that you are using. For example, the WebLogic Server installer creates the directories listed in the following table if you have selected all the components for installation.
Contains utilities that are used to support the installation of all WebLogic installed in this home directory.For more information on installing patches and maintenance packs, see
Installing Patches and Maintenance Packs Using Smart Update.
|
|||
A registry file that contains a persistent record of all WebLogic products installed on the target system. This registry contains product-related information, such as version number, service pack number, and location of the installation directory.
|
|||
| Note: | The directory user_projects does not contain anything when the product is installed on the disk. It is used as the default location for your files when you create domains at the location. |
Although it is possible to create more than one home directory, We recommend that you avoid doing so. In almost all situations, a single home directory is sufficient. There may be circumstances, however, in which you prefer to maintain separate development and production environments, with a separate product stack for each. With two directories, you can update your development environment (in a home directory) without modifying the production environment until you are ready to do so.
The product installation directory contains all the software components that you choose to install on your system, including program files and examples.
For example, the default installation directories for components of WebLogic Server are shown in the Table 2-4
The installation program installs the software components in a product installation directory represented by the WL_HOME variable. If, during your initial installation, you choose to install WebLogic Server only, and not all of the products available for installation, and you later decide to install additional products, such as Workshop (using the same home directory), you are not prompted, during the subsequent installations, to specify a product installation directory. The installation program detects the WL_HOME directory and installs the additional products under it.
The installation program provides two types of installation: Complete and Custom.
For a description of the software components provided with your product distribution, see Installable Product Components.
Sample domains preconfigured to use the PointBase database are created only for the installed components.
On Windows and LINUX systems, two JDKs are installed: the JRockit 1.6.0 JDK and the Sun JDK 1.6.0.
If you launch the installation from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log stores messages about events that occur during the installation process, including informational, warning, error, and fatal messages. This type of file can be especially useful for silent installations.
| Note: | You may see some warning messages in the installation log. However, unless a fatal error occurs, the installation program completes the installation successfully. The installation user interface indicates the success or failure of each installation attempt, and the installation log file includes an entry indicating that the installation was successful. |
To create a verbose log file during installation, include the -log=full_path_to_log_file option in the command line.
For example, to create a verbose log file for the WebLogic Server net installer, enter:
net_server103_win32.exe -log=C:\logs\server_install.logThe path must specify a file. You cannot create a folder simply by including a name for it in a pathname; your path should specify only existing folders. If your path includes a nonexistent folder when you execute the command, the installation program does not create the log file.
|