Preparing to Install WebLogic Server

Preparing to Install WebLogic Server

The BEA WebLogic Server Installation Program
WebLogic Server Distribution Methods
BEA WebLogic JRockit 8.1
Installation Prerequisites
Choosing the Type of Installation
Selecting Directories for the WebLogic Server Installation
Installing the Node Manager as a Windows Service
Generating a Verbose Installation Log
Where to Find Migration Information
Smart Update

The BEA WebLogic Server Installation Program

BEA WebLogic Server is distributed and installed using the BEA Installation and Distribution System, which provides a complete framework for the following:
Simplified distribution of BEA products via download from the BEA Web site.
Installation and uninstallation of the entire WebLogic Server product, or individual components as desired.
Simplified mechanism for obtaining and installing product upgrades using Smart Update.

WebLogic Express Support

You can also use the WebLogic Server installation program to install BEA WebLogic Express, a "lite" version of WebLogic Server.
WebLogic Express customers can upgrade to BEA WebLogic Platform.
To install WebLogic Express, you install WebLogic Server and then install a WebLogic Express license.

Installation Methods

The BEA installation program supports the following methods for installing the BEA WebLogic Server software:

Graphical mode
Interactive, GUI-based method for installing WebLogic Server that can be run on both Windows and UNIX systems.
To run graphical-mode installation, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX systems do. If you attempt to start the installation program in graphical mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation.
Console mode
Interactive, text-based method for installing WebLogic Server from the command line on both Windows and UNIX systems.
Silent mode
Non-interactive method of installing WebLogic Server that uses an XML properties file for selecting installation options. You can run silent-mode installation as part of a script or from the command line.

WebLogic Server Distribution Methods

WebLogic Server is distributed on both the BEA Web site and on CD-ROM.

Web Distribution of WebLogic Server

You can download the WebLogic Server software from the BEA Web site at...
http://commerce.bea.com

Two methods are available for download:

Package installer
Downloads a standalone version of the installation program that contains all of the WebLogic Server software components: Weblogic Server and related samples, WebLogic Workshop and related samples, and WebLogic JRockit (Windows and Linux platforms only). The package installer is approximately 260 MB.
Note: If you are planning to install the software using silent-mode installation, download the package installer. Silent-mode installation is not supported with the net installer.
Net installer
Downloads a small setup file (approximately 22 MB) to install all or part of BEA WebLogic Platform, which includes WebLogic Server, Weblogic Workshop, and WebLogic JRockit, as well as BEA WebLogic Integration and BEA WebLogic Portal. You can select the components that you want to install. The installer then downloads only the components you select.
Before the download begins, the net installer program prompts you to provide the following information:
A storage directory - The installation program downloads an archive file to your system for each component that you choose to install. You need to specify a directory to which you want to download these archive files.
HTTP Proxy - if you want to download these archive files using an HTTP proxy, specify the Host address and port numbers for the proxy server.

The net installer supports standard resume-processing in case of interrupted downloads. If the download is interrupted for any reason, either manually or an unplanned network interruption, you can resume the download from the point at which it was interrupted by restarting the installation process and selecting the same options. The installer checks to see what was already downloaded and downloads the remaining software that you need, including partial WebLogic Server components. When the download is complete, the installation program performs an integrity check on the archive files that were downloaded to your system to verify that the files downloaded correctly.

CD-ROM Distribution of WebLogic Server

If you purchased WebLogic Server from your local sales representative, you will find the following items in the WebLogic Server product box:
Four CD-ROMs:
Disk 1 of 4 contains the BEA WebLogic Server product software for Windows (includes WebLogic JRockit and WebLogic Workshop 8.1) and Solaris.
Disk 2 of 4 contains the BEA WebLogic Server product software for Red Hat Linux Advanced Server 2.1, 32-bit (includes WebLogic JRockit) and 64-bit.
Disk 3 of 4 contains the BEA WebLogic Server product software for HP-UX.
Disk 4 of 4 contains BEA WebLogic Server Online Documentation.
The following printed documents:
Installation Guide (this document)
Introduction to BEA WebLogic Server
BEA WebLogic Server Release Notes
BEA Software License and Limited Warranty pamphlet
Customer Support Quick Reference and Other Important Information card

Web Distribution of Service Packs and Rolling Patches

Service Packs and rolling patches, if any, are included in the latest distributions of WebLogic Server, which are available as described in WebLogic Server Distribution Methods. If you have not already installed WebLogic Server, you should install the latest distribution.
If you already have WebLogic Server installed and if you have a BEA eSupport account, you can upgrade your software in one of the following ways:

Use the Smart Update feature (recommended) to retrieve and install software updates from the BEA Web site. Smart Update downloads only the updates for the components currently installed in the target BEA Home directory.
Download the package upgrade installer from the BEA Customer Support Web site.

If you do not have a BEA eSupport account, you can register for one at on the BEA Customer Support Web site

BEA WebLogic JRockit 8.1

The BEA WebLogic JRockit 8.1 SDK provides tools, utilities, and a complete runtime environment for developing and running applications using the Java programming language.
The WebLogic JRockit SDK includes the WebLogic JRockit JVM, the first commercial server-side JVM for Intel architectures. WebLogic JRockit is supported by all WebLogic Platform components and is now fully integrated into the WebLogic Platform and WebLogic Server packages. In addition to being available as a standalone SDK. WebLogic JRockit is installed automatically when you install WebLogic Server and WebLogic Platform.
When you install WebLogic Server on Windows and Linux platforms, two Java 2 SDKs are installed on your system: the WebLogic JRockit SDK, optimized for server-side applications, and the Sun Java 2 SDK (including the Hotspot Client and Hotspot Server JVMs), provided for optional use by client- and server-side applications. When you create a configuration using the Configuration Wizard, you can select which SDK you want to use to run WebLogic Server instances and your applications.
WebLogic JRockit 8.1 is certified by Sun Microsystems, Inc. to be compatible with J2SE V1.4.1.

Installation Prerequisites

Review these requirements before installing WebLogic Server:

System Requirements
Temporary Storage Space Requirements
Administrator Privileges
Licensing and Encryption

System Requirements

Table 1-1 lists the system requirements for WebLogic Server.

Component

Requirement
Certified server platform A certified WebLogic Server platform.
Items to check include recommended Java run-time environment versions and, when appropriate, other prerequisites or recommendations, such as operating system patches, kernel configuration values, and performance packs.
Hard disk space For a WebLogic Server installation on a Windows system (including WebLogic Workshop) - about 445 MB^* free storage space for the installed product and about 275 MB of temporary storage space required by the installer (for either the net installer or the package installer).For a WebLogic Server installation on a UNIX system (which does not include WebLogic Workshop) - about 248 MB^** free storage space for the installed product and about 200 MB of temporary storage space required by the installer.
Memory WebLogic Server (with the Sun Java SDK) - 256 MB of RAM minimum, 512 MB or more recommended (without WebLogic Workshop)Weblogic Server (with the WebLogic JRockit SDK) - 512 MB of RAM minimumWebLogic Workshop - 512 MB RAM, 1 GB recommended
Color bit depth display For graphical-mode installation, 8-bit color depth (256 colors). For console-mode and silent-mode installation, there is no color bit depth requirement.
Java 2 SDK The WebLogic Server installation program requires a Java run-time environment (JRE) to run. A JRE is bundled in the Windows installation program and in some UNIX installation programs (those with filenames ending in .bin). For Windows and Linux, both the BEA WebLogic JRockit SDK and the Sun Java 2 SDK are installed on your system. You can specify the SDK to use with your domains when you create the domains with the Configuration Wizard. For other UNIX platforms, the WebLogic Server installation program does not include a JRE in the installation program. Filenames for these installation programs end in .jar. To run the .jar installation programs, have an appropriate version of a Java 2 SDK installed on your system, and include the bin directory of the SDK at the front of the PATH system variable.
Note: It is important that you use an SDK because the installation process sets the JAVA_HOME and related variables to point to this directory. All scripts installed with WebLogic Server will use this SDK by default, including scripts to start sample applications, the Configuration Wizard, and other WebLogic development tools.
Starting Graphical-Mode Installation for .jar Installation Files

Starting Console-Mode Installation for .jar Installation Files

* Includes 92 MB for the Sun and Weblogic JRockit Java 2 SDKs and 72 MB for examples and samples.
** Includes 59 MB for the Sun Java 2 SDK and 33 MB for examples and samples.

Temporary Storage Space Requirements

The BEA installation program uses a temporary directory in which it extracts the files necessary to install WebLogic Server on the target system. During the installation process, your temporary directory must contain sufficient space to accommodate the compressed Java run-time environment (JRE) bundled with the installation program and an uncompressed copy of the JRE that is expanded into the temporary directory. The extracted files are deleted from the temporary directory at the end of the installation process. As a general rule, installation programs require approximately 2.5 times the amount of temporary space that is ultimately required by the installed files.
By default, the installation program uses the following temporary directories:
Windows platforms - Directory referenced by the TMP system variable
UNIX platforms - System-dependent temporary directory

Note: If there is not enough temporary space to run the installation program, you are prompted to specify an alternate directory or exit the installation program.
To ensure there is adequate temporary space, you may want to allocate an alternate directory for use as a temporary directory for the installation. To do so, follow the instructions provided in Table 1-2.

On this platform . . .

Perform this step . . .
Windows Do one of the following:
Set the TMP system variable to a directory of your choice.

If starting the installation program from the command line, enter the option...
-Djava.io.tmpdir=tmpdirpath

UNIX Enter the following option on the command line when you start the installation program:
-Djava.io.tmpdir=tmpdirpath

Administrator Privileges

During a custom installation on a Windows system, you can install the WebLogic Server Node Manager as a Windows service. If you choose to run the Configuration Wizard to create a WebLogic configuration, you can also configure the server instance as a Windows service. When the Node Manager or a server instance is installed as a Windows service, it starts automatically each time you boot your Windows system. You must have Administrator privileges to install the Node Manager or a server instance as a Windows service.

Licensing and Encryption

The WebLogic Server software cannot be used without a valid license. When you install WebLogic Server, the installation program creates a non-expiring development license so that you can start using the product immediately. To use WebLogic Server in a production environment, purchase a production license. For information about purchasing a production license,contact your sales representative or see the BEA corporate Web site. For more information about WebLogic Server licenses, see About WebLogic Server Licenses
Development and production licenses for pre-8.1 versions of WebLogic Server will not work with WebLogic Server 8.1. You must upgrade your license to an 8.1 license. Procedures for upgrading a license file and installing permanent licenses are provided in Installing and Updating a WebLogic Server License.

About 128-Bit Encryption

Secure sockets layer (SSL) encryption software is available with two levels of encryption: 56-bit and 128-bit. Licenses for the 128-bit client version of SSL are available in the United States and Canada. With proper authorization, customers outside the United States and Canada may also acquire licenses with 128-bit encryption enabled.
A WebLogic Server license comes with 56-bit encryption enabled by default. If you want to enable 128-bit encryption for SSL, make sure that a 128-bit encryption license is included in the license.bea file of the target BEA Home directory before you install the WebLogic Server software.
For instructions about how to install the 128-bit encryption license, see Enabling 128-Bit Encryption.

Choosing the Type of Installation

The WebLogic Server installation program provides two types of installation: Complete and Custom.

Complete Installation

In a complete installation, the following components are automatically installed:
All software components included in the distribution. Software components vary depending on the software distribution method:

CD-ROM or WebLogic Server Package Installer - WebLogic Server and WebLogic Workshop (Windows only) program files and all related sample files.
Net Installer - All WebLogic Platform components, including WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogic Portal, and all related sample files. For more information about installing WebLogic Platform components, see the WebLogic Platform Installation Guide.

Two SDKs: The BEA WebLogic JRockit 8.1 SDK and the Sun Java 2 1.4.1 SDK (Windows and Linux only).

The WebLogic Server Node Manager is not installed as a Windows service.

Custom Installation

With the custom installation option, you can choose exactly which software components you want to install on your system:
WebLogic Server
WebLogic Workshop

On Windows and Linux systems, two SDKs are installed: The BEA WebLogic JRockit 8.1 SDK and the Sun Java 2 1.4.1 SDK.
You can also optionally install the WebLogic Server Node Manager as Windows service (Windows platforms only).

WebLogic Server

The WebLogic Server program files include the core Java 2, Enterprise Edition (J2EE) features, providing services to ensure a reliable, available, scalable, and high performing execution environment. WebLogic Server consists of the following components:
Server - WebLogic Server program files which contain the core Java 2 Enterprise Edition (J2EE) features.
Server Examples - WebLogic Server examples and the MedRec example servers and sample applications. These servers and sample applications demonstrate a variety of J2EE features. Resources are provided to help you build, configure, and run each of the sample applications. You must install the server to install and use the WebLogic Server samples.

WebLogic Workshop

WebLogic Workshop is a unified, visual development environment and run-time framework that lets application developers - not just J2EE experts - rapidly create, test, and deploy enterprise-class Web applications, Web services, and custom controls for WebLogic Server, WebLogic Integration, and WebLogic Portal.
If you select the entire WebLogic Workshop component, the installation program installs the runtime framework, the visual development environment, and the Workshop samples.
WebLogic Workshop consists of the following components:
Workshop Runtime Framework - an abstraction layer on top of J2EE to help all developers build web applications, web services, and custom controls.
WebLogic Workshop Application Developer Edition - a design-time visual development environment where developers build applications by adding methods and controls, setting properties, and writing business logic with Java.
Workshop Samples - samples that demonstrate how to build applications with WebLogic Workshop.

Selecting Directories for the WebLogic Server Installation

During installation of WebLogic Server, you need to specify locations for the following directories:
BEA Home Directory
Product Installation Directory

BEA Home Directory

When you install WebLogic Server, you are prompted to specify a BEA Home directory. The BEA Home directory is a repository for common files that are used by multiple BEA products installed on the same machine. For this reason, the BEA Home directory can be considered a "central support directory" for the BEA products installed on your system.
The files in the BEA Home directory are essential to ensuring that BEA software operates correctly on your system. They perform the following types of functions:
Ensure that licensing works correctly for the installed BEA products
Facilitate checking of cross-product dependencies during installation
Facilitate Service Pack installation

The structure of a sample BEA Home directory created by the WebLogic Server installer program that includes a bundled SDK is shown in the following illustration.

This illustration depicts only the files and directories required in the BEA Home directory. If you choose the default product installation directory, you will see additional directories in the BEA Home directory, such as weblogic81 (the WebLogic Server installation directory) and user_projects (a folder for WebLogic domains that you create). Although the default location for the WebLogic Server installation directory is within the BEA Home directory, you can select a different location outside the BEA Home directory.
Note: For some UNIX platforms, the WebLogic Server installation program does not install an SDK.
During installation of WebLogic Server, you are prompted to choose an existing BEA Home directory or specify a path to create a new BEA Home directory. If you choose to create a new directory, the WebLogic Server installation program automatically creates the directory for you.
Note: For a BEA Home directory, you are allowed to install each version of a BEA product that uses the BEA Home directory convention only once. For example, you can install WebLogic Server 8.1 and associate it with a BEA Home directory, and that BEA Home directory can also be associated with an installation of WebLogic Server 7.0. It cannot be associated with another installation of WebLogic Server 8.1.

Understanding the Functions of the BEA Home Directory

The files and directories in the BEA Home directory are described in Table 1-3.

Component

Description
ext_components directory Contains controls for third-party components.
Java controls are server-side components that encapsulate external resources and business logic for use in Workshop applications. They are integrated with the Workshop IDE and are managed by the Workshop run-time framework. For more information about this directory, see "Local Components Directory" in "Creating and Packaging WebLogic Workshop Controls" in the WebLogic Platform Partner's Guide.
jdk141_XX directory Software for the Sun Java 2 SDK 1.4.1 installed with WebLogic Server.
The SDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. When you create a configuration with the Configuration Wizard, you can choose which SDK to use to run WebLogic Server and your applications.
Note: For some UNIX platforms, the WebLogic Platform installation program does not include an SDK.
jrockit81spX_141_XX directory Software for the Weblogic JRockit Java 2 SDK 1.4.1 installed with WebLogic Server.
Weblogic JRockit is installed on Windows and Linux platforms only. The SDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. When you create a configuration with the Configuration Wizard, you can choose which SDK to use to run WebLogic Server and your applications.
logs directory History file of installation and uninstallation for the BEA Home directory.
utils directory Utilities that support the installation of all BEA WebLogic Platform products.
The utils.jar file contains code that supports the UpdateLicense utility.
license.bea file XML-format license file that contains the license keys for all BEA WebLogic Platform products installed on your system that use the BEA Home directory convention.
Licenses are release-specific. You cannot use a license from a previous release with WebLogic Server 8.1.
To convert a pre-8.1 license.bea file to a WebLogic Server 8.1 license.bea file, refer to Upgrading Licenses from Previous WebLogic Server Releases for information.
To add a production license or to update a license file for additional functionality, update the license.bea file using the UpdateLicense utility.
Note: Do not edit this file manually. Doing so may cause operating problems for the currently installed BEA products, or result in installation problems when installing future BEA products or maintenance upgrades.
registry.xml file A registry file that contains a persistent record of all BEA products installed on the target system. This registry contains product-related information, such as version number, Service Pack number, and installation directory.
Note: Do not edit this file manually. Doing so may cause operating problems for the currently installed BEA products, or result in installation problems when installing future BEA products or maintenance upgrades.
UpdateLicense.sh A command file (Windows) or a shell script (UNIX) that updates the current license.bea file with new license sections. The result is a merged license that contains both the existing and new license sections.

Creating Multiple BEA Home Directories

Although it is possible to create more than one BEA Home directory, BEA recommends that you avoid doing so. In almost all situations, a single BEA Home directory is sufficient. There may be circumstances, however, in which you prefer to maintain separate development and production environments on a single machine, each containing a separate product stack. With two directories, you can update your development environment (in a BEA Home directory) without modifying the production environment until you are ready to do so.

Product Installation Directory

The product installation directory contains all the software components that you choose to install on your system, including program files and examples. During installation, you are prompted to choose a product installation directory. If you accept the default, the WebLogic Server software is installed in the following directory:
c:\bea\weblogic81
where c:\bea is the BEA Home directory and weblogic81 is the product installation directory. However, you can specify any name and location on your system for your product installation directory; there is no requirement that you name the directory weblogic81, or create it under the BEA Home directory.
The installer uses the product installation directory as the WL_HOME directory and installs the software components under this directory.

Installing the Node Manager as a Windows Service

When installing WebLogic Server on a Windows platform, you can optionally install the WebLogic Server Node Manager as a Windows service when you select the custom installation option
Use the Node Manager to start and stop Managed Servers in a domain; monitor the self-reported health of Managed Servers ; and automatically restart Managed Servers that have the "failed" health state, or have shut down unexpectedly due to a system crash or reboot.
In a production environment, you usually install the Node Manager only on server machines that host Managed Server instances of WebLogic Server.
The Node Manager is installed as a Windows service only under the following conditions:
You are installing on a Windows platform.
The Node Manager for the current version of WebLogic Server is not already installed on the server.

After you install the Node Manager as a Windows service, the service is started after the next time you reboot the system. You can also manually start the service from the Windows Services control panel.
When you uninstall WebLogic Server, the service is uninstalled, too.
Note that by default, the WebLogic Server Node Manager uses port 5555. If the Node Manager for a previous release of WebLogic Server is installed on the machine, the new version will not start when Windows starts because of port contention. You can reconfigure the Node Manager to use a different port.
The "Node Manager service is linked to a BEA Home directory. If you have multiple BEA Home directories on your server and you uninstall WebLogic Server in the BEA Home linked to the Node Manager service, the uninstaller will uninstall the service. If you have other instances of WebLogic Server that rely on the Node Manager, manually start the Node Manger or reinstall the Node Manager service.

Generating a Verbose Installation Log

If you start the installation process from the command line or from a script, you can specify the -log option to generate a verbose installation log. The installation log lists messages about events during the installation process, including informational, warning, error, and fatal messages. This can be especially useful for silent installations.
You may see some warning messages during in the installation log. However, unless there is a fatal error, the installation program will complete the installation successfully. The installation user interface will indicate the success or failure of the installation, and the installation log file will include an entry indicating that the installation was successful.

Syntax

To create a verbose log file during installation, include the option...
-log=/full_path_to_log_file

...in the command line or script. For example:
serverXXX_win32.exe -log=D:\logs\wls_install.log

where XXX is the version of the software you are installing.
The path must be the full path to a file name. If the file does not exist, all folders in the path must exist before you execute the command or the installation program will not create the log file.

Where to Find Migration Information

For information about migrating from a previous release of WebLogic Server to WebLogic Server 8.1, see the Upgrade Guide for BEA WebLogic Server .

Smart Update

The Smart Update feature enables you to quickly and easily upgrade your WebLogic Server software with service packs and software patches (referred to as rolling patches).
When you start Smart Update, either from the Windows Start menu or from the command line, it checks the version of products installed (associated with the current BEA Home directory), and then connects to the BEA Web site to check for available updates.
For details about using Smart Update, see Installing WebLogic Server Service Packs and Rolling Patches.

Component	Requirement
Certified server platform	A certified WebLogic Server platform. Items to check include recommended Java run-time environment versions and, when appropriate, other prerequisites or recommendations, such as operating system patches, kernel configuration values, and performance packs.
Hard disk space	For a WebLogic Server installation on a Windows system (including WebLogic Workshop) - about 445 MB^* free storage space for the installed product and about 275 MB of temporary storage space required by the installer (for either the net installer or the package installer).For a WebLogic Server installation on a UNIX system (which does not include WebLogic Workshop) - about 248 MB^** free storage space for the installed product and about 200 MB of temporary storage space required by the installer.
Memory	WebLogic Server (with the Sun Java SDK) - 256 MB of RAM minimum, 512 MB or more recommended (without WebLogic Workshop)Weblogic Server (with the WebLogic JRockit SDK) - 512 MB of RAM minimumWebLogic Workshop - 512 MB RAM, 1 GB recommended
Color bit depth display	For graphical-mode installation, 8-bit color depth (256 colors). For console-mode and silent-mode installation, there is no color bit depth requirement.
Java 2 SDK	The WebLogic Server installation program requires a Java run-time environment (JRE) to run. A JRE is bundled in the Windows installation program and in some UNIX installation programs (those with filenames ending in .bin). For Windows and Linux, both the BEA WebLogic JRockit SDK and the Sun Java 2 SDK are installed on your system. You can specify the SDK to use with your domains when you create the domains with the Configuration Wizard. For other UNIX platforms, the WebLogic Server installation program does not include a JRE in the installation program. Filenames for these installation programs end in .jar. To run the .jar installation programs, have an appropriate version of a Java 2 SDK installed on your system, and include the bin directory of the SDK at the front of the PATH system variable. Note: It is important that you use an SDK because the installation process sets the JAVA_HOME and related variables to point to this directory. All scripts installed with WebLogic Server will use this SDK by default, including scripts to start sample applications, the Configuration Wizard, and other WebLogic development tools. Starting Graphical-Mode Installation for .jar Installation Files Starting Console-Mode Installation for .jar Installation Files
* Includes 92 MB for the Sun and Weblogic JRockit Java 2 SDKs and 72 MB for examples and samples. ** Includes 59 MB for the Sun Java 2 SDK and 33 MB for examples and samples.

Component	Description
ext_components directory	Contains controls for third-party components. Java controls are server-side components that encapsulate external resources and business logic for use in Workshop applications. They are integrated with the Workshop IDE and are managed by the Workshop run-time framework. For more information about this directory, see "Local Components Directory" in "Creating and Packaging WebLogic Workshop Controls" in the WebLogic Platform Partner's Guide.
jdk141_XX directory	Software for the Sun Java 2 SDK 1.4.1 installed with WebLogic Server. The SDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. When you create a configuration with the Configuration Wizard, you can choose which SDK to use to run WebLogic Server and your applications. Note: For some UNIX platforms, the WebLogic Platform installation program does not include an SDK.
jrockit81spX_141_XX directory	Software for the Weblogic JRockit Java 2 SDK 1.4.1 installed with WebLogic Server. Weblogic JRockit is installed on Windows and Linux platforms only. The SDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. When you create a configuration with the Configuration Wizard, you can choose which SDK to use to run WebLogic Server and your applications.
logs directory	History file of installation and uninstallation for the BEA Home directory.
utils directory	Utilities that support the installation of all BEA WebLogic Platform products. The utils.jar file contains code that supports the UpdateLicense utility.
license.bea file	XML-format license file that contains the license keys for all BEA WebLogic Platform products installed on your system that use the BEA Home directory convention. Licenses are release-specific. You cannot use a license from a previous release with WebLogic Server 8.1. To convert a pre-8.1 license.bea file to a WebLogic Server 8.1 license.bea file, refer to Upgrading Licenses from Previous WebLogic Server Releases for information. To add a production license or to update a license file for additional functionality, update the license.bea file using the UpdateLicense utility. Note: Do not edit this file manually. Doing so may cause operating problems for the currently installed BEA products, or result in installation problems when installing future BEA products or maintenance upgrades.
registry.xml file	A registry file that contains a persistent record of all BEA products installed on the target system. This registry contains product-related information, such as version number, Service Pack number, and installation directory. Note: Do not edit this file manually. Doing so may cause operating problems for the currently installed BEA products, or result in installation problems when installing future BEA products or maintenance upgrades.
UpdateLicense.sh	A command file (Windows) or a shell script (UNIX) that updates the current license.bea file with new license sections. The result is a merged license that contains both the existing and new license sections.