Contents

Title and Copyright Information

Preface

Audience

Document Organization

Documentation Accessibility

Conventions

1 Installation Overview

Installable Products

Installation Roadmap

2 Preparing for Installation

Types of Installers

Product Distribution

Downloading the Installer From Oracle E-Delivery

Downloading the Installer From Oracle Technology Network

Downloading an Upgrade Installer From My Oracle Support

Installation Prerequisites

System Requirements

WebLogic Server Installation User

Before You Start the Installation Program

Temporary Disk Space Requirements

Administrator Privileges

About Installing Node Manager as a Windows Service

Selecting Directories for Installation

Choosing a Middleware Home Directory

Choosing Product Installation Directories

Installation Modes

Choosing the Type of Installation

Installable Product Components

Generating a Verbose Installation Log

3 Running the Installation Program in Graphical Mode

Starting the Installation Program in Graphical Mode

Starting the Installation Program in Graphical Mode on Windows

Starting .bin Installation Programs in Graphical Mode on UNIX Machines

Starting .jar installation Programs in Graphical Mode

Installing WebLogic Server on 64-Bit Platforms Using a 64-Bit JDK

Installation Screens

Running the Upgrade Installer in Graphical Mode

4 Running the Installation Program in Console Mode

Starting the Installation Program in Console Mode

Starting the Installation Program in Console Mode on Windows

Starting .bin Installation Programs in Console Mode

Starting .jar Installation Programs in Console Mode

Installing WebLogic Server on 64-Bit Platforms Using a 64-Bit JDK

Installing WebLogic Server in Console Mode

Running the Upgrade Installer in Console Mode

5 Running the Installation Program in Silent Mode

What Is Silent-Mode Installation?

Overview of Silent-Mode Installation Steps

Creating a silent.xml File for Silent-Mode Installation

Guidelines for Component Selection

Starting Silent Mode Installation

Starting the Installation Program in Silent Mode on Windows

Starting .bin Installation Programs in Silent Mode

Starting .jar installation programs in Silent Mode

Installing WebLogic Server on 64-Bit Platforms Using 64-Bit JDK

Exit Codes for Silent Mode Installation

Sample silent.xml File for Silent Mode Installation

Running the Upgrade Installer in Silent Mode

Sample silent.xml File for Upgrade Installation

6 Post-Installation Information

Using QuickStart

Determining Which JDK Version You Are Using

Creating a WebLogic Domain

Installing and Uninstalling the Node Manager Service

Understanding the Windows Shortcuts

Upgrading WebLogic Server

Installing Patches

Configuring Domains to Use the Latest Version of JRockit

7 Uninstalling the Software

Uninstalling the Software

Uninstalling Your Software in Graphical Mode

Uninstalling Your Software in Console Mode

Uninstalling Your Software in Silent Mode

Reverting to a Previous Installation

Reverting to a Previous Version Using Graphical Mode

Reverting to a Previous Version Using Console Mode

Upgrading the Embedded LDAP Schema

Reinstalling Your Software

A Oracle WebLogic Server Installation Screens

Welcome

Choose Middleware Home Directory

Register for Security Updates

Choose Install Type

Choose Products and Components

JDK Selection

Choose Product Installation Directories

Confirm Product Installation Directory

Install Windows Service

Choose Shortcut Location

Installation Summary

Status

Installation Complete

B Development-Only Installation

Getting Started with the Development-only Installation

Creating Domains

Upgrading an Existing Installation

Removing an Existing Installation

C WebLogic Server Installers

D Using WebLogic Server with JDK 7

Oracle® Fusion Middleware

Installation Guide for Oracle WebLogic Server

11g Release 1 (10.3.6)

E14142-07

November 2011

This document describes how to install Oracle WebLogic Server.

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

E14142-07

Copyright © 2007, 2011, 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 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 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 America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

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.

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.

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.

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 WebLogic Server. 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, "Installation Overview," lists the products that can be installed with the WebLogic Server installer, and describes the high-level tasks that are required for installation.

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

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.

Appendix A, "Oracle WebLogic Server Installation Screens," describes each of the WebLogic Server installation program screens.

Appendix B, "Development-Only Installation," provides information about the WebLogic Server installer that is used only for development purposes.

Appendix C, "WebLogic Server Installers," lists and briefly describes the available WebLogic Server installers.

Appendix D, "Using WebLogic Server with JDK 7," describes how to install install JDK 7 for use with WebLogic Server, and issues that you may encounter when using JDK 7.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

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 Installation Overview

This chapter lists the products that you can install with the WebLogic Server installation program. It also includes the WebLogic Server installation roadmap.

Installable Products

Installation Roadmap

Installable Products

You can install the following products using the Oracle WebLogic Server installer:

WebLogic Server and optional sub-components

Oracle Coherence and optional sub-components

To get started with the installation, refer to Installation Roadmap.

Installation Roadmap

Table 1-1 describes the high-level tasks that are required to install WebLogic Server, and the optional Coherence product.

Table 1-1 Tasks WebLogic Server Product Installation Procedure

Task
Description
Documentation

Step 1 - Obtain the appropriate installation file for your platform

If you ordered a WebLogic Server kit, it includes a DVD for installation. Otherwise, there are several ways for you to download the software. The installer you use depends on your platform and the products you want to install.

For information about the types of installers that are available, see Types of Installers.

For information about how to download the software, see Product Distribution.

Step 2 - Complete the installation planning requirements

Ensure that your system environment meets the requirements for the installation. Also determine your Oracle Middleware home directory, and product installation home directories.

For installation requirements, see Installation Prerequisites.

For information about installation home directories, see Selecting Directories for Installation.

Step 3 - Determine the appropriate installation mode for your situation

There are three installation modes: graphical mode, console mode, or silent mode.

See Installation Modes.

Step 4 - Determine the type of installation

There are two types of installation Typical or Custom. The type of installation depends on the products and sub-components you want to install.

For information about the installation types, see Choosing the Type of Installation.

For information about each product and component, see Installable Product Components.

Step 5 - Install the software

Run the installation program in the desired installation mode. In each installation mode, you have the option to create a detailed installation log.

For instructions on how to create a detailed installation log, see Generating a Verbose Installation Log.

For installation instructions, see the following chapter that is appropriate for the installation mode you want to use:

Running the Installation Program in Graphical Mode.

Running the Installation Program in Console Mode.

Running the Installation Program in Silent Mode.

Step 6 - Create a WebLogic domain

Use the Fusion Middleware Configuration Wizard, WebLogic Scripting Tool, or the unpack command to create a WebLogic domain.

See Creating a WebLogic Domain.

2 Preparing for Installation

This chapter describes the type of WebLogic Server installers and how they are distributed. It also describes installation prerequisites, the installation directory structure, installation modes, types of installation, and installable components.

Types of Installers

Product Distribution

Installation Prerequisites

Selecting Directories for Installation

Installation Modes

Choosing the Type of Installation

Installable Product Components

Generating a Verbose Installation Log

Types of Installers

The following types of WebLogic Server installers are available:

OS-specific Package installer—This type of installer is a standalone version of the installation program that includes the JDKs for the selected platform. The installer may be either an .exe file or a .bin file, depending on the selected platform.

Note:

Silent mode installation is supported only for Package installers.

Generic Package installer—This type of installer is a .jar file. It does not include the JRockit SDK and Sun JDK. You can use this type of installer to install the product on any supported platform on which Java is already installed.

Upgrade installer—Upgrade installers allow you to upgrade an existing WebLogic Server installation to the current patch release. For example, if you have WebLogic Server 10.3.0 installed, you can use an Upgrade installer to upgrade your installation to WebLogic Server 10.3.6. If a patch release is available for your current WebLogic Server installation, you can download an Upgrade installer from My Oracle Support.

Note:

If you have an existing WebLogic Server 10.3.0, 10.3.1, 10.3.2, or 10.3.3 installation that includes Workshop for WebLogic, and you want to use an Upgrade installer to upgrade that installation to WebLogic Server 10.3.6, you must uninstall Workshop for WebLogic before running the Upgrade installer. See Chapter 7, "Uninstalling the Software," for more information.

Depending on your platform, the Upgrade installer is either an OS-specific Package installer (.bin or .exe file) or a Generic Package installer (.jar file).

Upgrade installers are available only from My Oracle Support. For information about how to download from this site, see Downloading an Upgrade Installer From My Oracle Support.

Development-only and supplemental installers—The development-only installer is a ZIP file that you extract to a Middleware home directory to create a WebLogic Server installation. It contains a WebLogic Server installation that includes all of the artifacts needed for development. You must not use this WebLogic Server installation for production.

A supplemental installer ZIP file is also available to provide additional features, such as server examples, for a development-only installation.

For more information about these installers, see Appendix B, "Development-Only Installation."

For a complete list of the available installers, see Appendix C, "WebLogic Server Installers." For information on how to obtain the appropriate installer for your platform, see Product Distribution.

Product Distribution

The WebLogic Server installers are distributed in the following ways:

WebLogic Server installation DVD.

Download from the Oracle Software Delivery Cloud Web site at http://edelivery.oracle.com/. Only the OS-specific Package installers and Generic Package installers are available from this site; Upgrade installers are not available here. These files are downloaded as ZIP files. For information about how to download from this site, see Downloading the Installer From Oracle E-Delivery.

Download from the Oracle Technology Network Web site. The OS-specific Package and Generic Package installers are available from this site; Upgrade installers are not available here. The downloaded file is a .bin, .jar, or .exe file, depending on your platform. For information about how to download from this site, see Downloading the Installer From Oracle Technology Network.

Download from My Oracle Support at https://support.oracle.com/CSP/ui/flash.html. Upgrade installers are available from this Web site. You must have a current My Oracle Support account to access this site. For information about how to download from this site, see Downloading an Upgrade Installer From My Oracle Support.

Downloading the Installer From Oracle E-Delivery

To download the installer from the Oracle E-Delivery Web site:

Enter the Oracle Software Delivery Cloud URL (http://edelivery.oracle.com/) in a Web browser.

If prompted, choose your language and click Continue.

Complete the Export License Agreement as instructed on the site, and then click Continue.

On the Media Pack Search page, select Oracle Fusion Middleware from the Select a Product Pack drop-down list.

Select your platform from the Platform drop-down list and click Go. The Results list shows all products that match your selections.

Click the Oracle Fusion Middleware 11g Media Pack link.

Click the Download link for the WebLogic Server installer you want to download.

Click Save.

Browse to the directory where you want to save the file. Click Save to start the file download. A compressed ZIP file is downloaded.

Extract the ZIP file, which contains only the appropriate installer executable for the selected platform, to a directory of your choice. The installer is located in the ZIP file part number directory.

Downloading the Installer From Oracle Technology Network

To download the installer from the Oracle Technology Network:

Enter the Oracle Technology Network URL (http://download.oracle.com) in a Web browser.

In the Middleware section, click Oracle Fusion Middleware 11g Release 1.

Click OTN License Agreement and read the license agreement.

Select the Accept License option. You must accept the license agreement before you can download the installer.

Follow the on-screen instructions to access the list of available installers for the current release and download the appropriate installer for your operating system.

Downloading an Upgrade Installer From My Oracle Support

If a patch release or patch set is available for your current WebLogic Server installation, you can download an Upgrade installer from My Oracle Support. Upgrade installers let you install an available patch release or patch set onto an existing WebLogic Server installation. For example, you can use an Upgrade installer to install the WebLogic Server 10.3.6 release over an existing WebLogic Server 10.3.0, 10.3.1, 10.3.2, 10.3.3, 10.3.4, or 10.3.5 installation.

Notes:

You must have an active My Oracle Support account in order to download an Upgrade installer.

As of WebLogic Server 10.3.4, you can no longer use Smart Update to download and install patch releases. You can only upgrade an existing installation to 10.3.4 or greater by downloading an Upgrade installer from My Oracle Support.

To download an Upgrade installer:

Enter the My Oracle Support URL (https://support.oracle.com/) in a Web browser.

Click Sign In and enter your My Oracle Support username and password.

Select the Patches and Updates tab.

In the Patch Search pane, click Product or Family (Advanced Search).

From the Product Is: drop-down list, select Oracle WebLogic Server.

From the Release Is: drop-down list, click the arrow next to the Oracle WebLogic Server folder, select the release you want to download, and click Close. (To upgrade to WebLogic Server 10.3.6, select WLS 10.3.6.0 from the list.)

From the Platform drop-down list, select your platform and click Close. You can select multiple platforms. Selected platforms are indicated by a check mark.

Click Search. The search results list displays all available patches and Upgrade installers for the selected release for all of the selected platforms.

Click the Patch ID or patch description to select a patch. The description for an upgrade installer patch includes the text WEBLOGIC SERVER 11GR1(10.3.4) UPGRADE INSTALLER.

Click the Download button on the right to begin the download.

Click Save.

Browse to the directory where you want to save the installer, and click Save again to start the file download. A compressed file downloads for the selected platform.

After the download completes, extract the compressed file, which contains only the appropriate installer executable for the selected platform.

Installation Prerequisites

The following sections describe the installation prerequisites:

System Requirements

WebLogic Server Installation User

Before You Start the Installation Program

Temporary Disk Space Requirements

Administrator Privileges

About Installing Node Manager as a Windows Service.

System Requirements

The system requirements for running the installation program are listed in Table 2-1.

Table 2-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 the most up-to-date 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.

Processor

1-GHz CPU

Hard disk drive

A complete installation (including SDKs) requires approximately 3.9 GB of disk space. This includes temporary disk space that is needed during installation. Depending on the components you choose to install, and the installer that you are using, less disk space may be needed.

For more information, see Temporary Disk Space Requirements.

Memory

A minimum of 1 GB RAM, although Oracle recommends 2 GB of RAM.

Color bit depth display

For graphical-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 installation program requires a Java run-time environment (JRE) to run. A JRE is bundled in the Windows 32-bit and Linux x86 installation programs, as well as in some UNIX installation programs (those with file names ending in .bin).

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

Note: 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. All scripts installed by the installation program use this JDK by default, including scripts to start sample applications, the Configuration Wizard, and other development tools.

WebLogic Server Installation User

The user account you use when installing WebLogic Server is important. Please review the following information before deciding which user account to use:

When installing WebLogic Server on a UNIX or Linux operating system, do not run the installation program as the root user.

When using a WebLogic Server Upgrade installer to upgrade an existing WebLogic Server installation on Linux or UNIX operating systems, you must run the Upgrade installer using the same user ID as was used to perform the initial WebLogic Server installation.

On Windows systems, if you want the option to create the Start menu shortcuts in the All Users folder, or in the Local User's Start menu folder, you must use an account that has administrator privileges when you log in to the target system. See Administrator Privileges, for more information.

Before You Start the Installation Program

Before you start the installation program, review the following information:

If you are using the Generic Package installer or the Linux 64-bit installer to install WebLogic Server on a UNIX or Linux system, Oracle recommends that you set the umask to 027 on your system prior to installation. This ensures that WebLogic Server file permissions will be set properly during installation. Use the following command:

umask 027

You must enter this command in the same terminal window from which you plan to run the WebLogic Server installer.

If you are installing the software in graphical mode on a UNIX or Linux machine, you must set the DISPLAY environment variable before running the installer.

If you want to use WebLogic Server with JDK 7, review the information in Using WebLogic Server with JDK 7, prior to starting the WebLogic Server installation.

If you are using a .jar installer, replace JAVA_HOME with the installation location of the supported JDK you installed for your platform.

Make sure that you are installing your product on a supported hardware or software configuration. For more information, see the Oracle Fusion Middleware Supported System Configurations page at http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html.

You cannot reinstall a product on top of a previously installed version of the same product, either in the same Middleware 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 Core Application Server, Administration Console, and Configuration Wizard Upgrade Framework during one installation, and add WebLogic JDBC Drivers and Server Examples during a separate installation. To reinstall the same version of a product, however, you must first uninstall the previous installation, as described in Chapter 7, "Uninstalling the Software."

You can also install patches to an existing installation using an Upgrade installer or Smart Update. For example, you can use a WebLogic Server 10.3.6 Upgrade installer to upgrade an existing version 10.3.0 installation to version 10.3.6.

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

Temporary Disk Space Requirements

The installation program uses a temporary directory into which it extracts the files that are needed 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 Table 2-2.

Table 2-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 temporary directory while running the WebLogic Server Package installer for Windows, execute this command:

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

Administrator Privileges

On Windows systems, if you want the option to create the Start menu shortcuts in the All Users folder, or in the Local User's Start menu folder, you must use an account that has administrator privileges when you log in to the target system.

Table 2-3 describes the available options.

Table 2-3 Available Shortcut Options

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

About Installing Node Manager as a Windows Service

When installing your software on a Windows platform, you can optionally install WebLogic Server Node Manager as a Windows service. The WebLogic Server Node Manager is used to:

Start and stop server instances—both Administration Servers and Managed Servers—remotely.

Monitor the self-reported health of servers and automatically kill server instances whose health state is FAILED.

Migrate servers in a WebLogic Server cluster.

Automatically restart servers that have the "failed" health state, or have shut down unexpectedly due to a system crash or reboot.

In a multi-machine environment, you must install Node Manager on each machine that hosts Managed Server and Administration Server instances of WebLogic Server.

Note:

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

To install the Node Manager Windows Service during an initial installation, you must select a Custom installation. For more information, refer to the chapter that is appropriate for the type of installation you are performing:

Chapter 3, "Running the Installation Program in Graphical Mode"

Chapter 4, "Running the Installation Program in Console Mode"

Chapter 5, "Running the Installation Program in Silent Mode"

Note:

When installing in silent mode, you do not specify a Custom installation. Set the INSTALL_NODE_MANAGER_SERVICE data-value to yes to install the service.

If you do not install the service during the initial installation, you can install it after installation using the installNodeMgrSvc.cmd command. You can also uninstall it at any time using the uninstallNodeMgrSvc.cmd command. For more information, see Installing and Uninstalling the Node Manager Service..

Selecting Directories for Installation

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

Oracle Fusion Middleware

WebLogic Server, Coherence (if applicable)

The following illustration shows the basic Middleware home and Middleware products directory structure. Additional directories and files are also located in the Middleware home directory, as described in Table 2-4. The user_projects directory is not present until you create your first WebLogic domain.

Choosing a Middleware Home Directory

When you install WebLogic Server, you are prompted to specify a Middleware home directory. This directory serves as a repository for common files that are used by multiple Fusion Middleware products installed on the same machine. For this reason, the Middleware home directory can be considered a central support directory for all the Fusion Middleware products installed on your system.

The files in the Middleware home directory are essential to ensuring that WebLogic Server operates correctly on your system. They facilitate checking of cross-product dependencies during installation.

When you are installing WebLogic Server, you are prompted to choose an existing Middleware home directory or specify a path to create a new Middleware home directory. If you choose to create a new directory, the installation program automatically creates it for you.

The Middleware home directory is referenced as MW_HOME in Fusion Middleware documentation.

Middleware Home Considerations

Consider the following information when creating the Middleware home directory and installing Fusion Middleware products:

Do not include spaces in the name of your Middleware home directory. If the name of this directory contains spaces, the CLASSPATH may not be resolved properly.

You can install only one instance of each version of a WebLogic Server product in a single Middleware home directory. If you need to maintain separate versions of WebLogic Server on the same machine, each version must be in its own Middleware home directory.

For example, you can install only one instance of the current version of WebLogic Server in a Middleware home directory, but you can have an earlier version of WebLogic Server in a separate Middleware home directory.

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, one of 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 Middleware home directory vary depending on the installer that you are using and the products you selected for installation.

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

Table 2-4 Directory Description for Middleware Home

Directory or file
Description

jdkversion

This directory 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)

This directory 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

This directory contains a history file, which has information about installation and uninstallation for the Middleware home directory.

modules

This directory contains the modules installed in the home directory.

utils

This directory contains utilities that are used to support the installation of all products installed in this home directory. For more information on installing patches and patch sets, see Oracle Smart Update Installing Patches and Maintenance Packs.

wlserver_version

The WebLogic Server home directory.

coherence_version

The Coherence home directory.

.home

This file contains the information about the Middleware home directory.

ocm.rsp

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

registry.xml

This registry file contains a persistent record of all WebLogic products installed on the target system. This registry contains product-related information, such as version number, patch set level, patch level, and location of the product installation directories. It also contains the name of the installed JDK(s) and the Java home.

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 version of the registry.xml file.

domain-registry.xml

This registry file contains the location of all domains currently registered with this WebLogic Server installation. Whenever you add a new domain, it is registered in this file.

Notes:

Once you create WebLogic domains and applications, the Middleware home directory also contains a directory in which they are stored (the default location is user_projects). This directory contains applications and domains sub-directories. The applications directory contains a sub-directory for each application you create, and the domains directory contains a sub-directory for each domain you create.

You may want to create all domains for your environment outside of the Middleware home directory. This makes it easier for you to remove an existing installation, or upgrade to a newer version of WebLogic Server, without having to recreate your domains and applications.

Creating Multiple Home Directories

Although in most situations, a single Middleware home directory is sufficient, it is possible to create more than one Middleware home directory. For example, you need to maintain multiple Middleware home directories in the following situations:

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 without modifying the production environment until you are ready to do so.

You want to maintain two different versions of WebLogic Server at the same time. For example, you may want to install a new version of WebLogic Server while keeping your existing version of WebLogic Server intact. In this case, you must install each WebLogic Server version in its own Middleware home directory.

Note:

You do not have to create a second Middleware home directory when using an Upgrade installer to upgrade an existing WebLogic Server installation to the current patch release. For example, if you are upgrading from WebLogic Server 10.3.1 to WebLogic Server 10.3.6 using an Upgrade installer, when running the WebLogic Server 10.3.6 Upgrade installer, you must select the Middleware home directory in which WebLogic Server 10.3.1 resides.

The registry.xml file in your WebLogic Server installation is corrupted.

After installation, the shared modules directory would contain multiple versions of one or more of the same third-party products.

Choosing Product Installation Directories

On the Choose Product Installation Directories screen of the installation program, you are prompted to enter the home directories for the following products:

Oracle WebLogic Server

Oracle Coherence (only if you selected this component for installation)

The WebLogic Server home directory contains all the WebLogic Server components that you choose to install on your system, including program files and examples.The default installation directory for WebLogic Server 10.3.6 is C:\MW_HOME\wlserver_10.3. This directory path is referenced as the WL_HOME directory in Fusion Middleware documentation.

The default installation directory for Coherence is C:\MW_HOME\coherence_version.

Installation Modes

You can run the installation program 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."

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. You use an XML properties file to specify the installation options. You can run silent-mode installation from either a script or from the command line. Silent-mode installation allows you to define the installation configuration only once, and then use that configuration to duplicate the installation on many machines. For more information about silent mode installation, see Chapter 5, "Running the Installation Program in Silent Mode."

Note:

Silent mode installation is supported only for Package installers.

Choosing the Type of Installation

When performing a graphical mode or console mode installation, the installation program provides two types of installation (Typical and Custom).

In a Typical installation, most 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. On Windows machines, if you want to install the Node Manager Windows Service, select a Custom installation. See About Installing Node Manager as a Windows Service, for more information about tis service.

For a list of the software components provided with your product distribution, and which are included in a Typical installation, see Installable Product Components.

Sample domains preconfigured to use the Derby database are created only for the installed components.

On Windows and Linux systems, two JDKs are installed:

JRockit 1.6.0 JDK

Sun JDK 1.6.0

Installable Product Components

Table 2-5 describes the components that are available for installation. Components that are installed in a Typical installation are indicated by an asterisk (*). If you do not want to install some of these components, or if you want to install additional components, perform a Custom installation.

Notes:

As of WebLogic Server 10.3.2, Workshop for WebLogic no longer ships with WebLogic Server. When upgrading from a prior WebLogic release to WebLogic Server 10.3.2 or 10.3.3, however, you can continue to use previously installed Workshop components. Oracle recommends that you use JDeveloper instead.

You can also use Oracle Enterprise Pack for Eclipse as a replacement for WorkShop.

As of WebLogic Server 10.3.4, Workshop for WebLogic is no longer supported.

Table 2-5 Installation Components

Component
Description

Core Application Server*

A complete application server that implements Java Enterprise Edition 5 (JEE 5) technologies, Web services, and other leading Internet standards to provide a reliable framework for highly available, scalable, and secure applications and services. Includes the full set of components that comprise the essential WebLogic Server run time with full JEE 5 support.

This component does not include administration tools and add-on technologies, such as the Administration Console, Web Server plug-ins, JDBC drivers, and so on.

Administration Console*

The Web application for configuring, administering, and monitoring WebLogic domains.

If you do not install the Administration Console, the console will not be available when you start the Administration Server.

For information, see "About the Administration Console" in Introduction to Oracle WebLogic Server.

Configuration Wizard and Upgrade Framework*

The Configuration Wizard guides you through the process of creating a domain for your target environment and selecting the configuration options you want to include. The Upgrade Framework provides tools that convert a domain configuration from previous WebLogic Server releases to the current release.

If you choose not to install this component, you will not be able to create new domains or upgrade pre-Version 9.0 domains. (If you exclude this component, you can still work with existing domains as long as they were created with the current version of WebLogic Server.) For example, you can deselect this component if you are installing in a production environment to which you subsequently migrate domain configurations that were created in a separate, pre-production environment.

Note: The WebLogic Scripting Tool (WLST) has a dependency on the Configuration Wizard. WLST is available only if you select this component for installation.

For information about the Configuration Wizard, see Creating Domains Using the Configuration Wizard. For information about the upgrade tools, see Upgrade Guide for Oracle WebLogic Server.

Web 2.0 HTTP Pub-Sub Server*

A channels based publish-subscribe mechanism for Web-based clients to send and receive asynchronous messages over HTTP. The HTTP Publish-Subscribe server can be used by Web clients to subscribe to channels (a representation in Bayeux for destinations) and publish messages to the channels. Developers are recommended to install the pub-sub sample, available by selecting the Server Examples product component.

If this component is not installed, you will not be able to take advantage of Web 2.0 HTTP Publish-Subscribe functionality.

For more information, see "Using the HTTP Publish-Subscribe Server" in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server.

WebLogic SCA*

This is a Spring container for Java applications that use SCA semantics to expose services and invoke references. The container is included as an optional library in WebLogic Server.

WebLogic JDBC Drivers*

WebLogic implementation of JDBC drivers that can be used to connect a WebLogic Server environment to an external database.

If this component is not installed, the WebLogic JDBC drivers will not be available for use.

For more information about this component, see Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.

Third-Party JDBC Drivers*

Other JDBC drivers bundled with WebLogic Server that can be used to connect a WebLogic Server environment to an external database.

If this component is not installed, the following JDBC drivers and files bundled with WebLogic Server will not be available for use:

The following Oracle Thin driver files:

ojdbc5_g.jar (debug version)

ojdbc6_g.jar (debug version for use with JDK 6)

orai18n.jar (internationalization support)

oraci18n-mapping.jar

ojdbc6dms.jar

ojdbc5.jar

The following third-party MySQL driver file:

mysql-connector-java-commercial-5.0.3-bin.jar

For more information about this component, see "Using JDBC Drivers with WebLogic Server" in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.

WebLogic Server Clients*

Thin-client JARs required for connecting to a WebLogic Server instance. Includes the JARs for the Web Services, JMS, Store and Forward, WebLogic RMI, JMS .NET, and JMX clients.

If you do not install this component, there is no effect on the server run time or deployed applications. However, if you have a thin client and need to distribute a smaller set of JARs, instead of all WebLogic JARs, you need to choose this installation option.

For more information about this component, see "Overview of Stand-alone Clients" in Programming Stand-alone Clients for Oracle WebLogic Server.

WebLogic Web Server Plug-Ins*

The WebLogic plug-ins for the Apache, Sun One and IIS Web servers used for connecting to WebLogic Server.

If you do not install this component, there is no effect on the server run time or your deployed applications.

For more information about this component, see Using Web Server Plug-Ins with Oracle WebLogic Server.

UDDI and XQuery Support*

The WebLogic Universal Description, Discovery and Integration (UDDI) and UDDI Directory Explorer applications.

The UDDI Project is an industry initiative that is working to enable businesses to quickly, easily, and dynamically find and carry out transactions with one another. A populated UDDI registry contains cataloged information about businesses, the services that they offer, and communication standards and interfaces they use to conduct transactions. Built on the Simple Object Access Protocol (SOAP) data communication standard, UDDI creates a global, platform-independent, open architecture space that benefits businesses.

If you do not install this component, the WebLogic UDDI and UDDI Directory Explorer applications will not be available in the server run time. If your application depends on the UDDI and UDDI Directory Explorer applications, you need to choose this installation option.

For more information about WebLogic UDDI, see "Publishing and Finding Web Services Using UDDI" in Programming Advanced Features of JAX-WS Web Services for Oracle WebLogic Server.

This component also includes the WebLogic XQuery implementation JARs. Select this installation option if you are using WebLogic XQuery libraries within your applications.

Server Examples

Example applications that demonstrate key features of WebLogic Server. Selecting this component also causes an evaluation database to be installed. For more information, see "Sample Application and Code Examples" in Information Roadmap for Oracle WebLogic Server .

Note: Server Examples are not installed as part of the Typical installation. You must select Custom installation in order to install the Server Examples on your system.

Note: If you select this option, you cannot deselect the Evaluation Database option. The Derby evaluation database is required by the server examples.

Evaluation Database

Installs the Derby evaluation database, which is used by the Server Examples, into the WL_HOME/common/derby directory. You may, however, install the evaluation database without installing the Server Examples. The evaluation database is installed by default in a Typical installation.

Coherence Product Files*

Coherence provides replicated and distributed (partitioned) data management and caching services on top of a reliable, highly scalable peer-to-peer clustering protocol. Coherence has no single points of failure; it automatically and transparently fails over and redistributes its clustered data management services when a server becomes inoperative or is disconnected from the network. When a new server is added, or when a failed server is restarted, it automatically joins the cluster and Coherence fails back services to it, transparently redistributing the cluster load. Coherence includes network-level fault tolerance features and transparent soft re-start capability to enable servers to self-heal.

For more information about Coherence, see Oracle Coherence Getting Started Guide.

Coherence Examples

Examples that demonstrate how to use the features of Coherence in all supported languages (Java, .NET, and C++). The examples are organized collections of code that show how to use one or more features, and provide a single common way (per language) to build and run all examples. Source code for the examples is included.

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 WebLogic Server Package installer for Windows, enter:

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

3 Running the Installation Program in Graphical Mode

This chapter describes how to start the installation program in graphical mode in different environments. It also describes the sequence of screens that may appear in the installation process.

Note:

In order 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 in console mode.

This chapter contains the following sections:

Starting the Installation Program in Graphical Mode

Installation Screens

Running the Upgrade Installer in Graphical Mode

Starting the Installation Program in Graphical Mode

The following sections describe how to start the installation program in graphical mode in different environments:

Starting the Installation Program in Graphical Mode on Windows

Starting .bin Installation Programs in Graphical Mode on UNIX Machines

Starting .jar installation Programs in Graphical Mode

Starting the Installation Program in Graphical Mode on Windows

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

Log in to the Windows system.

Go to the directory that contains the installation program.

Double-click the installation file.

For example, the name of the installation program for the WebLogic Server Package installer for Windows 32-bit is wls1036_win32.exe.

The installation program begins to install the software.

See Installation Screens for a description of each installation program screen.

Starting .bin Installation Programs in Graphical Mode on UNIX Machines

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

Log in to the target UNIX system.

Go to the directory that contains the installation program.

Launch the installation by entering the following commands:

chmod a+x file_name.bin

./file_name.bin

file_name.bin is the name of your installation program. For example, for WebLogic Server 10.3.6, the name of the Package installer file for Solaris is wls1036_solaris32.bin.

Note:

If you plan to install the Server Examples, you must include the following parameter in the installation command. Otherwise, the installation may take longer than expected.

-Djava.security.egd=file:/dev/./urandom

The installation program begins to install the software.

See Installation Screens for a description of each installation program screen.

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.

Notes:

If you are installing WebLogic Server on a 64-bit platform, see Installing WebLogic Server on 64-Bit Platforms Using a 64-Bit JDK, for more information.

If you are installing WebLogic Server on a UNIX or Linux operating system, you must include the following parameter in the installation command if you plan to install the Server Examples. Otherwise, the installation may take longer than expected.

-Djava.security.egd=file:/dev/./urandom

Log in to the target system.

Add the directory of the appropriate JDK to the PATH variable definition on the target system. For example, on UNIX or Linux systems, add the bin directory to the beginning of the PATH variable:

PATH=$JAVA_HOME/bin:$PATH; export PATH

Go to the directory where you downloaded the installation program.

Launch the installation program by entering the following command (this example shows the Generic installer):

java -jar wls1036_generic.jar

The installation program begins to install the software.

See Installation Screens for a description of each installation program screen.

Installing WebLogic Server on 64-Bit Platforms Using a 64-Bit JDK

If you are installing WebLogic Server on a 64-bit platform using a .jar installation program:

Add the directory of the appropriate JDK to the PATH variable definition on the target system. For example, on UNIX, add the bin directory of the appropriate 64-bit JDK to the beginning of the PATH variable definition on the target system:

JAVA_HOME=path_to_64-bit_JDK; export JAVA_HOME

PATH=$JAVA_HOME/bin:$PATH; export PATH

(UNIX or Linux only) Include the -d64 flag in the installation command when using a 32/64-bit hybrid JDK (such as for the HP-PA, HPIA, and Solaris64 platforms). For example, if installing in graphical mode using the Package installer:

java -d64 -jar wlsversion_generic.jar

Run the java -version command (or java -d64 -version command on UNIX or Linux platforms using a 32/64-bit hybrid JDK) to ensure that your JAVA_HOME refers to a 64-bit JDK.

If you are using the Sun 64-bit JDK, use the following command to install WebLogic Server:

java -Xmx1024m -jar wlsversion_generic.jar

Installation Screens

The installation program displays a series of screens, in the order listed in Table 3-1. Some screens are displayed only in certain situations, as noted in the table.

If you need additional help with any of the installation screens, see Appendix A, "Oracle WebLogic Server Installation Screens," or click the link in the Screen column of the following table.

Table 3-1 Running the Installation Program in Graphical Mode

No.
Screen
When Does This Screen Appear?
Perform the Following Action

1

Welcome

Always

Click Next to proceed with the installation.

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

2

Choose Middleware Home Directory

Always

Specify the Middleware home directory that will serve as the central support directory for all Fusion Middleware products installed on the target system, including WebLogic Server.

Click Next to continue.

3

Register for Security Updates

Always

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

If you chose not to register, an Are You Sure? dialog box appears. Click Yes to continue.

Click Next to continue.

4

Choose Install Type

This screen is displayed only during an initial installation.

Select the installation type.

Click Next to continue.

5

Choose Products and Components

This screen is displayed only under the following conditions:

You selected Custom installation.

You are adding components to an existing installation.

This screen displays a tree view of all the components available for installation.

Specify the components to be installed by selecting or clearing the appropriate check boxes.

Click Next to continue.

6

JDK Selection

This screen is displayed only if you selected a Custom installation. It is not displayed if you are running an Upgrade installer.

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

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

Click Next to continue.

7

Choose Product Installation Directories

This screen is displayed only during an initial installation.

Specify the directories in which you want to install the products (WebLogic Server and Coherence, if applicable).

Click Next to continue.

8

Confirm Product Installation Directory

This screen is displayed only if you are adding components to an existing installation, or you are running an Upgrade installer.

Click Next to continue.

9

Install Windows Service

This screen is displayed only if all of the following 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 screen.

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

Click Next to continue.

10

Choose Shortcut Location

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

Click Next to continue.

11

Installation Summary

In all situations except when running an Upgrade installer.

Click Next to continue.

12

Status

Always

When the installation program has finished copying the specified files to your system, click Next to continue.

13

Installation Complete

Always

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

Running the Upgrade Installer in Graphical Mode

If you are using an Upgrade installer, use the following steps to upgrade your installation in graphical mode.

Notes:

If you have an existing WebLogic Server 10.3.0, 10.3.1, 10.3.2, or 10.3.3 installation that includes Workshop for WebLogic, and you want to use an Upgrade installer to upgrade that installation to WebLogic Server 10.3.6, you must uninstall Workshop for WebLogic before running the Upgrade installer. See Chapter 7, "Uninstalling the Software," for more information.

If you do not remove Workshop prior to running the Upgrade installer, you can remove it after the upgrade only by reverting to the previous installation and running the WebLogic uninstall program to remove the WebLogic components. WebLogic Server 10.3.6 does not support removal of Workshop components.

When using an Upgrade installer to upgrade an existing WebLogic Server installation on Linux or UNIX operating systems, you must run the Upgrade installer using the same user ID as was used to perform the initial WebLogic Server installation.

Make backup copies of any files or applications that you have created in the WebLogic Server home directory. As part of the upgrade procedure, the installation program automatically overwrites any files, including applications, that you have created in this directory.

Note:

In some cases, changes are made in each domain's config.xml file between upgrade releases. You may want to make backup copies of the config.xml file in any domains you created, in case you later want to roll back or uninstall an upgrade installation.

Shut down any servers that are running.

Start the Upgrade installer as described in one of the following sections:

Starting the Installation Program in Graphical Mode on Windows

Starting .bin Installation Programs in Graphical Mode on UNIX Machines

Starting .jar installation Programs in Graphical Mode

Click Next on the Welcome screen.

On the Choose Middleware Home Directory screen, select an existing Middleware home directory or browse to an existing Middleware home that contains the WebLogic Server installation you want to upgrade. Click Next.

On the Register for Security Updates screen, make your selection and click Next.

On the Confirm Product Installation Directory screen, click Next.

The Status screen is displayed to indicate the progress of the installation. When the installation completes, the Installation Complete screen is displayed.

If you are using the JRockit SDK, Oracle recommends that you upgrade your domains to use the latest production version. See Configuring Domains to Use the Latest Version of JRockit.

4 Running the Installation Program in Console Mode

This chapter describes how to run the WebLogic Server installer in console mode in different operating system environments.

When installing WebLogic Server in console mode, 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) in response to any prompt. To review or change your selection, enter previous (or p) at the prompt. To proceed to the following window, enter next (or n).

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. For example, use forward slashes in path names, such as C:/Oracle/MW_HOME/wlserver_version.

This chapter contains the following sections:

Starting the Installation Program in Console Mode

Installing WebLogic Server in Console Mode

Running the Upgrade Installer in Console Mode

Starting the Installation Program in Console Mode

This section describes how to start the installation program in console mode in different environments. It contains the following sections:

Starting the Installation Program in Console Mode on Windows

Starting .bin Installation Programs in Console Mode

Starting .jar Installation Programs in Console Mode

Starting the Installation Program in Console Mode on Windows

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

Log in to the target Windows system.

Open a command prompt window.

Go to the directory that contains the installation program.

Launch the installation by entering the name of the installation program.

For example, to start the WebLogic Server Package installer for Windows in console mode, enter

wls1036_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 Generating a Verbose Installation Log.

After a few moments, the installation program begins to install the software. Proceed to Installing WebLogic Server in Console Mode, to continue.

Starting .bin Installation Programs in Console Mode

To start the installation program in console mode using a .bin installation file, follow these steps:

Log in to the target UNIX system.

Go to the directory that contains the installation program.

Launch the installation by entering the following commands:

chmod a+x file_name.bin

./file_name.bin -mode=console

file_name.bin is the name of your installation program. For example, for WebLogic Server 10.3.6, the name of the Package installer file for Solaris is wls1036_solaris32.bin.

Note:

If you plan to install the Server Examples, you must include the following parameter in the installation command. Otherwise, the installation may take longer than expected.

-Djava.security.egd=file:/dev/./urandom

After a few moments, the installation program begins to install the software. Proceed to Installing WebLogic Server in Console Mode, to continue.

Starting .jar Installation Programs in Console Mode

To start the installation program in console mode using a .jar installation file, follow these steps.

Note:

If you are installing WebLogic Server on a 64-bit platform, see Installing WebLogic Server on 64-Bit Platforms Using a 64-Bit JDK, for more information.

If you are installing WebLogic Server on a UNIX or Linux operating system, you must include the following parameter in the installation command if you plan to install the Server Examples. Otherwise, the installation may take longer than expected.

-Djava.security.egd=file:/dev/./urandom

Log in to the target system.

Add the directory of the appropriate JDK to the PATH variable definition on the target system. For example, on UNIX or Linux systems, add the bin directory to the beginning of the PATH variable:

PATH=$JAVA_HOME/bin:$PATH; export PATH

Go to the directory where you downloaded the installation program.

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.

After a few moments, the installation program begins to install the software. Proceed to Installing WebLogic Server in Console Mode, to continue.

Installing WebLogic Server on 64-Bit Platforms Using a 64-Bit JDK

If you are installing WebLogic Server on a 64-bit platform using a .jar installation program:

Add the directory of the appropriate JDK to the PATH variable definition on the target system. For example, on UNIX, add the bin directory of the appropriate 64-bit JDK to the beginning of the PATH variable definition on the target system:

JAVA_HOME=path_to_64-bit_JDK; export JAVA_HOME

PATH=$JAVA_HOME/bin:$PATH; export PATH

(UNIX or Linux only) Include the -d64 flag in the installation command when using a 32/64-bit hybrid JDK (such as for the HP-PA, HPIA, and Solaris64 platforms). For example, if installing in graphical mode using the Package installer:

java -d64 -jar wlsversion_generic.jar -mode=console

Run the java -version command (or java -d64 -version command on UNIX or Linux platforms using a 32/64-bit hybrid JDK) to ensure that your JAVA_HOME refers to a 64-bit JDK.

If you are using the Sun 64-bit JDK, use the following command to install WebLogic Server:

java -Xmx1024m -jar wlsversion_generic.jar -mode=console

Installing WebLogic Server in Console Mode

After starting the installation program, follow these steps to complete the installation:

At the Welcome: prompt, type next (or n), or press Enter to continue with the installation process.

The Choose Middleware Home Directory prompt is displayed.

Specify the Middleware home directory that will serve as the central support directory for all Fusion Middleware products (including WebLogic Server) installed on the target system. For information about the Middleware home directory, see Choosing a Middleware 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, enter the number associated with the home directory.

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

If there are no Middleware home directories on your system, or you selected Create a new Middleware Home, do one of the following:

To use the default home directory, enter next (or n), or press Enter.

To create a home directory, enter the full path of the home directory, for example C:\Oracle\Middleware. 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, enter 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, the Register for Security Updates: prompt is displayed.

To register for security updates, you must have a valid My Oracle Support account. By registering for security updates, Oracle Support notifies you immediately of any security updates that are specific to your installation.

If you want to register for security updates:

Enter 1, and then enter the email address for your My Oracle Support account.

Enter 2, and then enter the password for your My Oracle Support account.

Verify that Receive Security Update is set to Yes. If it is set to No, enter 3, and then enter Yes.

If you do not want to register for security updates, Enter 3, and then enter No. You are prompted to confirm that you want to bypass initiation of the Configuration Manager. Enter Yes.

After making the selections for security updates, press Enter to continue.

If you are performing an initial installation, the Choose Install Type prompt is displayed. Go to step 5.

If you are adding components to an existing installation, the Choose Products and Components prompt is displayed. Go to step 6.

(This step applies only if you are doing an initial installation) Specify the type of installation you want to perform by entering the number associated with the install type.

To select a Typical installation, enter 1 or press Enter and proceed to step 8.

To select Custom installation, enter 2. The Choose Products and Components to install prompt is displayed. Go to step 6.

For more information about Typical and Custom installations, see Choosing the Type of Installation.

(This step applies only if you are doing an initial Custom installation) Select the components you want to install. Selected components are indicated by a check mark. By default, the following items are already selected for installation:

WebLogic Server and all its subcomponents, except for Server Examples (1.11)

Oracle Coherence/Oracle Coherence Product Files

If you are adding components or products, the text [Installed] is shown 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.

To select a component that is not already selected, enter its associated number. For example, to select the WebLogic Server Server Examples, enter 1.11. A check mark appears next to the component.

To clear a component that is already selected, enter its associated number. For example, if the Third Party JDBC Drivers component is already selected, enter 1.7 to clear the selection.

When you select or clear components, the installation program checks for dependencies between the components and automatically modifies the list of selected components.

After selecting the required components, enter n or press Enter.

(This step applies only if you are doing an initial Custom installation.) The JDK Selection prompt is displayed. Select the JDK(s) you want to add. Currently selected JDKs are indicated by a check mark.

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(s) and proceed with the installation, press Enter.

Wait while the installer searches for the required archive files.

The Choose Product Installation Directories prompt appears. Specify the directory in which you want to install the software.

Note:

If you are adding components to an existing installation, the Confirm Product Installation Directories prompt appears instead. You cannot change the directories; new components will be installed to the original product installation directory. Press Enter to continue.

To accept the default product directories, press Enter to continue.

To change a product installation directory:

Enter the number for the product for which you want to change the installation directory.

Type the full path of the installation directory, and press Enter.

When done, press Enter to continue the installation.

(This step applies only if you are doing an initial Custom installation on Windows, and you have Administrator privileges.) The Install Node Manager as Windows Service prompt is displayed. To specify whether you want to install Node Manager as a Windows service:

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.

(This step applies only if you are doing an initial installation on Windows, and you have Administrator privileges.) The Choose Shortcut Location prompt is displayed. Specify the folder in which you want to create the Start menu shortcuts.

Do one of the following:

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

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

When prompted to confirm your selection, enter 1 or press Enter to proceed with the installation. Otherwise, enter 2 to return to the previous panel, where you can modify your entry.

(This step does not apply if you are running an Upgrade installer.) The list of products and JDKs to be installed is displayed, as well as the estimated size of the installation.

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 completes, the following message is displayed:

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

Running the Upgrade Installer in Console Mode

If you are using an Upgrade installer, use the following steps to upgrade your installation in console mode.

Notes:

If you have an existing WebLogic Server 10.3.0, 10.3.1, 10.3.2, or 10.3.3 installation that includes Workshop for WebLogic, and you want to use an Upgrade installer to upgrade that installation to WebLogic Server 10.3.6, you must uninstall Workshop for WebLogic before running the Upgrade installer. See Chapter 7, "Uninstalling the Software," for more information.

If you do not remove Workshop prior to running the Upgrade installer, you can remove it after the upgrade only by reverting to the previous installation and running the WebLogic uninstall program to remove the WebLogic components. WebLogic Server 10.3.6 does not support removal of Workshop components.

When using an Upgrade installer to upgrade an existing WebLogic Server installation on Linux or UNIX operating systems, you must run the Upgrade installer using the same user ID as was used to perform the initial WebLogic Server installation.

Make backup copies of any files or applications that you have created in the WebLogic Server home directory. As part of the upgrade procedure, the installation program automatically overwrites any files, including applications, that you have created in this directory.

Note:

In some cases, changes are made in each domain's config.xml file between upgrade releases. You may want to make backup copies of the config.xml file in any domains you created, in case you later want to roll back or uninstall an upgrade installation.

Shut down any servers that are running.

Start the Upgrade installer as described in one of the following sections:

Starting the Installation Program in Console Mode on Windows

Starting .bin Installation Programs in Console Mode

Starting .jar Installation Programs in Console Mode

At the Welcome prompt, type n or press Enter to continue.

At the Choose Middleware Home Directory prompt, enter the number for the Middleware home directory that contains the WebLogic Server installation you want to upgrade, or enter 1 and then enter the full path to the Middleware home directory. Click Next.

To register for security updates, you must have a valid My Oracle Support account. By registering for security updates, Oracle Support notifies you immediately of any security updates that are specific to your installation.

If you want to register for security updates, at the Register for Security Updates prompt:

Enter 1, and then enter the email address for your My Oracle Support account.

Enter 2, and then enter the password for your My Oracle Support account.

Verify that Receive Security Update is set to Yes. If it is set to No, enter 3, and then enter Yes.

If you do not want to register for security updates, Enter 3, and then enter No. You are prompted to confirm that you want to bypass initiation of the Configuration Manager. Enter Yes.

After making your selections for security updates, press Enter.

At the Confirm Product Installation Directory prompt, click Next.

The Status screen is displayed to indicate the progress of the installation. When the installation completes, the Installation Complete message is displayed. Press any key to exit the installation program.

If you are using the JRockit SDK, Oracle recommends that you upgrade your domains to use the latest production version. See Configuring Domains to Use the Latest Version of JRockit.

5 Running the Installation Program in Silent Mode

This chapter describes how to run the WebLogic Server installer in silent mode.

The following sections are included here:

What Is Silent-Mode Installation?

Overview of Silent-Mode Installation Steps

Creating a silent.xml File for Silent-Mode Installation

Starting Silent Mode Installation

Exit Codes for Silent Mode Installation

Sample silent.xml File for Silent Mode Installation

Running the Upgrade Installer in Silent Mode

What Is Silent-Mode Installation?

Silent-mode installation allows you to define an installation configuration only once and then use the configuration 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 as described in Product Distribution.

Overview of Silent-Mode Installation Steps

The silent-mode installation process has two primary steps:

Create a silent.xml file that defines the installation configuration that you would normally enter during an interactive installation process, such as graphical-mode or console-mode installation. For example, in silent.xml, you can supply the values for the Middleware home directory, the product directory, and the components to be installed.

For more information, see Creating a silent.xml File for Silent-Mode Installation.

Start the silent-mode installation as described in the section that is appropriate for your situation:

Starting the Installation Program in Silent Mode on Windows

Starting .bin Installation Programs in Silent Mode

Starting .jar installation programs in Silent Mode

Important Considerations for Silent-Mode Installation

When using silent mode, keep the following considerations in mind:

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, Oracle recommends 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 Middleware home directory or in the same file location. 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.

You can, however, add products and product components to an existing installation. For example, you can install Core Application Server, Administration Console, and Configuration Wizard Upgrade Framework during one installation, and add WebLogic JDBC Drivers and Server Examples during a separate installation.

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. Before you can run the installation program in silent mode, you must first create a silent.xml file.

To create a silent.xml file:

Copy the sample code provided in Sample silent.xml File for Silent Mode Installation, and paste the code in an XML file.

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.

In the silent.xml file that you saved on your system, edit the values for the data-value names to reflect your configuration.

Table 5-1 describes all of the data-value names that are currently available.

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 WebLogic Server

Data-Value Name
Description

BEAHOME

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

OCM_PROXY_HOST
OCM_PROXY_PORT
OCM_PROXY_USER
OCM_PROXY_PASSWORD

These parameters enable support for Oracle Configuration Manager (OCM). If your computer connects to the internet via a proxy server, use these data-values to specify the host name, port number, user name, and password for the proxy server.

OCM_SUPPORT_EMAIL
OCM_SUPPORT_PASSWORD

If you have a My Oracle Support account and want to receive security updates from Oracle, specify the email address and password for your My Oracle Support account.

If you do not want to receive security updates from Oracle, do not specify these values.

WLS_INSTALL_DIR

The full path for the directory where you want to install WebLogic Server (for example, for Windows:

C:\MW_HOME\wlserver_10.3

where MW_HOME is the name of the Middleware home directory specified by the BEAHOME data-value name).

OCP_INSTALL_DIR

The full path for the directory where you want to install Coherence (for example, for Windows:

C:\MW_HOME\coherence_3.7

where MW_HOME is the name of the Middleware home directory specified by the BEAHOME data-value name).

COMPONENT_PATHS

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

To install WebLogic Server components, 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 SCA
|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
|WebLogic Server/Evaluation Database

To install Coherence components, use the following syntax:

Oracle Coherence/Coherence Product Files
|Oracle Coherence/Coherence Examples

For additional information about entering these values, see Guidelines for Component Selection. Note that you should not have any spaces between components, as shown in the example in Sample silent.xml File for Silent Mode Installation,

INSTALL_NODE_MANAGER_SERVICE

(Windows platforms only)

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

no to skip the installation of the 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 Node Manager.

Note: The INSTALL_NODE_MANAGER_SERVICE option must be set to yes.

When the installation process completes, Node Manager is started using the specified port.

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 person performing the installation must have administrator privileges to install the Start menu shortcuts in the All Users folder. For more information, see Administrator Privileges.

LOCAL_JVMS

This is an optional element with 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 you can use to specify the Oracle-supplied JDKs to be installed. Enter the full path of the JDKs to be installed, separated by the pipe symbol ('|').

Guidelines for Component Selection

Use the following guidelines when 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 all WebLogic Server components:

<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 the WebLogic Server component (and all of its subcomponents) and Coherence, enter:

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

To specify subcomponents, you must specify a component/subcomponent combination for each entry.

For example, to install specific components of WebLogic Server and also install only the Oracle Coherence product files (but not the Coherence samples), enter the following line in the file:

<data-value name="COMPONENT_PATHS" value="WebLogic Server/Core Application
Server|WebLogic Server/Administration Console|Oracle Coherence|Oracle
Coherence Product Files"/>

If you do not include the COMPONENT_PATHS data-value name in silent.xml, the complete WebLogic Server and Coherence products are installed.

Note:

The installation program performs dependency checking to ensure that all components that provide functionality on which other components depend are installed. These dependencies are visible during graphical and console mode installations. The same dependencies are enforced during silent mode installation. Components on which other components depend are installed even if they are not explicitly referenced in silent.xml.

Starting Silent Mode Installation

This section describes how to start a silent mode installation on a Windows or UNIX machine. It contains the following sections:

Starting the Installation Program in Silent Mode on Windows

Starting .bin Installation Programs in Silent Mode

Starting .jar installation programs in Silent Mode

Note:

Incorrect entries in silent.xml can cause installation failures. To help you determine the cause of a failure, Oracle recommends that you create a log file when you start the installation. See Generating a Verbose Installation Log.

Starting the Installation Program in Silent Mode on Windows

To start the installation program in silent mode on a Windows system, follow these steps:

Log in to the Windows system.

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 Creating a silent.xml File for Silent-Mode Installation.

Open a command prompt window.

Go to the directory that contains the installation program.

Start the installer.

For example, to launch the WebLogic Server Package installer on Windows 32-bit platforms, enter:

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

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

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

Starting .bin Installation Programs in Silent Mode

When using a .bin installation file, follow these steps to start a silent-mode installation:

Log in to the target UNIX system.

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 Creating a silent.xml File for Silent-Mode Installation.

Go to the directory that contains the installation program.

Launch the installation program by entering the following commands:

chmod a+x file_name.bin

./file_name.bin -mode=silent -silent_xml=path_to_silent.xml

In this command, file_name.bin is the name of the installation file and path_to_silent.xml is the full path of the silent.xml file.

Note:

If you plan to install the Server Examples, you must include the following parameter in the installation command. Otherwise, the installation may take longer than expected.

-Djava.security.egd=file:/dev/./urandom

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

Starting .jar installation programs in Silent Mode

When using a .jar installation file, follow these steps to start a silent mode installation.

Notes:

If you are installing WebLogic Server on a 64-bit platform, see Installing WebLogic Server on 64-Bit Platforms Using 64-Bit JDK, for more information.

When you run the Generic Upgrade installer, include the -Xmxsize[g|G|m|M|k|K] option in the command to ensure that the heap size is adequate.

If you are installing WebLogic Server on a UNIX or Linux operating system, you must include the following parameter in the installation command if you plan to install the Server Examples. Otherwise, the installation may take longer than expected.

-Djava.security.egd=file:/dev/./urandom

Log in to the target system.

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 Creating a silent.xml File for Silent-Mode Installation.

Add the directory of the appropriate JDK to the PATH variable definition on the target system. For example, on UNIX or Linux systems, add the bin directory to the beginning of the PATH variable:

PATH=$JAVA_HOME/bin:$PATH; export PATH

Go to the directory that contains the installation file.

Launch the installation by entering the following command:

java -jar file_name.jar -mode=silent -silent_xml=path_to_silent.xml

In this command, file_name.jar is the name of the installation file and 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.

Installing WebLogic Server on 64-Bit Platforms Using 64-Bit JDK

If you are installing WebLogic Server on a 64-bit platform using a .jar installation program:

Add the directory of the appropriate JDK to the PATH variable definition on the target system. For example, on UNIX, add the bin directory of the appropriate 64-bit JDK to the beginning of the PATH variable definition on the target system:

JAVA_HOME=path_to_64-bit_JDK; export JAVA_HOME

PATH=$JAVA_HOME/bin:$PATH; export PATH

(UNIX or Linux only) Include the -d64 flag in the installation command when using a 32/64-bit hybrid JDK (such as for the HP-PA, HPIA, and Solaris64 platforms). For example, if installing in graphical mode using the Package installer:

java -d64 -jar filename.jar -mode=silent -silent_xml=path_to_silent.xml

Execute the java -version command (or java -d64 -version command on UNIX or Linux platforms using a 32/64-bit hybrid JDK) to ensure that your JAVA_HOME refers to a 64-bit JDK.

If you are using the Sun 64-bit JDK, use the following command to install WebLogic Server:

java -Xmx1024m -jar filename.jar -mode=silent -silent_xml=path_to_silent.xml

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.

Sample silent.xml File for Silent Mode Installation

The following sample silent.xml file installs all default components of WebLogic Server, the optional Server Examples sub-component of WebLogic Server, and the Product Files component of Coherence.

Note:

The Evaluation Database component is automatically installed if the Server Examples component is included in silent.xml. Therefore, it does not have to be explicitly included in silent.xml. If, however, you do not install the Server Examples, but you want to install the Evaluation Database, you must include WebLogic Server/Evaluation Database in silent.xml.

<!-- Silent installer option -mode=silent -silent_xml=C:\myfiles\silent.xml -->
<!-- Specify values for each data-value name as follows:

     BEAHOME            Complete pathname to the Middleware 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.
-->

<?xml version="1.0" encoding="UTF-8"?>
   <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|Oracle Coherence/Coherence Product Files" />
       <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>

Running the Upgrade Installer in Silent Mode

The process for upgrading an installation in silent mode is similar to the process for a full installation in silent mode, except that the silent.xml file is much simpler. Please note the following issues when performing an upgrade in silent mode:

If you created a silent.xml file when you initially installed WebLogic Server, you should store it in a safe location or make a backup copy of it so that you do not accidentally overwrite it with the silent.xml file you are creating for your upgrade installation. Alternatively, you can name your upgrade file using a different file name, for example silent_upgrade.xml.

Incorrect entries in silent.xml can cause installation failures. To help you determine the cause of a failure, Oracle recommends that you create a log file when you start the installation. See Generating a Verbose Installation Log.

When using an Upgrade installer to upgrade an existing WebLogic Server installation on Linux or UNIX operating systems, you must run the Upgrade installer using the same user ID as was used to perform the initial WebLogic Server installation.

If you are upgrading an existing WebLogic Server 10.3.0, 10.3.1, 10.3.2, or 10.3.3 installation that includes Workshop for WebLogic, you must uninstall the Workshop components before upgrading your software. You must use either GUI mode or console mode to remove the Workshop components. See Uninstalling the Software, for more information.

If you do not remove Workshop prior to running the Upgrade installer, you can remove it after the upgrade only by reverting to the previous installation and running the WebLogic uninstall program to remove the WebLogic components. WebLogic Server 10.3.6 does not support removal of Workshop components.

To run the Upgrade installer in silent mode:

Create a silent.xml file (or silent_upgrade.xml file) to specify the Middleware home directory that contains the WebLogic Server installation you want to upgrade. See the sample in Sample silent.xml File for Upgrade Installation.

Save the XML file in the directory in which the Upgrade installer is stored.

Start the Upgrade installer as described in one of the following sections:

Starting the Installation Program in Silent Mode on Windows.

Starting .bin Installation Programs in Silent Mode.

Starting .jar installation programs in Silent Mode.

Make sure that the -silent_xml option points to the XML file you created for the upgrade installation.

After the installation completes, if you are using the JRockit SDK, Oracle recommends that you upgrade your domains to use the latest production version. See Configuring Domains to Use the Latest Version of JRockit.

Sample silent.xml File for Upgrade Installation

When using an Upgrade installer, the silent.xml file needs to define only the BEAHOME data value name. This is the Middleware home directory that contains the WebLogic Server installation you want to upgrade. See the following example, where C:\Oracle\Middleware is the Middleware home directory where WebLogic Server is installed. Update this value to the appropriate directory for your installation.

<?xml version="1.0" encoding="ISO-8859-1" ?>
<domain-template-descriptor>
<input-fields>
<data-value name="BEAHOME" value="c:\Oracle\Middleware" />
</input-fields>
</domain-template-descriptor>

6 Post-Installation Information

This chapter describes common post-installation tasks and information, including how to use QuickStart and how create a WebLogic domain. It also describes how to determine your JDK version, the Node Manager service, Windows shortcuts, upgrading, and patch installation. It also includes a section on how to configure domains to use the latest JRockit version.

The following sections are included in this chapter:

Using QuickStart

Determining Which JDK Version You Are Using

Creating a WebLogic Domain

Installing and Uninstalling the Node Manager Service

Understanding the Windows Shortcuts

Upgrading WebLogic Server

Installing Patches

Configuring Domains to Use the Latest Version of JRockit

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 screen. QuickStart is not invoked for console-mode or silent-mode installations.

QuickStart is designed to help first-time users evaluate, learn, and use WebLogic Server.

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

Getting started with WebLogic Server

Starting the WebLogic Server samples domain

Upgrading WebLogic domains to the current version

Accessing documentation online

After installation, you can launch QuickStart as follows:

On Windows systems, choose Start > Programs > Oracle WebLogic > QuickStart.

On UNIX systems:

Log in to the target UNIX system.

Go to the /common/quickstart subdirectory of your installation. For example:

cd /MW_HOME/wlserver_10.3/common/quickstart

Enter the following command:

sh quickstart.sh

Determining Which JDK Version You Are Using

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

Open a command prompt window and go to the appropriate directory:

Windows system:

WL_HOME\server\bin

UNIX system:

WL_HOME/server/bin

Make sure that your environment is set up properly by entering the following command at the prompt:

Windows:

setWLSenv.cmd

UNIX:

. ./setWLSenv.sh

Enter the following command at the prompt:

java -version

If you are using JRockit, JRockit(R) is displayed in the output.

Creating a WebLogic Domain

After you install WebLogic Server, you can create a WebLogic domain. There are several ways to create a WebLogic domain:

Use the Fusion Middleware Configuration Wizard to create a domain using one or more domain templates.

If you are installing other Fusion Middleware products, such as SOA or WebCenter, this is the recommended method. For example, after you complete the SOA product installation, it includes domains templates that make it easy for you to create a WebLogic domain for SOA that contains the required domain resources, such as an Administration Server, Managed Servers, clusters, and JDBC resources.

If you are not installing other Fusion Middleware products, you can create a new domain by using the starter domain template, wls_starter.jar, which is available in the following folder.

WL_HOME\common\templates\domains

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 WebLogic domain by using an existing domain template, see "Creating a WebLogic Domain" in Creating Domains Using the Configuration Wizard.

Use the WebLogic Scripting Tool to create a domain. See "Creating WebLogic Domains Offline" in Oracle WebLogic Scripting Tool.

Use the unpack command to create a domain. You can use this command to create a WebLogic domain from the command line, by using a template that is compatible with your current installation. See "The unpack Command" in Creating Templates and Domains Using the Pack and Unpack Commands.

Note:

You cannot use unpack to extend an existing domain.

Installing and Uninstalling the Node Manager Service

On Windows machines, if you did not install the Node Manager Windows Service when you initially installed WebLogic Server, you can use the following steps to install it:

Log in to the machine with Administrator privileges.

Open a DOS command prompt window.

Change to the WL_HOME\server\bin directory, where WL_HOME is the WebLogic Server home directory (C:\Oracle\Middleware\wlserver_10.3 by default).

Enter the following command:

installNodeMgrSvc.cmd

After a few seconds, the following message is displayed:

Oracle WebLogic NodeManager (C_Oracle_Middleware_wlserver_10.3) installed.

The service is installed using the default Node Manager listen port (5556). If this listen port is already in use, the program prompts you to enter a different listen port.

Note:

If the Node Manager Windows Service is already installed, the following message is displayed instead:

CreateService failed - The specified service already exists.

If you want to uninstall the Node Manager Windows Service, use the following steps:

Log in to the machine with Administrator privileges.

Open a DOS command prompt window.

Change to the WL_HOME\server\bin directory, where WL_HOME is the WebLogic Server home directory (C:\Oracle\Middleware\wlserver_10.3 by default).

Enter the following command:

uninstallNodeMgrSvc.cmd

After a few seconds, the following message is displayed:

Oracle WebLogic NodeManager (C_Oracle_Middleware_wlserver_10.3) removed.

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 Local User Start menu folder. For more information, see Administrator Privileges.

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

WebLogic Server 11gR1—Contains a shortcut for launching the default WebLogic domain, examples, tools, and online documentation.

The WebLogic Server domain enables you to run pre-built 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.

If you installed the Server Examples, the Examples folder contains shortcuts for starting and stopping the example servers, as well as a shortcut to launch the WebLogic Server Code Examples documentation.

The Tools folder contains shortcuts to launch the WebLogic Server tools (Configuration Wizard, Domain Template Builder, Domain Upgrade Wizard, Node Manager, and WebLogic Scripting Tool).

Online Documentation—Provides a link to the online documentation.

QuickStart—Starts the QuickStart application designed to assist first-time users with evaluating, learning, and using the software.

Smart Update—Launches the Smart Update program, which you can use to install patches that you downloaded from My Oracle Support.

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

Note:

After you create domains, the name of the directory in which your domain directories are stored is also displayed on the Oracle WebLogic menu. The default is user_projects. This menu entry allows you to start and stop the Administration Server, or start the Administration Console, for a given domain.

Upgrading WebLogic Server

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

Installing Patches

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

Note:

As of WebLogic Server 10.3.4, you can no longer use Smart Update to download and install WebLogic Server patch set releases.

You can also install all currently available patches by using an Upgrade installer. When using a WebLogic Server Upgrade installer to upgrade an existing WebLogic Server installation on Linux or UNIX operating systems, you must run the Upgrade installer using the same user ID as was used to perform the initial WebLogic Server installation. See Types of Installers, and Downloading an Upgrade Installer From My Oracle Support, for more information.

Note:

If you also need to install patches for other Fusion Middleware 11g Release 1 products, such as SOA or WebCenter, that are installed in your WebLogic Server environment, refer to the Oracle Fusion Middleware Patching Guide before installing WebLogic Server patches or updating your WebLogic Server installation.

Configuring Domains to Use the Latest Version of JRockit

If you are using the JRockit SDK, after you install an upgrade patch or run an Upgrade installer, Oracle recommends that you upgrade your domains to use the latest production version of the JRockit SDK. Although the latest version of the JRockit SDK is installed by the upgrade patch or upgrade installer, your domains are not automatically configured to use it.

To configure your domains to use the latest production version of the JRockit SDK, edit the following file:

For Windows:

MW_HOME\domain_location\domains\domain_name\bin\setDomainEnv.cmd

For UNIX:

MW_HOME/domain_location/domains/domain_name/bin/setDomainEnv.sh

Replace all occurrences of the existing JRockit version with the latest production version of the JRockit SDK.

For example, if you are upgrading from WebLogic Server 10.3.2 to WebLogic Server 10.3.3, replace

jrockit_160_14_R27.6.5-32

with

jrockit_160_20_D1.0.1-2119

You can determine the JRockit SDK version number to use for your WebLogic Server version by looking at the JRockit directory name in MW_HOME. The number to use is identical to the directory name.

7 Uninstalling the Software

This chapter describes how to uninstall or reinstall WebLogic Server, and how to revert to a previous WebLogic Server installation.

It includes the following sections:

Uninstalling the Software

Reverting to a Previous Installation

Reinstalling Your Software

Uninstalling the Software

The following sections describe how to uninstall your software or individual components on Windows and UNIX systems. You can uninstall the software using graphical, console, or silent mode.

Note:

If you used an Upgrade installer to upgrade an existing installation, you can either remove the software completely, or revert back to the previous installation as described in Reverting to a Previous Installation.

Uninstalling Your Software in Graphical Mode

Uninstalling Your Software in Console Mode

Uninstalling Your Software in Silent Mode

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

The uninstall program does not remove the home directory associated with the installation, the JDK, or any user-created WebLogic domains. Only the components that were installed by the installation program can be removed. If you choose to uninstall the entire product, 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 uninstall program was invoked from within the product directory structure—specifically, from the uninstaller directory.

Uninstalling Your Software in Graphical Mode

To run the uninstall program in graphical-mode, 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.

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

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.

Start the uninstall program as described in Table 7-1.

Table 7-1 Starting the Uninstall Program in Graphical Mode

Platform
Procedure

Windows

Choose Start > Programs > Oracle WebLogic > Uninstall Oracle WebLogic.

The Oracle Uninstaller Welcome screen is displayed.

UNIX

Go to the following directory:

MW_HOME\utils\uninstall

where MW_HOME represents the Middleware home directory in which you installed the product you are uninstalling.

Enter uninstall.sh at the prompt.

The Oracle Uninstaller Welcome screen is displayed.

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

Click Next to start the uninstall program.

The Choose Components screen is displayed.

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

Note:

To uninstall Workshop for WebLogic prior to using an Upgrade installer to upgrade a WebLogic Server 10.3.0, 10.3.1, 10.3.2 or 10.3.3 installation to WebLogic 10.3.6, select only the components shown here. Workshop components to select

After selecting the components to uninstall, click Next.

Caution:

Once you click Next, you cannot abort the uninstallation process.

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

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

Uninstalling Your Software in Console Mode

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

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

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

Table 7-2 Starting the Uninstall Program in Console Mode

Platform
Procedure

Windows

Open a command prompt window and go to the following directory:

MW_HOME\utils\uninstall

where MW_HOME represents the Middleware home directory in which you installed WebLogic Server.

Enter the following command at the prompt:

uninstall -mode=console

The Welcome text is displayed.

UNIX

Go to the following directory:

MW_HOME/utils/uninstall

where MW_HOME represents the Middleware home directory in which you installed WebLogic Server.

At the prompt, enter the following command:

sh uninstall.sh -mode=console

The Welcome text is displayed.

Enter next or press Enter 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 one-letter shortcuts, x, p, and n, respectively.

The Choose Products and Components to uninstall prompt is displayed.

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

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.

To uninstall Workshop for WebLogic prior to using an Upgrade installer to upgrade a version 10.3.1 or 10.3.2 installation to a later 10.3.x installation:

Enter 1 to deselect all WebLogic Server components.

If you also installed Coherence, enter the value for that component to deselect it.

Verify that only the Workshop for WebLogic components are selected (indicated by a check mark next to the component number).

Enter next or press Enter to proceed with the uninstallation process.

Caution:

Once you enter next, you cannot abort the uninstallation process.

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

Uninstalling Your Software in Silent Mode

When you uninstall the software in silent mode, the complete software installation is uninstalled. You cannot uninstall individual components.

Note:

If you need to uninstall Workshop for WebLogic prior to running an Upgrade installer, you must run the uninstaller in graphical mode or console mode to remove only the Workshop components.

When you run the uninstallation program in silent mode, it leaves behind the same files and directories as when you run the uninstall 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 that was created or modified after your software was installed.

You can manually delete these files.

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

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

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.

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

Table 7-3 Starting the Uninstallation Program in Silent Mode

Platform
Procedure

Windows

Open a command prompt window and go to the following directory:

MW_HOME\utils\uninstall

Here MW_HOME represents the Middleware home directory in which you installed the software.

Enter the following command at the prompt:

uninstall -mode=silent

UNIX

Go to the following directory:

MW_HOME\utils\uninstall

Here MW_HOME represents the Middleware home directory in which you installed the software.

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

Reverting to a Previous Installation

If you used an Upgrade installer to upgrade an existing installation to the most current version, you can use the uninstaller program to revert to the previous version of the software. For example, if you upgraded from WebLogic Server version 10.3.0 to version 10.3.3, you can use the uninstaller to revert back to the 10.3.0 installation.

Notes:

When reverting to a previous installation, you can run the uninstall program either in graphical mode or console mode. You cannot run it in silent mode in this situation.

You can also use the Smart Update tool to remove patches and updates. For more information, see Oracle Smart Update Installing Patches and Maintenance Packs.

Reverting to a Previous Version Using Graphical Mode

To revert to a previous installation using graphical mode:

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.

If you are rolling back to WebLogic Server 10.3.0, refer to Upgrading the Embedded LDAP Schema, for important information regarding the Embedded LDAP schema.

Start the uninstall program as described in Table 7-1.

Click Next. The Select Uninstall Type screen appears. The options on this screen differ depending on the initial installation you upgraded, and the release to which you upgraded. The following example is for an environment in which WebLogic Server 10.3.0 was installed (without Workshop for WebLogic), and the version 10.3.0 installation was upgraded to version 10.3.4.

Select the appropriate Rollback or Uninstall option. In this example:

To revert back to the WebLogic Server 10.3.0 release, select Rollback to WebLogic Platform. Click Next. The Uninstalling WebLogic Platform screen is displayed. Go to step 5.

To completely uninstall the WebLogic Server 10.3.6 release, select Uninstall WebLogic Platform version. In this case, the Component Selection screen appears next, and you can continue the uninstallation from step 4 in Uninstalling Your Software in Graphical Mode.

Wait while the uninstall program restores the previous version of your software. When the message "Uninstall Complete" appears, click Done.

Reverting to a Previous Version Using Console Mode

To revert to a previous installation using console mode:

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.

If you are rolling back to WebLogic Server 10.3.0, refer to Upgrading the Embedded LDAP Schema, for important information regarding the Embedded LDAP schema.

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

Enter next or press Enter to proceed to the next panel of the uninstallation program.

Enter the appropriate number for the Uninstall or Rollback option you want to select. The options you see depend on your initial installation and the version to which you upgraded.

If you select the Rollback to WebLogic Server 10.3.0.0 option, after a few minutes, the message Restoring Files is displayed while the uninstall program restores your previous version. Go to Step 5.

If you select an Uninstall option, you can completely remove all of the existing installation, or you can remove individual components of the currently installed version. In this case, the Choose Components to Uninstall panel is displayed. To continue, go to step 4 in Uninstalling Your Software in Console Mode.

The process is complete when the uninstall program shell closes.

Upgrading the Embedded LDAP Schema

A new operational attribute, orclguid, was added to the Embedded LDAP server as of WebLogic Server 10.3.1. Therefore, if you upgraded from WebLogic Server 10.3.0 to a later 10.3.x version, and then need to perform a rollback to the 10.3.0 installation, Oracle recommends that, after rollback, you upgrade the Embedded LDAP schema in your 10.3.0 installation to the schema version in the later installation. Otherwise, you may see the following LDAP error after rollback:

LDAPException: error result (65); Missing Attributes: [], NotAllowed Attributes: [orclguid]

To upgrade the Embedded LDAP schema:]

Prior to rolling back to the 10.3.0 installation, save a copy of the following schema file to a temporary directory:

WL_HOME\server\lib\schema.core.xml

After rolling back to the WebLogic Server 10.3.0 installation, replace the schema file in the WebLogic Server 10.3.0 installation with the schema file you saved to the temporary directory.

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 Core Application Server, Administration Console, and Configuration Wizard Upgrade Framework during one installation, and add WebLogic JDBC Drivers and Server Examples 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 OK (or enter OK, if in console mode) to return to the Choose Middleware Home Directory screen (or panel).

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:

Uninstalling Your Software in Graphical Mode

Uninstalling Your Software in Console Mode

Uninstalling Your Software in Silent Mode

Then, install the software as described in one of the following chapters:

Chapter 3, "Running the Installation Program in Graphical Mode"

Chapter 4, "Running the Installation Program in Console Mode"

Chapter 5, "Running the Installation Program in Silent Mode"

A Oracle WebLogic Server Installation Screens

This appendix contains screenshots and descriptions for all of the WebLogic Server installation screens.

Welcome

Choose Middleware Home Directory

Register for Security Updates

Choose Install Type

Choose Products and Components

JDK Selection

Choose Product Installation Directories

Confirm Product Installation Directory

Install Windows Service

Choose Shortcut Location

Installation Summary

Status

Installation Complete

Welcome

The Welcome screen is displayed each time you start the installer.

Choose Middleware Home Directory

Specify the Middleware home directory that will serve as the central support directory for all Fusion Middleware products installed on the target system, including WebLogic Server. The default Middleware home directory is C:\Oracle\Middleware. Each Fusion MIddleware product will be installed in its own product directory in the Middleware home directory.

If you already have a Middleware home directory on your system, you can select that directory (recommended) or create another Middleware 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 an existing directory from the Middleware Home Directory screen.

For more details about the Middleware home directory, see Choosing a Middleware 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 My Oracle Support email address and your My Oracle Support password.

If you want to decline registration, deselect the I wish to receive security updates via My Oracle Support check box. An Are You Sure? dialog box appears. Click Yes to continue.

Notes:

If you are using a Generic installer (JAR file) to install WebLogic Server, and $JAVA_HOME points to a JDK that is later than JDK 1.60_05, you cannot deselect the I wish to receive security updates via My Oracle Support check box. In this case, if you do not want to install security updates:

Leave the Email and Support Password fields blank, and click Next. An Email Address Not Specified dialog box appears.

Click Yes. An Are You Sure? dialog box appears.

Click Yes to continue with the installation.

If a Connection Failed dialog box appears when you bypass security updates, select the I wish to remain uninformed of security updates check box and click Continue to continue the installation.

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

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

Choose Install Type

Select the installation type.

Typical—All the software components included in your installation program are installed on your system. Typical installation does not include the Server Examples.

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. If you want to install the Server Examples, you must select Custom.

For more information, see Choosing the Type of Installation.

Choose Products and Components

Specify the components to be installed by selecting or clearing the appropriate check boxes.

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

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

Note:

When you select components, the installation program checks for dependencies between the components and automatically modifies the list of selected components to ensure that dependencies for selected components are also selected.

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

JDK Selection

This screen displays a list of JDKs. This list differs depending on the specific installer you are using. For example, .jar installers do not include SDKs. If you are upgrading from a previous version, the list contains JDKs that are available for (and common across) previous installations of all the selected WebLogic Server components.

Select the JDK or JDKs 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 screen 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.

Choose Product Installation Directories

You can accept the default product directories or specify new directories for each product you are installing. The product directories that are listed on this screen depend on the products you selected for installation. You may have to specify up to three installation directories, one each for Oracle WebLogic Server and Oracle Coherence.

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 screen to change the Middleware home directory, 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 screen, then the old installation directory is retained in the Choose Middleware Home Directory screen.

For example, the default installation directory for Oracle WebLogic Server is MW_HOME\wlserver_10.3.

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

If you specify the installation directory in the Choose Product Installation Directory screen, and if the directory you specify is outside of the existing Middleware home, the existing installation directory is retained.

For more information, see Choosing Product Installation Directories.

Confirm Product Installation Directory

If you are adding components to an existing product installation, confirm the product installation directory. These are the directories in which you previously installed WebLogic Server or Oracle Coherence.

The selected components are installed in the product installation directory you specified during the initial installation.

Install Windows Service

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

Choose Shortcut Location

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

Status

This screen shows the progress of the installation. When the progress bar reaches 100%, the installation is complete.

Installation Complete

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

If you want to run the QuickStart application, leave the Run QuickStart check box selected. QuickStart is designed to assist first-time users in evaluating, learning, and using the software. It provides quick access to the sample domains, information for upgrading your applications, and the online documentation.

Clear the Run QuickStart check box if you do not want to launch QuickStart.

B Development-Only Installation

Oracle provides a complete WebLogic Server installation in a ZIP file for development use only. This installation is supported on Windows, Linux, and Mac OS X systems.

The extracted installation contains all the necessary artifacts you need to develop applications on WebLogic Server, but uses less disk space than a WebLogic Server installation performed in Typical mode. It includes all WebLogic Server components except for the following:

Samples

Derby database

WebServer plug-ins

Native JNI libraries for unsupported platforms

Administration Console help files for non-English locales

Oracle Configuration Management (OCM) and ADR files

Sun SDK and Oracle JRockit SDK

Coherence libraries

Oracle also provides a supplemental ZIP file which contains additional files that complement the development-only installer. The supplemental ZIP file contains the following components:

Samples files (extracted to WL_HOME/samples)

Derby database and relevant scripts (extracted to WL_HOME/common/derby)

Administration Console help files for non-English locales (extracted to WL_HOME/server/lib/consoleapp/consolehelp/locale_directory, where the locale directories are:

de

es

fr

it

ja

ko

pt-br

zh-cn

zh-tw

Getting Started with the Development-only Installation

To use the development-only WebLogic Server installation:

Download the ZIP file from the Oracle Technology Network. See Downloading the Installer From Oracle Technology Network, for instructions. When on the download page, click the appropriate link on the Oracle WebLogic Server 11gR1 (10.3.6) Development-Only Installer row.

When the installer download completes, extract the file to the directory you want to use as the Middleware home directory. For example, if you want the Middleware home for this WebLogic Server installation to be C:\Oracle\MW_dev, extract the files to that directory.

Note:

Do not extract the files to an existing Middleware home that already contains a WebLogic Server installation.

Optionally download the supplemental ZIP file from the Oracle Technology Network. When on the download page, click the appropriate link on the Oracle WebLogic Server 11gR1 (10.3.6) Supplemental Installer row.

When the download completes, extract the supplemental ZIP file to the same Middleware home directory in which you extracted the development-only installer files.

Open the README.txt file in the Middleware home directory to which you extracted the files, and follow the instructions in the QUICKSTART section. The README.txt file contains the most up-to-date preparation and installation instructions.

Note:

If you choose to download and install the supplemental ZIP after you have already run the configuration script described in the README.txt file, you must run the configuration script again after you extract the supplemental ZIP files to the Middleware home directory.

The README file also contains a list of all known issues for the current version of the development-only installation, as well as other important information.

If you extracted the supplement ZIP file, open the README_SUPP.txt file in the Middleware home directory and follow the instructions in the QUICKSTART section. The README_SUPP.txt file contains the most up-to-date installation and configuration instructions for the supplemental files, as well as information about the sample domains.

Refer to the following sections for additional information:

Creating Domains

Upgrading an Existing Installation

Removing an Existing Installation

Creating Domains

Oracle recommends that you create all domains for your development environment outside of the Middleware home directory. This makes it easier for you to remove an existing development-only installation, or upgrade to a newer version, without having to recreate your domains and applications.

You can create a domain using WLST, the unpack command, or the Fusion Middleware Configuration Wizard. WebLogic Server domain and extension templates are available in the MW_HOME/wlserver/common/templates/domains and MW_HOME/wlserver/common/templates/applications directories to help you get started with domain creation. See the following documents for more information about creating domains:

Creating Domains Using the Configuration Wizard

Oracle WebLogic Scripting Tool

Creating Templates and Domains Using the Pack and Unpack Commands

Domain Template Reference

Upgrading an Existing Installation

In-place upgrade of an existing installation is not supported by this installer. To upgrade to a newer version of the development-only installer:

Download the latest version from Oracle Technology Network.

Extract the ZIP file to a new Middleware home location.

Change the MW_HOME variable to point to new Middleware home.

Update the startup scripts for your domains to point to the new Middleware home.

Removing an Existing Installation

To completely remove an existing development-only installation, delete the entire Middleware home directory in which you extracted the files. If you also installed the supplemental files, those files are also removed when you delete the Middleware home directory.

Note:

If you created any domains and applications in the Middleware home directory, and you want to keep them for future use, move the directory that contains them to another location outside of the Middleware home before you delete it.

C WebLogic Server Installers

This appendix lists all of the available WebLogic Server installers. Refer to Product Distribution, for information about the Oracle Web sites from which you can download installers.

Table C-1 Available Installers

Filename
Description

wls1036_generic.jar

For installations on any supported platform on which Java is already installed. Includes WebLogic Server and Coherence. Does not include JDKs.

wls1036_linux32.bin

For installations on Linux x86 32-bit machines. Includes WebLogic Server, Coherence, Sun SDK 1.6.0, and Oracle JRockit 1.6.0.

wls1036_linux64.bin

For installations on Linux x86 64-bit machines. Includes WebLogic Server, Coherence, and Oracle JRockit 1.6.0.

wls1036_solaris32.bin

For installations on Solaris 32-bit machines. Includes WebLogic Server, Coherence, Sun SDK 1.6.0, and Oracle JRockit 1.6.0.

wls1036_win32.exe

For installations on Windows 32-bit machines. Includes WebLogic Server, Coherence, Sun SDK 1.6.0, and Oracle JRockit 1.6.0.

wls1036_upgrade_generic.jar

Generic Upgrade installer that allows you to upgrade from a WebLogic Server version 10.3.x installation to version 10.3.6.

wls1036_upgrade_linux32.bin

Linux 32-bit Upgrade installer that allows you to upgrade from a WebLogic Server version 10.3.x installation to version 10.3.6.

wls1036_upgrade_solaris32.bin

Solaris 32-bit Upgrade installer that allows you to upgrade from a WebLogic Server version 10.3.x installation to version 10.3.6.

wls1036_upgrade_win32.exe

Windows 32-bit Upgrade installer that allows you to upgrade from a WebLogic Server version 10.3.x installation to version 10.3.6.

wls1036_dev.zip

Development-only installer that extracts a complete WebLogic Server installation which contains all of the necessary artifacts for developing applications on WebLogic Server. This installer is not for production use. It can be installed on Windows, Linux, or Mac OS X machines. See Appendix B, "Development-Only Installation," for more information.

wls1036_dev_supplemental.zip

Contains additional files that supplement the development-only installer (wls1036_dev.zip). See Appendix B, "Development-Only Installation," for more information.

D Using WebLogic Server with JDK 7

WebLogic Server does not ship with JDK 7. This appendix describes the steps you need to perform to use WebLogic Server with JDK 7. It also describes issues that you may encounter when using WebLogic Server with JDK 7.

Prior to installing JDK 7 for use with WebLogic Server, review the following issues that you may encounter when using JDK 7:

In some cases, the new JVM requires more PermGen space, which can cause PermGen errors. If this occurs, use one of the following two options to resolve the issue:

If you are using the java command to start WebLogic Server, include the following option in the command:

-XX:MaxPermSize=350m

If you are using startWebLogic.sh (UNIX) or startWebLogic.cmd (Windows) to start WebLogic Server, prior to issuing the command, set the MEM_ARGS environment variable as follows:

UNIX:

USER_MEM_ARGS="-Xms32m -Xmx200m -XX:MaxPermSize=350m"

export MEM_ARGS

Windows:

set USER_MEM_ARGS=-Xms32m -Xmx200m -XX:MaxPermSize=350m

In some cases, the new compiler generates larger byte code. It is possible that a large method may exceed the 64KB limit per method. In this situation, you may need to refactor the method.

Classes may have been removed that are from the internal package sun.*, or that have been marked as deprecated in a previous version of the JVM. If an application uses these removed methods, a ClassNotFound exception will occur.

JDBC 4.1 methods are not currently supported in WebLogic Server with JDK 7. Calls to these methods will result in an SQLException indicating that the method is not supported.

Before installing WebLogic Server, perform the following steps:

Download the appropriate JDK 7 for your platform from the following URL:

http://www.oracle.com/technetwork/java/javase/downloads/java-se-jdk-7-download-432154.html

Install the JDK.

Set JAVA_HOME to point to the installed JDK 7.

Set PATH to point to $JAVA_HOME/bin.

When installing WebLogic Server: select a Custom installation. For the JDK selection, deselect the bundled JDK entries and under the Local JDK section browse and select the JAVA_HOME directory.

On the Choose Install Type screen, select the Custom option.

On the JDK Selection screen, deselect the bundled JDK entries, and then under the Local JDK section, browse to and select the JAVA_HOME directory.

After installing WebLogic Server, copy the following files from WL_HOME/modules to JAVA_HOME/jre/lib/endorsed, where WL_HOME is the WebLogic Server installation home directory:

javax.annotation_1.0.0.0_1-0.jar

javax.xml.bind_2.1.1.jar

javax.xml.ws_2.1.1.jar

Welcome screen. This screen is described in the surrounding text.

Choose Install Type screen. This screen is described in the surrounding text.

Choose Middleware Home Directory screen. This screen is described in the surrounding text.

Register for Security Updates screen. This screen is described in the surrounding text.

This image shows the Select Uninstall Type screen. There are two uninstall options: Uninstall WebLogic Platform and Rollback to WebLogic Platform. The Rollback to WebLogic Platform option is selected.

Installation Complete screen. This screen is described in the surrounding text.

Install Windows Service screen. This screen is described in the surrounding text.

This graphic shows the basic structure of the Middleware home directory and subdirectories. Middleware Home is the top-level directory. The second level contains the WebLogic Server home, user_projects, Coherence home (if installed), and Enterprise Pack for Eclipse home (if installed). The third level shows the applications and domain directories that are located under user_projects.

Installation Summary screen. This screen is described in the surrounding text.

This graphic shows the main Workshop component selected, with the two subcomponents (Workshop for WebLogic and Workshop Runtime Framework) also selected.

Choose Products and Components screen. This screen is described in the surrounding text.

Confirm Product Installation Directories screen. This screen is described in the surrounding text.

Choose Shortcut Location screen. This screen is described in the surrounding text.

Status screen. This screen is described in the surrounding text.

Choose Product Installation Directories screen. This screen is described in the surrounding text.

JDK Selection screen. This screen is described in the surrounding text.

Oracle Legal Notices

Copyright Notice

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

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

Hazardous Applications Notice

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.

Trademark Notice

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

Third-Party Content, Products, and Services Disclaimer

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.