Oracle® Fusion Middleware

Installation Guide for Oracle WebLogic Server

11g Release 1 (10.3.1)

E14142-01

May 2009

This document describes how to install Oracle WebLogic Server.

Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server, 11g Release 1 (10.3.1)

E14142-01

Copyright © 2007, 2009, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Document Organization

- Documentation Accessibility

- Conventions

1 Preparing for Installation

- 1.1 Installation Modes

- 1.2 Installable Product Components

- 1.3 Product Distribution

- 1.4 Installation Prerequisites

- 1.4.1 System Requirements

- 1.4.2 Temporary Disk Space Requirements

- 1.4.3 Administrator Privileges

- 1.5 Selecting Directories for Installation

- 1.5.1 Choosing a Home Directory

- 1.5.2 Choosing a Product Installation Directory

- 1.6 Choosing the Type of Installation

- 1.7 Generating a Verbose Installation Log

2 Starting the Installation Program

- 2.1 Before You Start the Installation Program

- 2.2 Starting the Installation Program on Windows

- 2.2.1 Starting the Installation Program in Graphical Mode

- 2.2.2 Starting the Installation Program in Console Mode

- 2.2.3 Starting the Installation Program in Silent Mode

- 2.3 Starting the Installation Program on UNIX

- 2.3.1 Starting the Installation Program on UNIX Using .bin Installers

- 2.3.2 Starting the Installation Program on UNIX Using .jar Installers

3 Running the Installation Program in Graphical Mode

4 Running the Installation Program in Console Mode

5 Running the Installation Program in Silent Mode

- 5.1 What Is Silent-Mode Installation?

- 5.2 Using Silent-Mode Installation: Main Steps

- 5.3 Creating a silent.xml File for Silent-Mode Installation

- 5.4 Exit Codes for Silent Mode Installation

6 Post-Installation Information

- 6.1 Using QuickStart

- 6.2 Determining Which JDK Version You Are Using

- 6.3 Creating an Oracle WebLogic Server Starter Domain

- 6.4 Understanding the Windows Shortcuts

- 6.5 Supported Configurations

- 6.6 Upgrading Oracle WebLogic Server

- 6.7 Installing Patches and Maintenance Updates

7 Uninstalling the Software

- 7.1 About the Uninstallation Program

- 7.2 Uninstalling Your Software in Graphical Mode

- 7.3 Uninstalling Your Software in Console Mode

- 7.4 Uninstalling Your Software in Silent Mode

- 7.5 Reinstalling Your Software

A Sample Silent.xml File for Silent-Mode Installation

Preface

This document describes how to use the WebLogic installation program on Windows and UNIX platforms.

Audience

This document is intended for system administrators or application developers who are installing the WebLogic software. It is assumed that readers are familiar with web technologies and have a general understanding of Windows and UNIX platforms.

Document Organization

The document is organized as follows:

- Chapter 1, "Preparing for Installation" describes the basic information you must know before installing your software.

- Chapter 2, "Starting the Installation Program" describes how to start the installation program in graphical, console, and silent modes on Windows and UNIX platforms.

- Chapter 3, "Running the Installation Program in Graphical Mode" describes how to install your software on Windows and UNIX platforms, using a Java-based graphical user interface (GUI).

- Chapter 4, "Running the Installation Program in Console Mode" discusses how to install your software on Windows and UNIX platforms, using a text-based interface.

- Chapter 5, "Running the Installation Program in Silent Mode" describes how to install your software, without user intervention by using an XML properties file to specify the installation options.

- Chapter 6, "Post-Installation Information" provides information about post-installation tasks.

- Chapter 7, "Uninstalling the Software" provides procedures for uninstalling your software in graphical, console, and silent modes.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Preparing for Installation

This section discusses the following topics:

- Section 1.1, "Installation Modes"

- Section 1.2, "Installable Product Components"

- Section 1.3, "Product Distribution"

- Section 1.4, "Installation Prerequisites"

- Section 1.5, "Selecting Directories for Installation"

- Section 1.6, "Choosing the Type of Installation"

- Section 1.7, "Generating a Verbose Installation Log"

1.1 Installation Modes

The installation program can be used in the following modes:

- Graphical mode
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 Chapter 3, "Running the Installation Program in Graphical Mode."

Note:
To be able 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
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 Chapter 4, "Running the Installation Program in Console Mode."

- Silent 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 Chapter 5, "Running the Installation Program in Silent Mode."

1.2 Installable Product Components

The product components that you can install vary depending on the installer that you are using.

For example, the Oracle WebLogic Server net installer for Windows includes the following components:

- Oracle WebLogic Server

- Core Application Server

- Administration Console

- Configuration Wizard and Upgrade Framework

- Web 2.0 HTTP Pub-Sub Server

- WebLogic JDBC Drivers

- Third Party JDBC Drivers

- WebLogic Server Clients

- WebLogic Web Server Plugins

- UDDI and XQuery Support

- Server Examples

- Oracle Enterprise Pack for Eclipse

For more information about the product components, see "Selecting the WebLogic Server Components" in Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server.

1.3 Product Distribution

You can download your software from the http://edelivery.oracle.com/ Oracle Web site.

The following types of installers are available for download:

- Net installer (recommended): This type downloads a small setup file that enables you to select the components to install on your system. The installer then downloads only the components you select. The net installer eliminates the need to download the entire product before installing it, and thereby reduces the time needed to complete the download, the disk space, and also the RAM required for installation.
The net installer enables 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:

- Storage directory: The installation program downloads an archive file to your system for each component that you choose to install. By default, these archive files are downloaded to the temporary directory on your system. You can specify an alternate directory on your system for these files; they need not be collocated with the installation setup file, or with the installed software. If you do not specify an alternate directory, your temporary directory must have sufficient space to accommodate the archive files and the installation program. For more information about temporary space required by the installation program, see Section 1.4.2, "Temporary Disk Space Requirements." To conserve disk space, you can also specify that the downloaded files should be removed from your system after the installation is complete.

- HTTP Proxy: If you want to download these files using an HTTP proxy, you must specify the host address and port numbers for the proxy server.

- Proxy authentication: If the HTTP proxy you are using requires server-side HTTP authentication, you must enter your username and password.
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.

- Package installer: This type of installer downloads a standalone version of the installation program.
For example, the Oracle WebLogic Server with Workshop for WebLogic installer contains Oracle WebLogic Server and related samples, Workshop and related samples, 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.

- Generic installers (net and package): This type of installer is a .jar file. It is the same as the package and net installers, except that it does not include JDKs. You can use this type of installer to install the product on UNIX machines on which Java is already installed. For more information, see Section 2.3.2, "Starting the Installation Program on UNIX Using .jar Installers."

1.4 Installation Prerequisites

The following sections describe the installation prerequisites:

- Section 1.4.1, "System Requirements"

- Section 1.4.2, "Temporary Disk Space Requirements"

- Section 1.4.3, "Administrator Privileges"

1.4.1 System Requirements

The system requirements for running the installation program are listed in the following table.

Table 1-1 System Requirements

Component

Requirement

Platform configuration

A supported configuration of hardware, operating system, JDK, and database specific to the product you are installing.

For information about other prerequisites and recommendations, such as recommended versions of the JDK, see the Oracle Fusion Middleware Supported System Configurations page at http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html document.

Processor

1-GHz CPU

Memory

A Minimum of 1 GB RAM, although we recommend 2 GB of RAM.

Color bit depth display and size

For Graphical User Interface (GUI) mode installation, 8-bit color depth (256 colors) is required.

For console-mode and silent-mode installation, there is no color bit depth requirement.

JDK

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 file names ending in .bin). For other UNIX platforms, the installation program does not install a JDK. File names 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.

1.4.2 Temporary Disk Space Requirements

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 after 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:

- Windows platforms: directory referenced by the TMP system variable

- UNIX platforms: system-dependent temporary directory

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.

Table 1-2 Setting Up the Temporary Directory

Platform

Procedure

Windows

Do one of the following:

- Set the TMP system variable to a directory of your choice.

- If you run the installation program from the command line, include the -Djava.io.tmpdir=tmpdirpath option, replacing tmpdirpath with the full path of the directory you want to designate as a temporary storage area for the installation program.
For example, to set up the temp directory while running the Oracle WebLogic Server net installer for Windows, execute this command:

net_wls1031_win32.exe -mode=console -Djava.io.tmpdir=C:\Temp

UNIX

Enter the following option on the command line when you start the installation program:

-Djava.io.tmpdir=tmpdirpath

Here, tmpdirpath is the full path of the directory you want to designate as a temporary storage area for the installation program.

1.4.3 Administrator Privileges

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.

Option

Behavior

All Users

All users registered on the machine are provided with access to the installed software. Subsequently, if users without Administrator privileges use the Configuration Wizard from this installation to create domains, Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired.

Local user

Other users registered on this machine do not have access to the Start menu entries for this installation.

If a user without Administrator privileges installs the software, the Start menu entries are created in the user's local Start menu folder.

1.5 Selecting Directories for Installation

During the installation process, you must specify locations for the following directories:

- Section 1.5.1, "Choosing a Home Directory"

- Section 1.5.2, "Choosing a Product Installation Directory"

1.5.1 Choosing a Home Directory

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 home directory. If you choose to create a directory, the installation program automatically creates it for you.

Installation Considerations

Oracle recommends the following:

- Do not exceed a maximum of 12 characters when naming your home directory. If the name of this directory has more than 12 characters and if there are spaces in the directory name, the CLASSPATH may not be resolved properly.

- You can install only one instance of each version of a WebLogic product in a single home directory.
For example, you can install only one instance of the current version of Oracle WebLogic Server in a home directory, but that home directory may also contain an instance of a previous version of Oracle WebLogic Server.

- If the home directory is not empty and it does not contain registry.xml, or if any of the product installation directories are not empty, the following messages is displayed:

- For home directory selection task: Middleware home directory is not empty. Proceed with installation?

- For product installation directory selection task: One or more installation directories are not empty. Proceed with installation?

Functions of the Home Directory

The directories in the home directory vary depending on the installer that you are using.

For example, the Oracle WebLogic Server with Workshop for WebLogic installer creates the directories listed in the following table if you have selected all the components for installation.

Table 1-3 Directory Description for Middleware Home

Component

Description

jdkversion

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.

jrockit_version

(Windows and Linux only)

Contains the software for the JRockit JDK installed with your software. The JDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications.

logs

Contains a history file that contain information about installation and uninstallation for the home directory.

modules

Contains the modules installed in the Home Directory.

utils

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 Oracle Smart Update Installing Patches and Maintenance Packs.

wlserver_version

This directory contains the following directories:

- common

- samples

- server

- uninstall

workshop_version

This directory contains the following directories:

- common

- Samples

- uninstall

- weblogic-beehive

- workshop4WP

.home

Contains the information about the home directory.

ocm.rsp

The response file that contains information about the Oracle Configuration Manager (OCM) installation.

registry.xml

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: Do not edit this file manually. Doing so may cause operating problems for the currently installed WebLogic products, or result in installation problems when future products or maintenance upgrades are installed.

registry.dat

This is an encrypted file of registry.xml file.

Note:
The user_projects folder is created in the middleware home directory only when you create domains and it is the default location for your domain files.

Creating Multiple home Directories

Although it is possible to create more than one home directory, We recommend that you avoid doing so. In most 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.

1.5.2 Choosing a Product Installation Directory

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 directory for Oracle WebLogic Server is C:\Oracle\MW_HOME\wlserver_version.

The installation program installs the software components in a product installation directory represented by the MW_HOME variable.

1.6 Choosing the Type of Installation

The installation program provides two types of installation: Typical and Custom.

- In a typical installation, all of the components that are included in the installation program are installed.

- In a custom installation, you can choose the software components you want to install on your system.

For a description of the software components provided with your product distribution, see Section 1.2, "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.

1.7 Generating a Verbose Installation Log

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 (informational, warning, error, and fatal) about events that occur during the installation process. This type of file can be especially useful for silent installations.

Note:
You may see a few warning messages in the installation log. However, unless a fatal (irrecoverable) 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 Oracle WebLogic Server net installer for Windows, enter:

net_wls1031_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.

2 Starting the Installation Program

The following sections describe how to start the installation program on Windows and UNIX platforms:

- Section 2.1, "Before You Start the Installation Program"

- Section 2.2, "Starting the Installation Program on Windows"

- Section 2.3, "Starting the Installation Program on UNIX"

2.1 Before You Start the Installation Program

Before you start installing the software, review the following information:

- Make sure that you are installing your product on a supported hardware or software configuration. For more information, see the Supported Configurations document.

- Read Chapter 1, "Preparing for Installation."

- You cannot reinstall a product on top of a previously installed version of the same product—in the same home directory or in the same file location. You can, however, add products and product components to an existing installation.
For example, you can install WebLogic Server during one installation, and Workshop during a separate installation. However, to reinstall the same version of a product, you must first uninstall the previous installation, as described in Chapter 7, "Uninstalling the Software."

- If you are adding components to an existing installation of WebLogic Server, you should shut down any running servers before starting the installation.

2.2 Starting the Installation Program on Windows

The following sections describe how to start the installation program on a Windows platform:

- Section 2.2.1, "Starting the Installation Program in Graphical Mode"

- Section 2.2.2, "Starting the Installation Program in Console Mode"

- Section 2.2.3, "Starting the Installation Program in Silent Mode"

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.

2.2.1 Starting the Installation Program in Graphical Mode

To start the installation program in graphical-mode on a Windows platform, follow these steps:

1. Log in to the Windows system.

2. Go to the directory where you have downloaded the installation program.

3. Go to the directory that contains the installation program.

4. Double-click the installation file.
For example, the name of the installation program for the Oracle WebLogic Server net installer for Windows is net_wls1031_win32.exe.

The installation program begins to install the software.

5. Proceed to Chapter 3, "Running the Installation Program in Graphical Mode."

2.2.2 Starting the Installation Program in Console Mode

To start the installation program in console-mode on a Windows platform, follow these steps:

1. Log in to the target Windows system.

2. Open a command prompt window.

3. Go to the directory that contains the installation program.

4. Launch the installation by entering the name of the installation program.
For example, to start the Oracle WebLogic Server net installer for Windows in console mode, enter

net_wls1031_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.
For more information, see Section 1.7, "Generating a Verbose Installation Log."

After a few moments, the installation program begins to install the software.

5. Proceed to Chapter 4, "Running the Installation Program in Console Mode."

2.2.3 Starting the Installation Program in Silent Mode

For information about silent-mode installation, see Section 5.1, "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:

1. Log in to the Windows system.

2. Create a 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 Section 5.3, "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.

3. Open a command prompt window.

4. Go to the directory that contains the installation program.

5. Start the installer.
For example, to launch the Oracle WebLogic Server installer on Windows, enter:

wls1031_win32.exe -mode=silent -silent_xml=path_to_silent.xml

Here, path_to_silent.xml is the full path 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.
For more information, see Section 1.7, "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 Chapter 5, "Running the Installation Program in Silent Mode."

2.3 Starting the Installation Program on UNIX

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 file names ending in .bin). For other UNIX platforms, the installation program does not include a JRE. File names 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 Java-based GUIs. If the installation program determines that your system cannot support Java-based GUIs, it automatically starts running in console mode.

2.3.1 Starting the Installation Program on UNIX Using .bin Installers

The following sections describe how to start the installation program on UNIX platforms, by using files with the .bin extension:

Starting .bin Installation Programs in Graphical Mode

To start the graphical-mode installation process with .bin installation files, follow these steps:

1. Log in to the target UNIX system.

2. Go to the directory that contains the installation program.

3. Launch the installation by entering the following command:
chmod a+x file_name.bin ./file_name.bin

file_name.bin is the name of your installation program. For example, for Oracle WebLogic Server 10.3, the name of the net installer file for Solaris is net_wls1031_solaris32.bin.

The installation program begins to install the software.

4. Proceed to Chapter 3, "Running the Installation Program in Graphical Mode."

Starting .bin Installation Programs in Console Mode

To start the console-mode installation process with .bin installation files, follow these steps:

1. Log in to the target UNIX system.

2. Go to the directory that contains the installation program.

3. Launch the installation by entering the following command:
chmod a+x file_name.bin ./file_name.bin -mode=console

4. Proceed to Chapter 4, "Running the Installation Program in Console Mode."

Starting .bin Installation Programs in Silent Mode

To start the silent-mode installation process by using .bin installation files, follow these steps:

1. Log in to the target UNIX system.

2. Create a 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 Section 5.3, "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.

3. Go to the directory that contains the installation program.

4. Launch the installation program by entering the following command:
chmod a+x file_name.bin ./file_name.bin -mode=silent -silent_xml= path_to_silent.xml

file_name.bin is the name of the installation file.

path_to_silent.xml is the full path of the silent.xml file.

An Installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.

For more information about silent-mode installation, see Chapter 5, "Running the Installation Program in Silent Mode."

Note:
You can include the -log=full_path_to_log_file option in the command line to create a verbose installation log.
For more information, see Section 1.7, "Generating a Verbose Installation Log."

2.3.2 Starting the Installation Program on UNIX Using .jar Installers

The following sections describe how to start the installation program on UNIX platforms by using generic (.jar) installers:

Starting .jar Installation Programs in Graphical-Mode

To start the installation program in graphical-mode for installation files with names ending in .jar, perform the following steps.

1. Log in to the target UNIX system.

2. Add the bin directory of the appropriate JDK to the beginning of the PATH variable definition on the target system.
For example: PATH=$JAVA_HOME/bin:$PATHexport PATH

3. Go to the directory where you downloaded the installation program.

4. Launch the installation program by entering the following command:
java -jar net_wlsversion_generic.jar

The installation program begins to install the software.

5. Proceed to Chapter 3, "Running the Installation Program in Graphical Mode."

Starting .jar Installation Programs in Console-Mode

To start the installation program in console-mode for installation files with names ending in .jar, follow these steps:

1. Log in to the target UNIX system.

2. Add the bin directory of the appropriate JDK to the beginning of the PATH variable definition on the target system.
For example: PATH=$JAVA_HOME/bin:$PATHexport PATH

3. Go to the directory where you downloaded the installation program.

4. Launch the installation by entering the following command:
java -jar <file_name.jar> -mode=console

file_name.jar is the name of the installation file.

5. Proceed to Chapter 4, "Running the Installation Program in Console Mode."

Starting .jar Installation programs in Silent-Mode

To start the installation program in silent-mode for installation files with names ending in .jar, follow these steps:

1. Log in to the target UNIX system.

2. Create a 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 Section 5.3, "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.

3. Add the bin directory of the appropriate JDK to the beginning of the PATH variable definition on the target system.
For example: PATH=$JAVA_HOME/bin:$PATHexport PATH

4. Go to the directory that contains the installation file.

5. Launch the installation by entering the following command:
java -jar file_name.jar -mode=silent -silent_xml=/path_to_silent.xml

file_name.jar is the name of the installation file

path_to_silent.xml is the full path to the silent.xml file.

An Installer window is displayed, indicating that the files are being extracted.

For more information, see Chapter 5, "Running the Installation Program in Silent Mode."

Notes:
You can include the -log=full_path_to_log_file option in the command line to create a verbose installation log. For more information, see Section 1.7, "Generating a Verbose Installation Log."
When you run the generic upgrade installer, ensure that the heap size is adequate, by including the -Xmx<size>[g|G|m|M|k|K] option in the command.

3 Running the Installation Program in Graphical Mode

Start the installation program as described in Chapter 2, "Starting the Installation Program."

The installation wizard displays a series of windows which are described in Table 3-1.

Table 3-1 Running the Installation Program in Graphical Mode

In this window

Perform the following action

Welcome

Click Next to proceed with the installation.

You may cancel the installation at any time by clicking Exit.

Choose Middleware Home Directory

Specify the home directory that will serve as the central support directory for all products installed on the target system.

- If you already have a home directory on your system, you can select that directory (recommended) or create a home directory.

- If you choose to create a directory by typing a new directory name in the Middleware Home Directory field, the installation program automatically creates one for you. You can also click Browse and select a directory from the Middleware Home Directory selection window.

Click Next to continue. The Specify Download Options window is displayed.

For details about the home directory, see Section 1.5.1, "Choosing a Home Directory."

Register for Security Updates

Specify whether you want to register the Oracle WebLogic Server installation with My Oracle Support. By registering, Oracle Support notifies you immediately of any security updates that are specific to your installation.

If you want to register your installation, enter your e-mail address and your My Oracle Support password. If you want to decline registration, deselect "I wish to receive security updates via My Oracle Support" and confirm your choice.

If you have not registered with Oracle Support, go to the My Oracle Support Web site, https://metalink.oracle.com/CSP/ui/index.html, and register to obtain a My Oracle Support account.

For more information about the capabilities of registering your installation with My Oracle Support, see Oracle Configuration Manager Installation and Administration Guide.

Specify Download Options

Note: This window is displayed only if you are using the net installer.

Indicate your preferences for downloading the software as follows and then click Next to continue. The Choose Install Type window is displayed.

- Storage Directory: Specify a storage directory to which you want to download the software components. The installation program downloads an archive file to your system for each component that you choose to install. You can choose any location on your system for these files. The directory you choose need not be the same as the directory that contains the installer or the installed software.

Note: If you have specified a storage directory, that directory name is displayed. If you have not specified a storage directory, the installer specifies the system's temporary directory as the default. Make sure that your temporary directory has sufficient space to accommodate the archive files and the installation program. For more information about temporary space required by the installation program, see Temporary Disk Space Requirements.

- Remove downloaded files when installer exits: Select this option if you want the installation program to delete the downloaded files after the installation is complete. If you do not select this option, the downloaded files are saved to the storage directory you specified.

- Use HTTP Proxy: Select this option if you want to use an HTTP Proxy server for the download. To use an HTTP Proxy server, you must provide the following information:
Host: Enter the name or IP address of the proxy server.

Port: Enter the port number of the proxy server.

- Use Authentication: Select this option if the HTTP Proxy server you are using requires server-side authentication. If you select this option, you must provide the following information:
Username: Enter a valid username required by the proxy server.

Password: Enter a valid password for the user.

Choose Install Type

This window is displayed only during an initial installation.

Select the installation type:

- Typical: All the software components included in your installation program, are installed on your system. Sample domains are preconfigured for use with the PointBase database during installation, allowing you to execute the samples when the installation is complete.

- Custom: You select the software components to be installed. On Windows systems, you also have the option to install Oracle WebLogic Server Node Manager as a Windows service.

Click Next. The Choose Product and components window is displayed

For more information, see Section 1.6, "Choosing the Type of Installation."

Choose Products and Components

This window is displayed only under the following conditions:

- You selected Custom installation in the Choose Install Type window.

- You are adding components to an existing installation.

Specify the components to be installed by selecting or clearing the appropriate check boxes. This window displays a tree-view of all the components available for installation.

When you select or clear a component at the folder level, all subcomponents are selected or cleared accordingly.

If any components are installed on your system, the corresponding check boxes are grayed out.

This window also displays the description and the approximate installed size of the selected component.

Note: When you select or deselect components, the installation program checks for dependencies between the components and automatically modifies the list of selected components. For example, if you deselect Oracle WebLogic Server, the components that require Oracle WebLogic Server are also deselected.

For details about the components available for installation on your system, see Section 1.2, "Installable Product Components."

JDK Selection

This window is displayed only if you have opted for custom installation.

This window displays a list of JDKs. This list contains JDKs that are available for (and common across) previous installations of all the selected components.

Select the JDK that you want to install with the product.

You can also browse for and select a local JDK (at least 1.6.0_05) installed on your machine.

This window also displays the approximate installed size of the highlighted JDK, the total installed size of all the selected JDKs, and the total installed size of all the components.

Note: Sun has addressed multiple Java security vulnerabilities affecting the following Sun Java Runtime Environments.

- JDK and JRE 6 Update 10 and earlier

- JDK and JRE 5.0 Update 16 and earlier

If you have already installed any of the above versions of JDK, you must upgrade it to the latest version of Sun Java Runtime Environment by selecting the latest JDK version in the installer.

Downloading Archive Information

This window is displayed only if you are using the net installer.

No action required.

This window is displayed when the preliminary archive information is downloaded to your system. This window is followed by the Archive Download window.

Archive Download

This window is displayed only if you are using the net installer.

- Indicate whether you want to proceed with the installation automatically after the download is complete by selecting or clearing the appropriate check box. This check box is selected by default. If you clear it, you must click Next when the download is complete to proceed with the installation.

- To interrupt the download for any reason, click Pause. The Pause button is replaced by a Resume button. If you click the Pause button, the download is discontinued, and you can go back to the previous windows and change the selections. Click Resume if you are ready to proceed with the download.

Archive Integrity Check

This window is displayed only if you are using the net installer.

- No action required. This window is displayed while the installation program verifies that the component archive files have been downloaded successfully.

Install Eclipse Location Options

This window is displayed only in the following situations:

- You are performing a complete installation using the generic installer.

- You are performing a custom installation and have selected the Workshop component.

Select whether you want to install Eclipse or you want the Workshop for WebLogic to use a pre-existing Eclipse installation.

- By default, the Install Eclipse option is selected and eclipse is installed at MW_HOME\tools\eclipse_pkgs\2.0\eclipse_3.3.2\eclipse, unless you are running a generic installer.
If you are running the generic installer, Use Existing Eclipse is the only available option. Eclipse is platform-specific, so you must download and install a copy of Eclipse 3.3.2 and WTP 2.0.3 for your platform before running the generic installer.

- If you select Use Existing Eclipse option, specify the path of an existing Eclipse home (the parent directory of the eclipse plugins and features).

Choose Product Installation Directories

This window is not displayed if you are adding components to an existing installation. Instead, you are prompted to confirm the product installation directory. If you do so, the selected components are installed in the product installation directory you specified during the initial installation.

Specify the directories in which you want to install the products, and click Next. You can accept the default product directories or specify new directories.

If you choose to create a directory, the installation program automatically creates one for you.

If you go back to the Choose Middleware Home Directory window to change the home Selection, the following changes occur based on the type of changes you make to the home directory:

- If you accept the default product installation directory in the Choose Product Installation Directory window, then the old installation directory is retained in the Choose Middleware Home Directory window.
For example, the default installation directory for Oracle WebLogic Server is MW_HOME\wlserver_version.

- If you enter a new product installation directory in the Choose Product Installation Directory window, the directory name is modified to this new name in the Choose Middleware Home Directory window.

- If you specify the installation directory in the Choose Product Installation Directory window, and if the directory you specify is outside of the old home, the old installation directory is retained.

For more information, see Section 1.5.2, "Choosing a Product Installation Directory."

Install Windows Service

This window displays only if all the conditions are true:

- You have Administrator privileges.

- You are performing an initial installation.

- You are installing on a Windows platform.

- You selected Custom installation in the Choose Install Type window.

Choose whether you want to install the Windows services indicated, specifically the Oracle WebLogic Server Node Manager service. Node Manager is used to monitor, start, and stop server instances in a domain.

If you select Yes, enter the Node Manager Listen Port in the appropriate field. The default is 5556.

Note: If the Listen Port number you specify is being used by a running application, the installation program prompts you to enter a different Node Manager Listen Port number.

Choose Shortcut Location

This window is displayed only under the following conditions:

- You have Administrator privileges.

- You are performing an initial installation.

- You are installing on a Windows platform.

Specify the Start menu folder in which you want the Start menu shortcuts to be created and, click Next to continue. The Status window is displayed.

Select from the following options:

- All Users Start menu folder
Select this option to provide all users registered on the machine with access to the installed software. However, only users with administrator privileges can create shortcuts in the All Users folder. Therefore, if a user without administrator privileges uses the Configuration Wizard to create domains, Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired. Press ALT+A on the keyboard to select the All Users Start Menu.

- Local User's Start menu folder
Selecting this option ensures that other users registered on this machine do not have access to the Start menu entries for this installation. Press ALT+L on the keyboard to select the Local User's start menu.

Installation Summary

This window displays a list of product components and JDKs to be installed. It also displays the description and the approximate installed size of each product component, JDKs, and the total size of all the selected items.

Click Next.

Status

Read the information displayed about products and services. When the installation program has finished copying the specified files to your system, click Next.

Installation Complete

In this screen you see a dialog box with the message, "Congratulations! Installation is Complete".

Specify whether you want to run the QuickStart application. QuickStart, designed to assist first-time users in evaluating, learning, and using the software, provides quick access to the sample domains, information for upgrading your applications, and the online documentation. Clear the check box for this option if you do not want to launch QuickStart.

Click Done to exit the installation program and, launch QuickStart, if selected.

4 Running the Installation Program in Console Mode

Start the installation program in console mode, as described in Chapter 2, "Starting the Installation Program."

To complete the console-mode installation process, respond to the prompts in each section by entering the number associated with your choice or by pressing Enter to accept the default. To exit the installation process, enter exit (or x, for short) in response to any prompt. To review or change your selection, enter previous (or p, for short) at the prompt. To proceed to the following window, enter next (or n, for short).

Note:
In the sample console text and directory path names provided in this section, Windows conventions (such as backslashes in path names) are used, for example, C:\Oracle\MW_HOME\wlserver_version. When entering path names on a UNIX system, be sure to use UNIX conventions, instead. For example, use forward slashes in path names, such as C:/Oracle/MW_HOME/wlserver_version.

Use the following procedure after you have started the installation program in console mode, as described in Chapter 2, "Starting the Installation Program."

1. At the Welcome prompt, type next (or n for short), or press Enter to continue with the installation process.
The Choose Middleware Home directory prompt is displayed

2. Specify the home directory that will serve as the central support directory for all WebLogic products installed on the target system. For information about the home directory, see Section 1.5.1, "Choosing a Home Directory."
One of the following is displayed on your system:

- If you have existing home directories on your system, a list of the directories is displayed.
To use an existing home directory, type the number associated with the home directory.

To create a home directory, type 1 or press Enter.

- If there are no home directories on your system, or you have selected create a new Middleware Home, do one of the following:
To use the default home directory, type next (or n for short), or press Enter.

To create a home directory, enter the full path of the home directory, for example C:\Middleware Home. If you specify a directory that does not exist, the installation program creates it for you.

The installation program displays the home directory you have specified.

On the command line, press Enter to accept your selection. Otherwise, type 1 or 2 to return to the Choose Middleware Home Directory panel, where you can modify your entry.

After you have selected your home directory and confirmed your selection, type Next or press Enter.

The Specify Download Options prompt is displayed

3. Indicate your preferences for downloading the software. The installation program prompts you to select from the given options.

Note:
If you have previously installed Oracle WebLogic Server and specified a storage directory during the installation process, the full path name for that directory is displayed as the default. If you have not specified a storage directory, the installer specifies the system's temporary directory as the default. Make sure that your temporary directory has sufficient space to accommodate the archive files and the installation program. For more information about temporary space required by the installation program, see Section 1.4.2, "Temporary Disk Space Requirements."

To accept the defaults, type next (or n for short) or press Enter. If you have not specified a download storage directory in a previous installation and you want to save the files to be downloaded, you must specify a directory before you can proceed with the installation.

To modify any of the options, do the following:

- Enter 1 to specify a storage directory to which you want to download the software components. When prompted, type the full path name for the desired directory. If the directory does not exist, the installation program creates it for you

- Enter 2 to delete the downloaded files after the installation is complete. If you do so, the download options are displayed again, and the Modify Remove download files after installation option is set to No. If you accept the default for this option (Yes), the downloaded files are deleted from the storage directory you specified.

- Indicate whether you want to use an HTTP Proxy server for the download by providing values for the Modify Host and Modify Port options as follows:

Enter 3 to specify a host. At the prompt, enter the name or IP address of the proxy server.

Enter 4 to specify a port. At the prompt, enter the port number of the proxy server.

- Specify the username and password required by the HTTP Proxy server, if required, as follows:

Enter 5 to specify a username. At the prompt, enter a valid username for the proxy server.

Enter 6 to specify a password. At the prompt, enter a valid password for the user.

For additional information about downloading the software, see Section 1.3, "Product Distribution."

After you have indicated your preferences for downloading the software, press Enter. One of the following occurs:

- If you are adding components to an existing installation, the Choose Components to install panel is displayed. Go to step 5.

- If you are performing an initial installation, the Choose Install Type prompt is displayed.

4. Specify the type of installation you want to perform by entering the number associated with the install type.

- To select complete installation, type 1 or press Enter and proceed to step 7.

- To select custom installation, type 2. The Choose Products and Components to install prompt is displayed.

For more information about complete and custom installations, see Section 1.6, "Choosing the Type of Installation."

5. Select the components you want to install.
The word Installed is shown in brackets for any component that is already installed in the current Middleware Home directory.

Note:
The installer displays the estimated size of the installation for the selected components.

When you select or deselect components, the installation program checks for dependencies between the components and automatically modifies the list of selected components. For example, if you deselect Oracle WebLogic Server, the components that require Oracle WebLogic Server are also deselected.

After selecting the required components, press Enter, or type n and then press Enter.

The JDK Selection prompt is displayed.

6. Select the JDK.

- To add a local JDK, enter 1, and specify the location of the JDK.

- To toggle the selection for an existing JDK, enter the appropriate number (2 or higher).

- To retain the current selection and proceed with the installation, press Enter.

The installer searches for the required archive files. User interaction is not required here.

After you select the JDK, the files begin downloading to the specified storage directory. When the download is complete, the installation program verifies that the component archive files are downloaded successfully. If the installation program cannot verify the integrity of the download, an error message is displayed.

Once the verification is complete, the Install Eclipse Options prompt is displayed.

7. Specify whether you want to install Eclipse or use the existing Eclipse.

Note:
This prompt is displayed only when you have selected Workshop as one of the components to be installed.

Press Enter to proceed to the next step.

8. Specify the directory in which you want to install the software. You can accept the default product directory (MW_HOME\wlserver_version) or create a product directory.

Note:
If you are adding components to an existing installation, you are prompted to confirm the product installation directory.

If you specify a new directory, the installation program automatically creates it for you. Do one of the following:

- Press Enter or type next (or n for short) to accept the current selection.

- Enter the full path to the directory in which you want to install the software, and press Enter. The Install Node Manager as a Windows Service prompt is displayed.

In the following situations, the installation program begins copying the components you specified to your system.

- You are performing a complete installation on a Windows platform,

- You are installing on a Windows platform and you do not have Administrator privileges,

- You are installing on a UNIX platform, or

- You are adding components to an existing installation

9. Specify whether you want to install Node Manager as a Windows service.
Do one of the following:

- Enter 1 to install node manager as a Windows service. Then, at the prompt, enter the listen port for the node manager, or press Enter to accept the default (5556). If the Listen Port number you specify is being used by a running application, the installation program prompts you to enter a different Node Manager Listen Port number. You are prompted to confirm your selection.

- Enter 2 if you do not want to install Node Manager as a Windows service.

The Choose Shortcut Location prompt is displayed.

10. Specify the folder in which you want to create the Start menu shortcuts.
Do one of the following:

- Type 1 or press Enter to create Start menu shortcuts in the All Users folder. This provides all users registered on the machine with access to the installed software. However, only users with Administrator privileges can create shortcuts in the All Users folder. Therefore, if a user without Administrator privileges uses the Configuration Wizard to create domains, Start menu shortcuts to the domains are not created. In this case, users can manually create shortcuts in their local Start menu folders, if desired.

- Type 2 to create shortcuts in your local user's Start menu folder. If you do so, other users registered on this machine will not have access to the Start menu entries for this installation.

You are prompted to confirm your selection.

11. Verify that your entry is correct, then type 1 or press Enter to proceed with the installation. Otherwise, type 2 to return to the previous panel, where you can modify your entry.
After you have verified your selection, the Installer displays a list of product components and JDKs to be installed, it also displays the estimated size of installation for the components displayed.

12. Press Enter to continue. The installation program begins copying the components you specified to your system.

Note:
It is normal for the installation program to pause for a long time, especially toward the end. The installation program is still working while this occurs.

After the installation is complete, the following message is displayed:

Installation Complete
Congratulations! Installation is complete.
Press[Enter]to continue or type [Exit]>

5 Running the Installation Program in Silent Mode

The following sections describe how to run the installation program in silent mode:

- Section 5.1, "What Is Silent-Mode Installation?"

- Section 5.2, "Using Silent-Mode Installation: Main Steps"

- Section 5.3, "Creating a silent.xml File for Silent-Mode Installation"

- Section 5.4, "Exit Codes for Silent Mode Installation"

5.1 What Is Silent-Mode Installation?

Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many machines. During installation in silent mode, the installation program reads the settings for your configuration from an XML file that you create before beginning the installation. The installation program does not display any configuration options during the installation process. Silent-mode installation works on both Windows and UNIX systems.

The instructions in this section are based on the assumption that you have already acquired the installation program either on DVD or from http://edelivery.oracle.com.

Note:
You must use the package installer for silent-mode installation. Silent-mode installation is not supported with the net installer.

5.2 Using Silent-Mode Installation: Main Steps

The silent-mode installation process has two primary steps:

1. Create a 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 example, values for the middleware home directory, the product directory, and the components to be installed are supplied in a silent.xml file.
For more information, see Section 5.3, "Creating a silent.xml File for Silent-Mode Installation."

2. Start the silent-mode installation process by using the values specified in the silent.xml file.
For information about starting the installation in silent mode, see Section 2.2.3, "Starting the Installation Program in Silent Mode."

Important Considerations for Silent-Mode Installation

When you are running the installation program in silent mode, keep in mind the following considerations:

- Silent-mode installation requires the same amount of temporary disk space and uses the same temporary storage directories as a standard installation. The installation program does not alert you if there is not enough space in the temporary directory.

- A silent-mode installation takes the same amount of time as a standard installation. At the beginning of a silent-mode installation, an initial installation program window or message is displayed briefly, indicating that the installation has started. No messages are displayed to indicate that the installation is in progress or has completed successfully.

- 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.

- The XML definition (<?xml version="1.0" encoding="UTF-8"?>) must be at the very beginning of the silent.xml file. Do not enter a space or line breaks before the XML definition.

- You cannot reinstall any WebLogic product on top of a previously installed version of the same product—in the same home directory or in the same file location. You can, however, add products and product components to an existing installation. For example, you can install WebLogic Server during one installation, and Workshop during a separate installation. To reinstall the same version of a product, you must first uninstall the previously installed instance of it or install the new instance in another location.

5.3 Creating a silent.xml File for Silent-Mode Installation

When you install your software in silent mode, the installation program uses an XML file (silent.xml) to determine which installation options should be implemented. Therefore, before you can run the installation program in silent mode, you must first create a silent.xml file in which you specify the installation options.

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.

To create a silent.xml file for use in the silent-mode installation process, follow these steps:

1. Copy the sample code provided in Appendix A, "Sample Silent.xml File for Silent-Mode Installation" and paste the code in an XML file.

2. Save the file, with the name silent.xml, in the same directory that contains the installation program.

Note:
The XML definition (<?xml version="1.0" encoding="UTF-8"?>) must be at the very beginning of the silent.xml file. Do not enter a space or line breaks before the XML definition.

3. In the silent.xml file that you saved on your system, edit the values for the keywords to reflect your configuration.
For example, for the Oracle WebLogic Server installation, edit the values in the sample silent.xml file as shown in Table 5-1.

Note:
You must follow XML guidelines for characters when modifying values. That is, you cannot use characters reserved for use in XML, such as <, >, [, and ].

Table 5-1 Values for the Sample silent.xml File for Oracle WebLogic Server

Data-Value Name

Description

MW_HOME

The full path for the home directory of your choice. For more information about the home directory, see Section 1.5.1, "Choosing a Home Directory."

WLS_INSTALL_DIR

The full path for the directory where you want to install Oracle WebLogic Server (for example, for Windows: C:\MW_HOME\wlserver_10.3).

WLW_INSTALL_DIR

The full path for the directory where you want to install Workshop (for example, for Windows:C:\MW_HOME\workshop_10.3).

For more information, see Section 1.5.2, "Choosing a Product Installation Directory."

COMPONENT_PATHS

Specify the components and subcomponents you want to install on your system.

For Example:

- To install Oracle WebLogic Server, use the following values:

WebLogic Server/Core Application Server
|WebLogic Server/Administration Console
|WebLogic Server/Configuration Wizard and Upgrade Framework
|WebLogic Server/Web 2.0 HTTP Pub-Sub Server
|WebLogic Server/WebLogic JDBC Drivers
|WebLogic Server/Third Party JDBC Drivers
|WebLogic Server/WebLogic Server Clients
|WebLogic Server/WebLogic Web Server Plugins
|WebLogic Server/UDDI and Xquery Support
|WebLogic Server/Server Examples

- To install Workshop use the following values:

Workshop/Workshop for WebLogic
Workshop/Workshop Runtime Framework

For additional information about entering these values, see Guidelines for Component Selection.

USE_EXTERNAL_ECLIPSE

If the correct version of Eclipse is already installed, this variable is ignored.

The default value is false.

If Eclipse is not installed, or is an older version,

- If the value of this variable is true, only the Eclipse plug-ins are installed in the directory indicated by EXTERNAL_ECLIPSE_DIR. If the required dependencies are not installed in the Eclipse directory, the installation fails.

- If the value of this variable is false, the complete Eclipse is installed in the default location. Note that this location is different from the location for older versions of Eclipse; this ensures that the older versions are not overwritten.

EXTERNAL_ECLIPSE_DIR

The directory where the existing Eclipse instance is installed.

If the correct version of Eclipse is already installed, this variable is ignored.

INSTALL_NODE_MANAGER_SERVICE

(Windows platforms only)

- yes to install the Oracle WebLogic Server Node Manager as a Windows service.

- no to skip the installation of the Oracle WebLogic Server Node Manager as a Windows service. The default is no.

Note: You must have Administrator privileges to install Node Manager as a Windows service.

NODEMGR_PORT

The Node Manager listen port.

If you do not specify a port number, the installer uses the default port 5556.

If the port number is in use, the installer scans for the next available port and assigns it to the Node Manager.

Note: The INSTALL_NODE_MANAGER_SERVICE option must be set to yes.

At the completion of the installation process, the Node Manager is started using the port specified.

INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER

- true, or yes, to create the shortcuts in the All Users folder. The default is true.

- false, or no, to create the shortcuts in the local users folder.

The user performing the installation must have Administrator privileges to install the Start menu shortcuts in the All Users folder. For more information, see Section 1.4.3, "Administrator Privileges."

LOCAL_JVMS

This is an optional element using which you can specify the local JDKs to be installed. Enter the full path of the JDKs to be installed, separated by the pipe symbol ('|').

BEA_BUNDLED_JVMS

This is an optional element using which you can specify the BEA-supplied JDKs to be installed. Enter the full path of the JDKs to be installed, separated by the pipe symbol ('|').

Guidelines for Component Selection

The following are the guidelines for specifying values for the COMPONENT_PATHS data-value name:

- When you specify a product component to be installed, all subcomponents that are installed by default in a complete installation are also installed. For example, the following entry installs both Oracle WebLogic Server and the examples:

<data-value name="COMPONENT_PATHS" value="WebLogic Server" />

- To install multiple components, separate the components with a bar (|). Do not leave a space before or after the bar.
For example, to install Oracle WebLogic Server and Oracle Workshop for WebLogic, enter:

<data-value name="COMPONENT_PATHS" value="WebLogic Server|Workshop" />

- To specify subcomponents, you must specify a component/subcomponent combination for each entry.
For example, to install specific components of Oracle WebLogic Server and Oracle Workshop for WebLogic, enter the following line in the file:

<data-value name="COMPONENT_PATHS" value="WebLogic Server/Core Application Server|
WebLogic Server/Administration Console|Workshop/Workshop for WebLogic"/>

- If you do not include the COMPONENT_PATHS data-value name in the silent.xml file, the complete Oracle WebLogic Server and Oracle Workshop for WebLogic are installed.

Note:
The installation program performs dependency checking to ensure that all components that provide functionality on which other components depend for proper operation are installed. These dependencies are visible during graphical and console mode installations. The same dependencies are enforced during silent installation, components on which other components depend are installed even if they are not explicitly referenced in a silent script.

5.4 Exit Codes for Silent Mode Installation

When run in silent mode, the installation program generates exit codes that indicate the success or failure of the installation.

Table 5-2 shows the exit codes.

Table 5-2 Exit Codes for Silent Mode Installation

Exit Code

Description

0

Installation completed successfully

-1

Installation failed due to a fatal error

-2

Installation failed due to an internal XML parsing error

If you launch the silent-mode installation process from a script, you can choose to have these exit codes displayed on the console.

Example 5-1 provides a sample command file that invokes the installation program in silent mode and echoes the exit codes to the console from which the script is executed.

Example 5-1 Sample Command File Displaying Silent-Mode Exit Codes

rem Execute the installer in silent mode
@echo off
server103_win32.exe -mode=silent -silent_xml=C:\downloads\silent.xml -log=C:\logs\products_silent.log
@rem Return an exit code to indicate success or failure of installation
set exit_code=%ERRORLEVEL%

@echo.
@echo Exitcode=%exit_code%
@echo.
@echo Exit Code Key
@echo ---------------
@echo  0=Installation completed successfully
@echo -1=Installation failed due to a fatal error
@echo -2=Installation failed due to an internal XML parsing error
@echo.

6 Post-Installation Information

This section covers the following topics:

- Section 6.1, "Using QuickStart"

- Section 6.2, "Determining Which JDK Version You Are Using"

- Section 6.3, "Creating an Oracle WebLogic Server Starter Domain"

- Section 6.4, "Understanding the Windows Shortcuts"

- Section 6.5, "Supported Configurations"

- Section 6.6, "Upgrading Oracle WebLogic Server"

- Section 6.7, "Installing Patches and Maintenance Updates"

6.1 Using QuickStart

When the product installation is completed using graphical-mode installation, the QuickStart application is launched automatically, by default. If you do not want to run QuickStart at the completion of the installation process, you can clear the Run QuickStart check box in the Install Complete window. QuickStart is not invoked for console-mode or silent-mode installations.

QuickStart is designed to help first-time users evaluate, learn, and use Products software.

For example, the QuickStart application for Oracle WebLogic Server provides quick access to the following tasks:

- Getting started with Oracle WebLogic Server

- Starting the Oracle WebLogic Server samples domain

- Upgrading domains to the current version

- Accessing documentation online

After installation, you can launch QuickStart as follows:

- On Window systems, choose Start > Programs > Oracle WebLogic > QuickStart.

- On UNIX systems, perform the following steps:

1. Log in to the target UNIX system.

2. Go to the /common/bin subdirectory of your installation. For example:
cd /MW_HOME/wlserver_version/common/bin

3. Enter the following command:
sh quickstart.sh

6.2 Determining Which JDK Version You Are Using

You can determine which version of the JDK you are using by issuing a command, as follows:

1. Open a command prompt window and go to the appropriate directory:
Windows: MW_HOME\WL_HOME\server\bin

UNIX: MW_HOME/WL_HOME/server/bin

2. Make sure that your environment is set up properly by entering the following command at the prompt:
Windows: setWLSenv.cmd

UNIX: setWLSenv.sh

3. Enter the following command at the prompt: java -version
If you are using JRockit, JRockit(R) is displayed in the output.

6.3 Creating an Oracle WebLogic Server Starter Domain

After you install WebLogic Server, you can create a WebLogic Server domain by using the starter domain template, wls_starter.jar, which is available in the MW_HOME\WL_HOME\common\templates\domains folder.

The wls_starter.jar template contains the default domain configuration settings and an application that provides a welcome page to help you get started.

For more information about creating a domain by using an existing domain template, see "Creating a WebLogic Domain" in Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.

6.4 Understanding the Windows Shortcuts

When you install your software on a Windows system, the installation program automatically creates shortcut entries on the Start Menu.

Note:
If the user performing the installation has Administrator privileges, the shortcut entries can be created in the All Users Start menu folder or in the user's local Start menu folder. For more information, see Section 1.4.3, "Administrator Privileges."

The options in the Start > Programs > Oracle WebLogic menu vary, according to the components you choose to install.

- WebLogic Server 11gR1: Contains a shortcut for launching the default Oracle WebLogic Server domain, examples, tools, online documentation. The Server domain enables you to run pre-built Oracle WebLogic Server code samples, deploy Java EE applications, and quickly serve JSPs or HTML pages. You can also use this domain as a place to test your applications during development.
Examples contain a folder for each component installed on your system that contain shortcuts for launching the examples and associated tools for the component.

Tools contain a folder for each component installed on your system that contains shortcuts for launching the examples and associated tools for the component.

- Workshop: Contains shortcut for the examples and the online documentation.

- Online Documentation: Provides a link to the online documentation.

- QuickStart: Starts the QuickStart application designed to assist first-time users in evaluating, learning, and using the Products software.

- Smart Update: Launches the Smart Update program, which checks for any updates available for installed products, and installs the updates as required.

- Uninstall Oracle WebLogic: Launches the uninstallation program. For more information, see Chapter 7, "Uninstalling the Software."

- Workshop for WebLogic 11gR1: Launches the Workshop for WebLogic.

6.5 Supported Configurations

For complete details about the hardware and software configurations supported by Oracle WebLogic Server and Oracle Workshop for WebLogic, see the Oracle Fusion Middleware Supported System Configurations page at http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html. This document describes supported operating systems, Web servers, browsers, firewalls, database configurations, and other tools and configurations.

6.6 Upgrading Oracle WebLogic Server

If you are upgrading your Oracle WebLogic Server installation from an earlier version, see Oracle Fusion Middleware Upgrade Guide for Oracle WebLogic Server. This document explains how to upgrade the entire Oracle WebLogic Server environment, including applications, the WebLogic domains in which they are deployed, and any application data associated with the domain, and may include external resources, such as database servers, firewalls, load balancers, and LDAP servers.

6.7 Installing Patches and Maintenance Updates

Smart Update is a standalone Java application that is automatically installed in the Middleware Home directory and that simplifies the process of applying patches and maintenance updates to your Oracle WebLogic Server installation. When support makes a patch or maintenance update available for an installed version of Oracle WebLogic Server, you use Oracle Smart Update to obtain that update and apply it to your installation. Smart Update organizes all available maintenance for you, and has several features that allow a great deal of customizing in the way various patches and other maintenance updates are applied and managed in your environment.For information about using Smart Update, see Oracle Smart Update Installing Patches and Maintenance Packs.

7 Uninstalling the Software

The following sections provide procedures for uninstalling the software:

- Section 7.1, "About the Uninstallation Program"

- Section 7.2, "Uninstalling Your Software in Graphical Mode"

- Section 7.3, "Uninstalling Your Software in Console Mode"

- Section 7.4, "Uninstalling Your Software in Silent Mode"

- Section 7.5, "Reinstalling Your Software"

7.1 About the Uninstallation Program

The following sections describe how to uninstall your software on Windows and UNIX systems. You can uninstall the software using graphical, console, or silent mode. To run the graphical-mode uninstallation program, your console must support Java-based GUIs. If the uninstallation program determines that your system cannot support Java-based GUIs, it automatically starts running in console mode.

You can uninstall individual components of your product distribution, or the entire installation. Dependency checking in the uninstaller ensures that the appropriate components are uninstalled.

The uninstallation program does not remove the home directory associated with the installation, the JDK, or any user-created domains. Only the components that were installed by the installation program can be removed. If you choose to uninstall the entire installation, the uninstallation program also removes the product directory associated with the installation unless any of the following is true:

- The product directory contains user-created configuration or application files. The uninstallation program does not delete user-created configuration files, application files, or domains.

- The complete installation was not uninstalled. If an individual component is uninstalled, only the installation directory for that component is removed; the installation directories for other components are unaffected.

- The uninstallation program was invoked from within the product directory structure—specifically, from the uninstaller directory.

7.2 Uninstalling Your Software in Graphical Mode

Use the following procedure to uninstall the complete product installation, or individual components, in graphical mode:

1. Shut down any servers that are running. If any of these servers is configured as a Windows service, you should stop the service(s) before uninstalling the software.

2. Start the uninstallation program as described in Table 7-1.

Table 7-1 Starting the Uninstallation Program in Graphical Mode

Platform

Procedure

Windows

1. From the Windows Start menu, choose Start > Programs > Oracle WebLogic > Uninstall Oracle WebLogic.
The Oracle Uninstaller Welcome window is displayed.

2. Proceed to step 3

UNIX

1. Go to the following directory:
MW_HOME\utils\uninstall

Here MW_HOME represents the directory in which you have installed your software.

2. Enter uninstall.sh at the prompt.

The Oracle Uninstaller Welcome window is displayed.

Note: If your system supports a graphical user interface, the uninstallation program starts in graphical mode. If your system does not support a graphical user interface, the uninstallation program starts in console mode. If console mode is started, see Section 7.3, "Uninstalling Your Software in Console Mode" for instructions.

3. Click Next to start the uninstall program.
The Choose Components window is displayed.

4. Select the components to uninstall by selecting or clearing the appropriate check boxes. Then click Next. By default, all installed components are selected, indicating that they will be removed.

5. Optionally, click Details to view the log file that lists the uninstalled components.

6. Click Done in the Uninstalling Oracle Products window to exit the uninstallation program.

7.3 Uninstalling Your Software in Console Mode

Use the following procedure to uninstall the complete product installation, or individual components, using the command-line interface:

1. Shut down any servers that are running. If any of these servers is configured as a Windows service, you should stop the service(s) before uninstalling the software.

2. Start the uninstallation program as described in Table 7-2.

Table 7-2 Starting the Uninstallation Program in Console Mode

Platform

Procedure

Windows

1. Open a command prompt window and go to the following directory:
MW_HOME\utils\uninstall

Here MW_HOME represents the directory in which you have installed your software.

2. Enter the following command at the prompt:

uninstall -mode=console

The Welcome text is displayed.

UNIX

1. Go to the following directory:
MW_HOME\utils\uninstall

Here MW_HOME represents the directory in which you have installed your software.

2. At the prompt, enter the following command:

sh uninstall.sh -mode=console

The welcome text is displayed.

3. Press Enter or type next to proceed to the next panel of the uninstallation program.

Note:
Instead of typing complete words when you want to enter [Exit], [Previous], and [Next], you can use the following one-letter shortcuts: x, p, and n, respectively.

The Choose Components to uninstall panel is displayed.

4. Select the components you want to uninstall.
By default, all installed components are selected, indicating that they will be removed.

Note:
If you have installed your software using the installation program for Oracle WebLogic Server, only the Oracle WebLogic Server components are displayed.

To leave a component installed on your system, enter the numeric code for that component on the command line, exactly as it appears within the brackets.

Dependency checking is performed to ensure that you do not uninstall a component that is required by another component.

5. Press Enter or type next to proceed with the uninstallation process.

6. When the uninstallation process is complete, press Enter or type exit to complete the uninstallation and exit the uninstallation program.

7.4 Uninstalling Your Software in Silent Mode

When you uninstall your Products software in silent mode, the complete installation of your software is uninstalled.

When you run the uninstallation program in silent mode, it leaves behind the same files and directories as when you run the uninstallation program in graphical and console modes, including:

- The home directory, including the logs and utils subdirectories

- The JDK, if it was installed with your product

- Domain directories, including those in user_projects

- Any other file created or modified after your software was installed

You can manually delete these files.

Although you can use silent-mode uninstallation to manually uninstall your software, silent-mode uninstall is intended for use in scripts. You can follow the steps in Table 7-3 for use in scripts.

Use the following procedure to uninstall your Products software in silent mode:

1. Shut down any servers that are running. If you configured any of the servers as a Windows service, you must stop the service(s) before uninstalling the software.

2. Start the uninstallation program as described in Table 7-3.

Table 7-3 Starting the Uninstallation Program in Silent Mode

Platform

Procedure

Windows

1. Open a command prompt window and go to the following directory:
MW_HOME\utils\uninstall

Here MW_HOME represents the directory in which you have installed your software.

2. Enter the following command at the prompt:

uninstall -mode=silent

UNIX

1. Go to the following directory:
MW_HOME\utils\uninstall

Here MW_HOME represents the directory in which you have installed your software.

2. At the prompt, enter the following command:
sh uninstall.sh -mode=silent

Note:
When you run the uninstallation program in silent mode, no messages are displayed indicating the uninstallation is in progress or has completed successfully, even if errors are encountered.
You can include the -log=full_path_to_log_file option in the command line to create a verbose installation log.For example:

uninstall -mode=silent -log=C:\logs\weblogic_uninstall.log

7.5 Reinstalling Your Software

You cannot reinstall the same version of a product on top of a previously installed version of the same product, in the same home directory or in the same file location. However, you can add products and product components to an existing installation. For example, you can install WebLogic Server during one installation, and Workshop for WebLogic during a separate installation.

To reinstall the same version of a product component or an entire product distribution in the same location, you must first uninstall the previous installation.

If you try to install a complete copy of a product in a home directory that contains a complete installation, an error message is displayed. Click or type OK to return to the Choose Middleware Home directory prompt.

At the prompt, choose one of the following options:

- To continue installing the software using a different home directory, select an existing home directory that does not contain a previous installation, or create a home directory.

- Exit the installation program. To reinstall your software in the same home, you must uninstall the previous installation.
You can start the uninstall program appropriate for your platform, as described in the following sections:

- Section 7.2, "Uninstalling Your Software in Graphical Mode"

- Section 7.3, "Uninstalling Your Software in Console Mode"

- Section 7.4, "Uninstalling Your Software in Silent Mode"

Then, install the software as described in Chapter 2, "Starting the Installation Program."

A Sample Silent.xml File for Silent-Mode Installation

<?xml version="1.0" encoding="UTF-8"?>
<!-- Silent installer option: -mode=silent -silent_xml=C:\bea\silent.xml -->
<!-- Specify values for each data-value name as follows:

BEAHOME            Complete pathname to the BEA Home directory that
will contain this installation.

WLS_INSTALL_DIR    Complete pathname to the product installation
directory in which to install WebLogic Server.

COMPONENT_PATHS    Components and subcomponents to be installed.
To install multiple components, separate the components
with a bar (|).
To install subcomponents, specify a
component/subcomponent combination. For example,
to install Core Application Server, use
"WebLogic Server/Core Application Server".

INSTALL_NODE_MANAGER_SERVICE  Install Node Manager as a Windows
service. The default is "no".
Requires Administrator privileges.

NODEMGR_PORT       Node Manager listen port number. If none specified,
installer uses default port 5556.
INSTALL_NODE_MANAGER_SERVICE must be set to "yes".

INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER
The Windows Start menu folder in which you want the
Start menu shortcuts created.
The user performing the installation must have
Administrator privileges to install the shortcuts
in the All Users folder.
Possible values:
true/yes  The shortcuts are created in
the All Users folder (default)
false/no  The shortcuts are created in
the local user's folder

BEA_BUNDLED_JVMS
Option to select BEA bundled JVMS (for e.g. either
jrockit_160_05 or jdk160_05 for Windows and Linux
platforms). The default value is all BEA bundled JVMs
for selected platform.

LOCAL_JVMS
Option to select supported JVM, which is already
installed.Note: The presence of either(BEA_BUNDLED_JVMS
or LOCAL_JVMS) or both of these tokens negates any
default selection and only sets the values assigned for
these tokens as user selection. The value of the token
can be a pipe ('|') separated JavaHomes.

See the Installation Guide for more information.

-->
<bea-installer>
<input-fields>
<data-value name="BEAHOME" value="D:\Oracle\Middleware_Home" />
<data-value name="WLS_INSTALL_DIR" value="D:\Oracle\Middleware_Home\wlserver_10.3" />
<data-value name="COMPONENT_PATHS"
value="WebLogic Server/Core Application Server
|WebLogic Server/Administration Console
|WebLogic Server/Configuration Wizard and Upgrade Framework
|WebLogic Server/Web 2.0 HTTP Pub-Sub Server
|WebLogic Server/WebLogic JDBC Drivers
|WebLogic Server/Third Party JDBC Drivers
|WebLogic Server/WebLogic Server Clients
|WebLogic Server/WebLogic Web Server Plugins
|WebLogic Server/UDDI and Xquery Support
|WebLogic Server/Server Examples" />
<data-value name="INSTALL_NODE_MANAGER_SERVICE" value="yes"  />
<data-value name="NODEMGR_PORT" value="5559" />
<data-value name="INSTALL_SHORTCUT_IN_ALL_USERS_FOLDER" value="yes"/>
<!--
<data-value name="LOCAL_JVMS       "value="D:\jrockit_160_05|D:\jdk160_11"/>
-->

</input-fields>
</bea-installer>

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.