|
|
The following sections provide information that you need to know before installing your BEA software:
This guide describes using the BEA Products installation program for BEA WebLogic Server, which includes BEA WebLogic Server, BEA WebLogic Portal, and BEA Workshop for Weblogic™.
You can use either of the two BEA Product installation programs to install BEA WebLogic Express™. WebLogic Express is a cost-effective entry point to the WebLogic product family, creating a productive ramp for you to begin using BEAs market-leading application server technology. From WebLogic Express, you can easily upgrade to other products in the WebLogic family, which allows you to take advantage of a wide variety of enterprise-level functionality.
The BEA Products 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 graphical-mode installation, 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 a 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 instructions for 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 in either of two ways: as part of 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 instructions, see Running the Installation Program in Silent Mode.
The BEA Product installer allows you to install the following programs:
Your BEA software is distributed on both the BEA Web site and DVD.
You can download your software from the BEA Web site at
http://commerce.bea.com.
Two installation programs are available for download:
If you purchased your software from your local sales representative, you will find the following items in the product box:
The following sections specify the installation prerequisites:
The system requirements for your installation are given in the following table.
A supported configuration of hardware, operating system, JDK, and database is required. See
Supported Configurations
|
|
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 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 BEA 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. As a general rule, installation programs require approximately 2.5 times the amount of temporary space that is ultimately required by the installed files.
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 BEA software, you are prompted to specify a BEA Home directory. This directory serves as a repository for common files that are used by multiple BEA products installed on the same machine. For this reason, the BEA Home directory can be considered a central support directory for all the BEA products installed on your system.
The files in the BEA Home directory are essential to ensuring that BEA software operates correctly on your system. They perform the following types of functions:
| Note: | On some UNIX platforms, the installation program does not install the JDK. |
During installation of your BEA software, you are prompted to choose an existing BEA Home directory or specify a path to create a new BEA 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 installation directories are not empty, the following messages will be displayed about it with the option to continue installation, or return to the directory selection task:The files and directories in the BEA Home directory are described in the following table.
Contains the software for the Sun JDK if it is installed with your software. The JDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. In this directory name,
<version> indicates the version of the Sun JDK installed on your system, for example jdk150_11.
|
|||
Contains the software for the BEA JRockit JDK installed with your software. The JDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. In this directory name,
<version> indicates the version of the JRockit JDK installed on your system, such as jrockit_150_11.
|
|||
A registry file that contains a persistent record of all BEA 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.
For more information about the BEA registry file, see
“ Using the BEA Registry API” in ISV Partners’ Guide
|
| 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 BEA Home directory, we recommend that you avoid doing so. In almost all situations, a single BEA 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 BEA 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. You are prompted during your initial installation to choose a product installation directory. Table gives information about the product install directories for different products if you accept default on windows:
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 for Weblogic (using the same BEA 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.
A description of the BEA Products directory structure is provided in Understanding the Product Directory Structure.
The BEA Products installation program provides two types of installation: Complete and Custom.
In a complete installation for WebLogic Server and BEA Workshop for WebLogic, following components of BEA products are installed:
In a complete installation for WebLogic Server, BEA Workshop for WebLogic, and WebLogic Portal, the following components of BEA products are installed:
On Windows systems, two JDKs are installed: BEA JRockit 1.5.0 JDK and the Sun JDK 1.5.0.
You cannot install the following sub-components if you choose complete installation
In a custom installation, you have the following options:
On Windows systems only, two JDKs are installed: the BEA JRockit 1.5.0 JDK and the Sun JDK 1.5.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:
platform<version>_win32.exe -log=C:\logs\server_install.log
The 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.
For information about upgrading your software with maintenance patches and service packs, if available, see Installing Maintenance Updates and Service Packs
| Note: | If you are installing this version of WebLogic Server into an existing BEA Home directory that contains an older installation of WebLogic Server, all custom security providers that reside in the default location, WL_HOME\server\lib\mbeantypes, where WL_HOME specifies the root directory of older installation, are upgraded automatically. If all of your custom security providers reside in the default location, then the security provider upgrade step is complete, and you do not have to perform any of the additional steps in
“Upgrading a Security Provider” in Upgrading WebLogic Application Environments. |
| Note: | You can verify that a custom security provider has been upgraded by locating the upgraded security provider, security_provider_name_Upgraded, in the WL_HOME\server\lib\mbeantypes directory, where WL_HOME specifies the root directory of the current installation and security_provider_name specifies the name of the security provider. |
You can upgrade your WebLogic Platform installation by using the downloadable upgrade installer.
When a maintenance release is available, you can download a package upgrade installer from the BEA Customer Support Web site at http://support.bea.com.
Two package upgrade installers are available: a WebLogic Platform upgrade installer for all components of WebLogic Platform, and a WebLogic Server upgrade installer, which includes WebLogic Server and WebLogic Workshop only. Both programs provide the same functionality. The procedures provided in this section apply to both installers.
These installers upgrade only those components that are already installed on your system. For example, if your installation consists of the WebLogic Server, WebLogic Workshop and WebLogic Portal components of WebLogic Platform 10.0, the upgrade installer upgrades only those components.
The upgrade installer can be run in the following modes on both UNIX and Windows platforms:
Graphical mode: For instructions, see Using the Upgrade Installer in Graphical Mode on page 3-6.
Console mode: For instructions, see Using the Upgrade Installer in Console Mode on page 4-8.
Silent mode: For instructions, see Using the Upgrade Installer in Silent Mode on page 5-8.
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.
The upgrade installation programs require 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 WebLogic Platform installation program does not include the Java 2 SDK. Filenames for these installation programs end in .jar. To run the .jar installation programs, you must have an appropriate version of a Java 2 SDK installed on your system, and include the bin directory of the Java 2 SDK at the beginning of your PATH system variable.
| Note: | It is important that you use an SDK because the installation process resets the JAVA_HOME, and related variables to point to this directory. All scripts installed with WebLogic Platform use this SDK by default, including scripts to start sample applications, the Configuration Wizard, and other WebLogic development tools. |
|