Install
Install
Server and ™
WebLogic
Express ™
Installation Guide
Index
This document explains how to install BEA WebLogic Server™ on both Windows and UNIX systems.
This document is organized as follows:
! Chapter 1, “Preparing to Install WebLogic Server,” provides the basic information you need to
know before installing WebLogic Server.
! Chapter 4, “Installing WebLogic Server Using Silent-Mode Installation,” describes how to install
WebLogic Server without user intervention by using a template file during the installation
process.
! Chapter 5, “Installing and Updating a WebLogic Server License,” explains how to install and
update your WebLogic Server license file.
! Chapter 6, “Installing WebLogic Server Service Packs and Rolling Patches,” describes how to
launch Smart Update and check for available service packs.
Related Information
The BEA corporate Web site provides all documentation for WebLogic Server. Other WebLogic Server
documents that you may find helpful when installing the WebLogic Server software are:
! Administration Guide at
[Link]
Contact Us!
Your feedback on BEA documentation is important to us. Send us e-mail at docsupport@[Link]
if you have questions or comments. Your comments will be reviewed directly by the BEA professionals
who create and update the documentation.
In your e-mail message, please indicate the software name and version you are using, as well as the
title and document date of your documentation. If you have any questions about this version of BEA
WebLogic Server, or if you have problems installing and running BEA WebLogic Server, contact BEA
Customer Support through the BEA Customer Support Web site at [Link] You
can also contact Customer Support by using the contact information provided on the Customer
Support Card, which is included in the product package.
When contacting Customer Support, be prepared to provide the following information:
Documentation Conventions
The following documentation conventions are used throughout this document.
Convention Usage
Convention Usage
monospace Code samples, commands and their options, Java classes, data types,
text directories, and filenames and their extensions. Monospace text also indicates
text that you enter from the keyboard.
Examples:
import [Link];
chmod u+w *
config/examples/applications
.java
[Link]
float
Convention Usage
... Indicates one of the following in a command line:
• An argument can be repeated several times in the command line.
• The statement omits additional optional arguments.
• You can enter additional parameters, values, or other information
. Indicates the omission of items from a code example or from a syntax line.
.
.
BEA WebLogic Server™ implements J2EE 1.3 technologies, Web services, and other leading Internet
standards to provide a reliable framework for highly available, scalable, and secure applications.
WebLogic Server includes BEA WebLogic Workshop™, which is a graphical development environment
in which you can easily build Web services that automatically leverage the power, reliability, and
scalability of WebLogic Server.
With the release of WebLogic Server 7.0 Service Pack 2, the BEA WebLogic JRockit™ SDK is bundled
with WebLogic Server for Windows and Linux platforms. The WebLogic JRockit SDK was developed
and optimized for server-side applications and supports Intel architectures.
WebLogic Server and WebLogic Workshop are also available as part of the BEA WebLogic Platform™.
For more information about Weblogic Platform, see the Weblogic Platform online documentation at
[Link]
The following sections provide information that you need to know before installing WebLogic Server:
Audience
This document is written for system administrators or application developers who are installing the
latest version of WebLogic Server software. It is assumed that readers know Web technologies and
have a general understanding of Windows and UNIX systems.
WebLogic Server is available as a separate product (including WebLogic Workshop) and as a
component in WebLogic Platform. Use this document if you are installing WebLogic Server as a
separate product or if you are installing only the Weblogic Server component (including WebLogic
Server with WebLogic Workshop and related samples) of Weblogic Platform. This document does not
discuss installation of the entire WebLogic Platform. If you are installing WebLogic Server with
additional WebLogic Platform components, refer to the WebLogic Platform Installation Guide at
[Link]
If you are upgrading to WebLogic Server 7.0 from WebLogic Server 6.1 or earlier, see the WebLogic
Server 7.0 Upgrade Guide at [Link]
! 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.
! Ability to create WebLogic domains using a Configuration Wizard that can be invoked at the end
of the installation process. For full details on the Configuration Wizard, see Creating New
Domains Using the Configuration Wizard in Creating and Configuring WebLogic Server
Domains at [Link]
Detailed descriptions of the domain templates provided with the WebLogic Platform installation
program are provided in the Configuration Wizard Template Reference at
[Link]
Installation Methods
The BEA installation program supports the following methods for installing the BEA WebLogic Server
software:
! Graphical mode
Graphical-mode installation is an interactive, GUI-based method for installing WebLogic Server.
It can be run on both Windows and UNIX systems. See Chapter 2, “Installing WebLogic Server
Using Graphical-Mode Installation.”
Note: 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
Console-mode installation is an interactive, text-based method for installing WebLogic Server
from the command line on both Windows and UNIX systems. See Chapter 3, “Installing
WebLogic Server Using Console-Mode Installation.”
! Silent mode
Silent-mode installation is a 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. See Chapter 4, “Installing WebLogic Server Using
Silent-Mode Installation.”
! Package installer—downloads a standalone version of the installation program that contains all
of the WebLogic Server software components: server (which includes WebLogic Workshop) and
server samples (approximately 150 MB).
Note: You must use the package installer option if you are planning to install the software using
silent-mode installation. Silent-mode installation is not supported with the net installer
option.
! Net installer—downloads a setup file (approximately 18MB) to install the complete BEA
WebLogic Platform™, which includes WebLogic Server and Weblogic Workshop, as well as BEA
WebLogic Integration™, and BEA WebLogic Portal™. You can choose to install only WebLogic
Server with WebLogic Workshop, as described in “Custom Installation” on page 1-12.
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, you must
specify the Host address and port numbers for the proxy server.
The net installer supports standard resume-processing in the 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. 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.
! Five CD-ROMs:
– Disk 1 of 4 contains the BEA WebLogic Server 7.0 SP2 product software for Windows,
Solaris, and Linux with the Sun Java 2 SDK
– Disk 2 of 4 contains the BEA WebLogic Server 7.0 SP2 product software for Windows and
Linux with the JRockit Java 2 SDK
– Disk 3 of 4 contains the BEA WebLogic Server 7.0 SP1 product software for HP-UX and AIX
– Disk 4 of 4 contains BEA WebLogic Server 7.0 Online Documentation
! 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.
Note: Smart Update upgrades your Windows installation to use the Sun Java 2 SDK and your
Linux installation to use the WebLogic JRockit SDK. If you want to use a different SDK,
you should use a WebLogic Platform upgrade installer that is bundled with the
appropriate SDK or change the SDK, as described in “Switching JVMs in WebLogic
Platform” in the WebLogic Platform Release Notes, at the following URL:
[Link]
undledJVM
! Download the package upgrade installer from the BEA Customer Support Web site at
[Link]
Details about installing WebLogic Server service packs and rolling patches are provided in Chapter 6,
“Installing WebLogic Server Service Packs and Rolling Patches.”
If you do not have a BEA eSupport account, you can register for one at on the BEA Customer Support
Web site at [Link]
If you install WebLogic Server 7.0 with the Sun Java 2 SDK and you want to change your installation
to use the WebLogic JRockit 7.0 SDK, see “Switching JVMs in WebLogic Platform” in the BEA
WebLogic Platform Release Notes for instructions.
For more information about WebLogic JRockit, see the JRockit documentation at
[Link]
Note: The installation instructions provided in BEA WebLogic JRockit™ 7.0 for Windows and
Linux Installation and Migration Guide describe how to install JRockit as a standalone SDK
and do not apply to the WebLogic Server/JRockit bundles.
Installation Prerequisites
Review these requirements before installing WebLogic Server:
System Requirements
Table 1-1 lists the system requirements for WebLogic Server.
Certified server A certified WebLogic Server platform. See the Supported Configurations page at
platform [Link]
This page includes the recommended Java run-time environment versions and, when
appropriate, other prerequisites or recommendations, such as operating system
patches, kernel configuration values, and performance packs.
For more information about performance packs, see “Using WebLogic Server
Performance Packs” in the Performance and Tuning Guide at
[Link]
#wlstuning-PerformPacks.
Hard disk drive For a WebLogic Server 7.0 installation on a Windows system—about 236 MB* free
storage space for the installed product and
about 170 MB of temporary storage space required by the installer (for either the net
installer or the package installer).
For a WebLogic Server 7.0 installation on a UNIX system—
about 196 MB** free storage space for the installed product and
about 162 MB of temporary storage space required by the installer.
Memory For a Windows or UNIX system, 256 MB of RAM minimum; 512 MB or more is
recommended.
Color bit depth For graphical-mode installation, 8-bit color depth (256 colors).
display
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 Java 2 Software Development Kit (SDK), which includes a JRE, is
bundled in the Windows installation program and in some UNIX installation programs
(those with filenames ending in .bin). For other UNIX platforms, the WebLogic
Server installation program does not include the Java 2 SDK in the installation
program. Filenames for these installation programs end in .jar. To run the .jar
installation programs, you must have the appropriate version of the Java 2 SDK
installed on your system, and include the bin directory of the SDK at the front of the
PATH variable. It is important that you use an SDK because the installation process
sets the JAVA_HOME and related variables to point to this directory. For procedures,
see one of the following:
• “Starting Graphical-Mode Installation for .jar Installation Files” on page 2-4
• “Starting Console-Mode Installation for .jar Installation Files” on page 3-5
* Includes 35 MB for the Java 2 SDK and 36 MB for examples and samples.
** Includes 50 MB for the Java 2 SDK and 32 MB for examples and samples.
UNIX Enter the following option on the command line when you start
the installation program:
-[Link]=tmpdirpath
Where tmpdirpath is the full path of the directory that you
want to use to temporarily store files used by the WebLogic Server
installation program.
Administrator Privileges
If you choose to run the Configuration Wizard (launched as part of a custom installation) to create
user domains, you can install the server as a Windows service. When a server is installed as a Windows
service, it starts automatically each time you boot your Windows [Link] must have Administrator
privileges to install the server as a Windows service.
For additional information, see “Setting Up WebLogic Server as a Windows Service” in the BEA
WebLogic Server Administration Guide at
[Link]
AsWindowsService.
Licenses for pre-7.0 versions of WebLogic Server will not work with WebLogic Server 7.0. You must
upgrade your license to a 7.0 [Link] format. Procedures for upgrading a license file and
installing permanent licenses are provided in Chapter 5, “Installing and Updating a WebLogic Server
License.”
Typical Installation
Results of a typical installation depend on the software distribution method:
! Net installer
If you downloaded the net installer version of the WebLogic Server installation program, a
typical installation installs all components and samples included in WebLogic Platform, which
includes WebLogic Server with WebLogic Workshop, BEA WebLogic Integration™, and BEA
WebLogic Portal™ (about 295 MB). To install WebLogic Server without WebLogic Integration
and WebLogic Portal when using a net installer, you must select the Custom installation option.
See “Custom Installation” on page 1-12.
Note: The Configuration Wizard is not invoked in a typical installation, regardless of the
download option you select. If you select the typical installation option, you can manually
launch the Configuration Wizard from the Start menu (Windows only) or with a command
line script. See “Configuring Domains, Servers, and Clusters with the Configuration
Wizard” on page 2-10.
Custom Installation
A custom installation allows you to choose exactly which components you want to install on your
system. Component options depend on how you acquired the software:
! Net installer
If you downloaded the net installer version of the WebLogic Server installation program (and
you choose the custom installation option), you can select the Server, WebLogic Workshop, and
Server Examples options, as well as options for additional WebLogic Platform components.
Details about those additional options are beyond the scope of this document. For information
about installing WebLogic Platform and all of its components, see the WebLogic Platform
Installation Guide at
[Link]
Note: By default, all WebLogic Platform components are selected. You must clear the check box
for all components that you do not want to install.
In a custom installation, regardless of the distribution method, the BEA WebLogic Platform
Configuration Wizard is optionally invoked after the selected components are installed on your
system. You use the Configuration Wizard to configure WebLogic domains using preconfigured
domain templates that facilitate domain creation for the target environment.
! Ensure that licensing works correctly for the installed BEA products
sdk (dir)
logs (dir)
utils (dir)
[Link]
[Link]
UpdateLicense (.cmd/.sh)
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 weblogic700 (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. See “Understanding the WebLogic Server Directory Structure” on
page 7-4.
Note: For some UNIX platforms, the WebLogic Server installation program does not install the 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 only one instance of each version of a
BEA product that uses the BEA Home directory convention. For example, you can install only
one instance of WebLogic Server 7.0 in a BEA Home directory, but that BEA Home directory
may also contain an instance of WebLogic Server 6.1.
sdk directory Contains the software for the Java 2 SDK installed with WebLogic Server. The
SDK provides the Java run-time environment (JRE) and tools for compiling and
debugging Java applications. Options include:
• jdk131_XX—the 1.3.1 version of the Sun Java 2 SDK
• jrockitXXX—The WebLogic JRockit SDK.
Note: SDK options vary by hardware platform. For some UNIX platforms, the
WebLogic Platform installation program does not include an SDK.
logs directory Contains a history file of installation and uninstallation for the BEA Home
directory.
utils directory Contains utilities that support the installation of all BEA WebLogic Platform
products. The [Link] file contains code that supports the
UpdateLicense utility.
[Link] file An 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.
The format of this license has changed in WebLogic Server 7.0. To convert a
pre-7.0 [Link] file to a WebLogic Server 7.0 [Link] file, refer
to the procedures in “Upgrading Licenses from Previous WebLogic Server
Releases” on page 5-5. To add a non-expiring (permanent) license or to update a
license file for additional functionality, you must update the [Link] file
using the UpdateLicense utility. For details, see “Updating Your [Link]
File” on page 5-2.
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.
[Link] 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 A command file (Windows) or a shell script (UNIX) that updates the current
(.cmd/.sh) [Link] file with new license sections. The result is a merged license
that contains both the existing and new license sections. For details about using
the UpdateLicense utility, see “Updating Your [Link] File” on page 5-2.
where c:\bea is the BEA Home directory and weblogic700 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 weblogic700, 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. See “Files and Directories Installed” on page 7-4 for more
information.
Syntax
To create a verbose log file during installation, include the -log=/full_path_to_log_file
option in the command line or script. For example:
serverXXX_win32.exe -log=D:\logs\wls_install.log
The following sections describe how to install WebLogic Server using the graphical user interface
(GUI) mode installation on both Windows and UNIX systems:
! “Starting the Installation Program in Graphical Mode on Windows Platforms” on page 2-2
! “Starting the Installation Program in Graphical Mode on a UNIX Platform” on page 2-3
! “Configuring Domains, Servers, and Clusters with the Configuration Wizard” on page 2-10
! “What’s Next?” on page 2-12
! Make sure you are installing the product on a supported platform. A complete list of supported
platforms can be found at
[Link]
! You should read all of Chapter 1, “Preparing to Install WebLogic Server,” specifically the
following sections:
– “Installation Prerequisites” on page 1-7
– “Choosing the Type of Installation” on page 1-11
! You cannot re-install WebLogic Server in the same location (BEA Home or physical location) as
previously installed. You must first uninstall the WebLogic Server installation, as described in
Chapter 8, “Uninstalling WebLogic Server,” or install in another location. You can, however,
install additional Weblogic Platform components, such as the WebLogic Server examples, in the
same location without uninstalling existing components.
! All WebLogic Platform components installed in a BEA product directory (for example,
c:\bea\weblogic700) must be at the same version level. If you attempt to install additional
components at a higher version than those that are already installed in that directory, the
installation program prompts you to upgrade your existing components before you can proceed
with the installation. For example, if you installed WebLogic Server 7.0 Service Pack 1, and later
attempt to install WebLogic Portal 7.0 Service Pack 2, you are required to upgrade WebLogic
Server to Service Pack 2 before you can install WebLogic Portal. For details on upgrading your
installation, see Chapter 6, “Installing WebLogic Server Service Packs and Rolling Patches.”
2. If you are installing WebLogic Server from a CD-ROM, go to step 3. If you are installing WebLogic
Server by downloading from the BEA Web site:
a. Go to [Link] and
download the WebLogic Server installation file for your platform. See “Web Distribution of
WebLogic Server” on page 1-4 for information about download options.
b. Go to the directory where you downloaded the installation file and double-click the
installation file:
serverXXX_win32.exe (package installer file—WebLogic Server, WebLogic Workshop,
and related samples)
net_platformXXX_win32.exe (net installer file—WebLogic Platform)
where XXX is the version number of the software you are installing.
Note: The net installer installs all or part of the WebLogic Platform, which includes
WebLogic Server with WebLogic Workshop. See “Web Distribution of WebLogic
Server” on page 1-4 for more details.
c. Navigate to the folder for the Windows installation and double-click serverXXX_win32.exe,
where XXX is the version number of the software you are installing. The installation program
begins to install WebLogic Server.
Note: To run graphical-mode installation, your console must support a Java-based GUI. If the
installation program determines that your system cannot support a Java-based GUI, the
installation program automatically starts console-mode installation. For details, see
Chapter 3, “Installing WebLogic Server Using Console-Mode Installation.”
3. If you are installing WebLogic Server from a CD-ROM, go to step 4. If installing WebLogic Server
by downloading from the BEA Web site:
a. Go to [Link] and
download the WebLogic Server installation file for your platform. See “Web Distribution of
WebLogic Server” on page 1-4 for information about download options.
b. In the command shell, go to the directory where you downloaded the installation program and
start the installation by entering the following commands:
chmod a+x filename
./[Link]
where [Link] is the name of the WebLogic Server installation program specific to
your platform.
b. Go to the CD-ROM directory, and navigate to the folder for the installation program for your
hardware platform.
3. Include the bin directory of the appropriate SDK at the beginning of the PATH variable on the
target system. For example:
PATH=$JAVA_HOME/bin:$PATH
export PATH
Where JAVA_HOME is the full path to the SDK directory.
For each command, [Link] is the name of the WebLogic Server installation file, for
example pj_serverXXX_generic.jar. Filenames for the net installer are preceded by net_,
for example, net_pj_platformXXX_generic.jar.
Note: You can also include the -log=/full_path_to_log_file option on the command
line to create a log file during installation. For example:
java -jar [Link] -log=/nfs/home1/logs/wls_install.log
The installation program creates a verbose installation log. For more information, see
“Generating a Verbose Installation Log” on page 1-16.
Welcome Click the Next button to proceed or cancel the installation at any time by
clicking Exit.
BEA License Agreement Read the BEA Software License Agreement and indicate your acceptance of the
terms of the agreement by selecting Yes. To continue with the installation, you
must accept the terms of the license agreement and then click Next.
Choose BEA Home Directory Specify the BEA Home directory that will serve as the central support directory
for all BEA products installed on the target system. If you already have a BEA
Home directory on your system, you can select that directory (recommended) or
create a new BEA Home directory. If you choose to create a new directory, the
WebLogic Server installer program automatically creates the directory for you.
For details about the BEA Home directory, see “BEA Home Directory” on
page 1-13.
Choose Install Type Select the option button for the type of installation you want to perform:
• Typical—In a typical installation, all software components in the
distribution are installed on your system. Sample domains are
preconfigured for use with the PointBase database during installation
allowing you to execute the samples when the installation is complete.
Software components vary depending on the distribution method of the
software:
CD-ROM or package installer: Installs WebLogic Server with WebLogic
Workshop and all related examples.
Net installer: Installs all components of WebLogic Platform, which includes
WebLogic Server with WebLogic Workshop as well as WebLogic Portal,
WebLogic Integration, and all related examples.
Note: When you choose the Typical installation option, the Configuration
Wizard is not invoked automatically as part of the installation.
However, you can launch it manually after the installation is complete
from the Start menu or with a command line script. See “Configuring
Domains, Servers, and Clusters with the Configuration Wizard” on
page 2-10.
• Custom—In a custom installation, you can select the software components
you want to install and optionally run the Configuration Wizard to create
custom WebLogic domains.
Note: If you downloaded software using the net installer option and you want
to install WebLogic Server without the additional WebLogic Platform
components, select the Custom installation option and select only the
components you want to install. If you want to install components
other than server and server examples, see the WebLogic Platform
Installation Guide at
[Link]
[Link].
For additional information about installation types, see “Choosing the Type of
Installation” on page 1-11.
If you are using the typical installation option, go to the Choose Product
Directory window.
Choose Components Select the components to install by selecting or clearing the appropriate check
boxes.
Note: This window is displayed
only if you select Custom This window displays a tree-view of all the components available for installation.
installation in the In an initial installation, all components are checked.
Choose Install Type The check boxes for components already installed on your system appear as a
window. greyed-check box.
If you want to install components other than server and server examples, see the
WebLogic Platform Installation Guide at
[Link]
html.
Specify Download Options Indicate your preferences for downloading the software as follows:
Note: This window is displayed • Storage Directory—Specify a storage directory to which you want to
only if you are using the download the software components. The installation program downloads an
net installer. archive file to your system for each component that you choose to install.
You can choose any location on your system for these files. It does not need
to be collocated with the installation setup file, or with the installed
software.
• Remove downloaded files after installation—Select this check box if you
want the installation program to delete the downloaded files after the
installation is complete. If you do not select this check box, the downloaded
files are saved to the storage directory you specified.
• Use HTTP Proxy—Select this check box if you want to use an HTTP proxy
server for the download. To use an HTTP proxy server, you must provide the
following information:
Host—enter the name or IP address of the proxy server
Port—enter the port number of the proxy server
Archive Integrity Check This window is displayed while the installation program verifies that the
component archive files downloaded successfully.
Note: This window is displayed
only if you are using the
net installer. Click Next when the download verification is complete.
Choose Product Directory Specify the directory in which you want to install the WebLogic Server software
and click Next. You can accept the default product directory (weblogic700)
Note: This window is not or create a new product directory.
displayed if you are
performing a Custom For additional information and a description of the resulting directory structure,
installation and you have see “Product Installation Directory” on page 1-16.
selected the same BEA If you choose to create a new directory, the installation program automatically
Home directory that creates the directory for you, if necessary.
contains previously
When you click Next, the installation program begins copying the components
installed WebLogic
you specified to your system.
Server components. In
that case, the selected
components are
installed in the Product
Directory you specified
during the initial
installation.
Status Read the information displayed about BEA products and services and click Next
when the installation program has finished copying the specified files to your
system. If you are performing a Typical installation, the installation is complete.
Run Configuration Wizard Indicate whether you want to run the Configuration Wizard to create an
application domain by selecting the appropriate option.
Note: This window is displayed
only if you select Custom If you choose Yes, proceed to Configuring Domains, Servers, and Clusters with
installation in the the Configuration Wizard for a summary description of the Configuration
Choose Install Type Wizard. For complete details, refer to Creating New Domains Using the
window. Configuration Wizard in Creating and Configuring WebLogic Server Domains
at
[Link]
[Link].
If you choose No, you can run the Configuration Wizard from the Start menu
(Windows only) or from the command line at a later time.
You use the Configuration Wizard to create and configure custom WebLogic domains. A domain is an
interrelated set of WebLogic Server resources that are managed as a unit. A domain includes one or
more WebLogic Servers, and may also include WebLogic Server clusters.
The Configuration Wizard uses pre-configured domain templates that you use to create a domain for
the target environment. WebLogic Server 7.0 includes the following templates:
! WLS Domain—The basic, full-featured template for creating WebLogic domains for WebLogic
Server.
! WLS Examples—A template used for updating the WebLogic Server examples domain when
you install a service pack.
! WLS Petstore—A template used for recreating the WebLogic Server Pet Store domain when
you install a service pack.
If you install additional WebLogic Platform components, you may see additional templates when you
start the Configuration Wizard. For detailed procedures for using the Configuration Wizard with
WebLogic Platform, see Using the Configuration Wizard at
[Link] For details about
available Configuration Wizard templates, see the Configuration Wizard Template Reference at
[Link]
Configuration Options
Based on the pre-configured domain template that you choose when running the Configuration
Wizard, you are prompted to supply certain types of information for each domain. The following list
offers a sampling of the type of information you need to provide. Complete details are provided in
Creating New Domains Using the Configuration Wizard in Creating and Configuring WebLogic Server
Domains at [Link]
! Server Type, such as a Single standalone server, or an Administration Server with Managed
Servers or clustered Managed Servers.
! A domain directory in which to create the domain. By default, this directory is created in
bea_home\user_projects, where bea_home is the BEA Home directory containing the
support information for this installation. If the directory does not exist, the Configuration
Wizard creates the directory for you.
Note: On UNIX systems, do not use spaces in the domain name.
! Configuration information for the server, such as Server Name, Listen Address, Listen Port, and
SSL Listen Port. Default values are provided for most values.
Note: On UNIX systems, do not use spaces in the server name.
! A system user name and password. WebLogic Server user names and passwords can contain any
character from the JDK supported character sets, including international characters.
Characters should also be valid XML data characters, which excludes the following characters:
<, >, [, and ].
! An option to configure the server as a Windows service. If you choose to do so, the server starts
automatically each time you boot your Windows system. You must have Administrator
privileges to the install the server as a Windows service. For complete details about installing
and running WebLogic Server as a Windows service, see Setting Up a WebLogic Server as a
Windows Service in the Administration Guide at
[Link]
verAsWindowsService.
Note: You must follow XML guidelines for characters when specifying values in the Configuration
Wizard. That is, you cannot use characters reserved for use in XML, such as <, >, [, and ].
What’s Next?
To learn more about WebLogic Server 7.0, view the following files:
! about_wls.html
Summarizes new features in this version of WebLogic Server and provides pointers to useful
related information.
On a Windows system, access this file by using the About WebLogic Server shortcut on the Start
Menu. On both Windows and UNIX systems, access the about_wls.html file at
WL_HOME\server\about_wls.html, where WL_HOME represents the top-level installation
directory for the WebLogic Server software.
! [Link]
The following sections describe how to install WebLogic Server using console-mode installation:
! Make sure you are installing the product on a certified platform. A complete list of certified
platforms can be found at
[Link]
! You should read all of Chapter 1, “Preparing to Install WebLogic Server,” specifically the
following sections:
– “Installation Prerequisites” on page 1-7
– “Choosing the Type of Installation” on page 1-11
– “Selecting Directories for the WebLogic Server Installation” on page 1-13
! You cannot re-install WebLogic Server in the same location (BEA Home or physical location) as
it was previously installed. You must first uninstall the WebLogic Server installation, as
described in Chapter 8, “Uninstalling WebLogic Server,” or install in another location. You can,
however, install additional Weblogic Platform components, such as the WebLogic Server
examples, in the same location without uninstalling existing components.
! All WebLogic Platform components installed in a BEA product directory (for example,
/bea/weblogic700) must be at the same version level. If you attempt to install additional
components at a higher version than those that are already installed in that directory, the
installation program prompts you to upgrade your existing components before you can proceed
with the installation. For example, if you installed WebLogic Server 7.0 Service Pack 1, and later
attempt to install WebLogic Portal 7.0 Service Pack 2, you are required to upgrade WebLogic
Server to Service Pack 2 before you can install WebLogic Portal. For details on upgrading your
installation, see Chapter 6, “Installing WebLogic Server Service Packs and Rolling Patches.”
a. Go to [Link] and
download the WebLogic Server installation file for your platform. See “Web Distribution of
WebLogic Server” on page 1-4 for information about download options.
b. Go to the directory where you downloaded the installation program and invoke the installation
procedure by entering one of the following commands:
serverXXX_win32.exe -mode=console (package installer file—WebLogic Server,
WebLogic Workshop, and related samples)
net_platformXXX_win32.exe -mode=console (net installer file—WebLogic
Platform)
where XXX is the version number of the software you are installing.
Note: By default, the net installer installs all or part of the WebLogic Platform, which
includes WebLogic Server with WebLogic Workshop. See “Web Distribution of
WebLogic Server” on page 1-4 for more details.
The path must be to a file. All folders in the path must exist before you execute the
command or the installation program will not create the log file. For more information,
see “Generating a Verbose Installation Log” on page 1-16.
The installation program begins to install WebLogic Server.
The path must be to a file. All folders in the path must exist before you execute the
command or the installation program will not create the log file.
important that you use an SDK because the installation process sets the JAVA_HOME and related
variables to point to this directory.
3. If you are installing WebLogic Server from CD-ROM, go to step 4. If installing WebLogic Server by
downloading from the BEA Web site:
a. Go to [Link] and
download the WebLogic Server installation file for your platform. See “Web Distribution of
WebLogic Server” on page 1-4 for information about download options.
b. Go to the directory where you downloaded the installation program and invoke the installation
procedure by entering the following commands:
chmod a+x [Link]
./[Link] -mode=console
where [Link] is the name of the WebLogic Server installation file.
Note: To create a verbose log file during installation, include the
-log=/full_path_to_log_file option in the command line. For example:
./serverXXX_solaris.bin -mode=console
-log=/nfs/home1/logs/wls_install.log
The path must be to a file. All folders in the path must exist before you execute the
command or the installation program will not create the log file.
b. Go to the CD-ROM directory, and navigate to the folder for the installation program for your
hardware platform.
where [Link] is the name of the WebLogic Server installation program specific to
your platform.
Note: To create a verbose log file during installation, include the
-log=/full_path_to_log_file option in the command line. For example:
./serverXXX_solaris.bin -mode=console
-log=/nfs/home1/logs/wls_install.log
The path must be to a file. All folders in the path must exist before you execute the
command or the installation program will not create the log file.
3. Include the bin directory of an appropriate Java 2 SDK at the beginning of the PATH variable on
the target system. For example:
PATH=$JAVA_HOME/bin:$PATH
export PATH
Where JAVA_HOME is the full path to the Java 2 SDK directory.
5. Go to the directory that contains the installation file and invoke the installation procedure as
described in Table 3-1.
Table 3-1 Commands for Starting the WebLogic Server Installation Program
If you are . . . Enter the following command . . .
For each command, [Link] is the name of the WebLogic Server installation file, for
example pj_serverXXX_generic.jar. Filenames for the net installer are preceded by net_,
for example, net_pj_platform700_generic.jar.
Note: To create a verbose log file during installation, include the
-log=/full_path_to_log_file option in the command line. For example:
java -jar [Link] -mode=console
-log=/nfs/home1/logs/wls_install.log
The path must be to a file. All folders in the path must exist before you execute the
command or the installation program will not create the log file.
1. At the Welcome prompt, type next or press Enter to continue with the installation process.
2. Read the BEA Software License Agreement and indicate your acceptance or rejection of the
terms of the agreement by typing yes or no, respectively, at the prompt. To review the entire
agreement, press Enter or type more several times. If you type no, the installation process
terminates. To proceed with the installation, type yes to indicate your agreement with the terms
of the license.
The Choose BEA Home directory prompt is displayed.
3. Specify the BEA Home directory that will serve as the central support directory for all BEA
products installed on the target system. For details about the BEA Home directory, see “BEA
Home Directory” on page 1-13.
The installation program displays the following prompt:
Choose BEA Home Directory:
Select Option:
1 - Create a new BEA Home
2 - Use an existing BEA Home [/home/bea]
After you have selected your BEA Home directory and confirmed your selection, the Choose
Install Type prompt is displayed.
4. Specify the type of installation you want to perform by entering the number associated with the
install type, as shown in the following text:
Choose Install Type:
If you are using the net installer, the Specify Download Options prompt is displayed. Go to
step 6.
– Type 2 to choose a Custom installation. In a custom installation, you can select the software
components you want to install and optionally run the Configuration Wizard to create
custom WebLogic domains.
The Choose Components prompt is displayed.
For more information about typical and custom installations, see “Choosing the Type of
Installation” on page 1-11.
5. Select the components you want to install. The available components are displayed as follows:
Choose Components:
Release 7.0
|-----WebLogic Server [0] x
| |-----Server [0.0] x
| |-----Workshop [0.1] x
| |-----Server Examples [0.2] x
Note: When you select or deselect components to install, the installation program checks for
dependencies between components and automatically modifies the list of selected
components.
If you are installing from CD-ROM or using the package installer, the Choose Product Directory
prompt is displayed. Go to step 7.
If you are using the net installer (installation program filenames beginning with net_), the
Specify Download Options prompt is displayed.
6. Indicate your preferences for downloading the software. The installation program presents the
following options:
SPECIFY DOWNLOAD OPTIONS
After you have indicated your preferences, the files begin downloading to the storage directory
you specified. When the download is complete, the installation program verifies that the
component archive files downloaded successfully. If the installation program cannot verify the
integrity of the download, the following message is displayed:
The required installation files could not be [Link]
may download them from BEA or select different components.
When the verification is complete, the Choose Product Directory prompt is displayed.
7. Specify the directory in which you want to install the WebLogic Server software. Select the
default product directory (bea_home/weblogic700) or create a new product directory. If you
specify a new directory, the installation program automatically creates the directory for you.
The choices displayed in this section are as follows:
Choose Product Directory:
Select Option:
1 - Input new Product Directory
2 - Reset to default
8. Indicate whether you want to run the Configuration Wizard to create a WebLogic domain by
selecting the appropriate option. The console displays the following options:
Run Configuration Wizard
What’s Next?
To learn more about WebLogic Server 7.0, view the following files:
! about_wls.html
Summarizes new features in this version of WebLogic Server and provides pointers to useful
related information.
You can access the about_wls.html file at WL_HOME/server/about_wls.html, where
WL_HOME represents the top-level installation directory for the WebLogic Server software.
! [Link]
The following sections describe how to install WebLogic Server using the installation program in silent
mode on both Windows and UNIX systems:
The instructions in this section assume that you have already acquired the installation program, either
on CD or from the Web. For more information, see “WebLogic Server Distribution Methods” on
page 1-3.
Note: You must use a package installer for silent-mode installation. Silent-mode installation is not
supported with the net installer. Filenames for the net installer version of the installation
program are preceded by net_, for example net_platformXXX_solaris.bin. Do not
attempt to use installation programs with filenames beginning with net_ for silent-mode
installation.
Notes: Silent-mode installation supports typical installation only: you must install all software
components included in the WebLogic Server installation program. For information about the
components installed in a typical installation, see “Choosing the Type of Installation” on
page 1-11.
You cannot re-install WebLogic Server in the same location as a previously installed version.
You must first uninstall the WebLogic Server installation, as described in Chapter 8,
“Uninstalling WebLogic Server,” or install in another location.
1. Create a template file that contains the configuration settings, such as BEA Home directory,
product directory, and options for the Configuration Wizard.
For the detailed procedure, see “Creating a Silent-Mode Installation Template File” on page 4-4.
For a sample template file, see “Sample Silent-Mode Installation Template Files” on page 4-8.
2. Start the silent-mode installation process and use the values specified in the template file.
For the detailed procedure, see “Starting the Silent-Mode Installation Process on a Windows
System” on page 4-18 and “Starting the Silent-Mode Installation Process on a UNIX System” on
page 4-19.
A silent-mode installation takes the same amount of time as a standard installation. During
silent-mode installation, an initial installation program window appears briefly, indicating that the
installation has started. No other messages are displayed indicating the installation is in progress or
has completed successfully, even if errors are encountered.
Notes: During silent-mode installation, the installation program does not validate entries in the
[Link] file. If there are errors in the [Link] file, the installation will fail.
You must use a package installer for silent-mode installation. Silent-mode installation is not
supported with the net installer. Filenames for the net installer version of the installation
program are preceded by net_, for example net_platformXXX_solaris.bin. Do not
attempt to use installation programs with filenames beginning with net_ for silent-mode
installation.
Silent-mode installation requires the same temporary space and uses the same temporary storage
directories as a standard installation. See “Temporary Storage Space Requirements” on page 1-9 for
more information. The installation program does not prompt you if there is not enough space in the
temporary directory.
! You must use the package installer for silent-mode installation. Silent-mode installation is not
supported with the net installer. Filenames for the net installer version of the installation
program are preceded by net_, for example net_platformXXX_solaris.bin, where XXX is
the version number of the software you are installing. Do not attempt to use installation
programs with filenames beginning with net_ for silent-mode installation.
! Silent-mode installation supports typical installation only: you must install all the components
of WebLogic Server. For information about the components installed in a typical installation,
see “Choosing the Type of Installation” on page 1-11.
! Silent-mode installation requires the same temporary disk space and uses the same temporary
storage directories as a standard installation. For more information, see “Temporary Storage
Space Requirements” on page 1-9. The installation program does not prompt 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
appears briefly, indicating that the installation has started. No message is displayed indicating
the installation is in progress or has completed successfully.
! Incorrect entries in the [Link] file can cause installation failures. To help you determine the
cause of a failure, we recommend that you create a log file when you start the installation.
1. From a supported browser, download a sample template file for silent-mode installation. Several
sample templates are available for various configurations:
– Comprehensive Template File Sample
– Sample Template for Configuring a Domain with Separate Admin and Managed Servers
– Sample Template for Configuring a Cluster of Managed Servers
– Sample Template for Adding a Managed Server to an Existing Domain
All four templates are available later in this chapter at the following location:
[Link]
You can download these templates from a browser using the instructions that are provided with
the description of each template. (If you are viewing these templates in PDF format, you can
copy them directly from the Adobe Reader.)
2. Save the contents of the template file in a text file named [Link] in the directory
containing the WebLogic Server installer.
Note: The XML definition (<?xml version="1.0" encoding="UTF-8"?>) must be at the
very beginning of the template file. There cannot be any spaces or line breaks before the
XML definition.
3. In the [Link] file, modify the values for the keywords shown in Table 4-1 to create your
desired configuration.
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 ].
Note: For silent install only, the BEA Home directory cannot exist
before installing the software.
USER_INSTALL_DIR The full pathname for the directory where you want to install the
WebLogic Platform software. For details, see “Product Installation
Directory” on page 1-16.
RUN_DOMAIN_WIZARD true to run the Configuration Wizard and create a domain as part of
the installation, false to skip it. If you choose to run the Configuration
Wizard, you must specify values for the appropriate data-values as listed
in the following rows in this table. For more information about the
Configuration Wizard, see “Creating New Domains Using the
Configuration Wizard” in Creating and Configuring WebLogic Server
Domains at
[Link]
[Link].
[Link] The full path to the domain directory. The domain directory should be
named the same name as the domain.
C_domainName Name of the domain to create. The name must match the directory
name specified for [Link].
Note: On UNIX systems, do not include spaces in the domain name.
C_serverName Name of the server to configure, used as the server name for stand-alone
servers and as the Administration Server for domains with Managed
Servers and clustered servers.
C_username An administrative user name to start the server and access the
Administration Console. Do not use spaces or XML reserved characters.
C_password A password for the administrative user. It must contain at least eight
characters but no more than 20 characters. Do not use spaces or XML
reserved characters.
C_serverListenAddress The system IP address or DNS name for the server. You can leave this
blank if you want to use localhost and the server IP address to
access the server and the Administration Console.
C_serverListenPort A dedicated TCP/IP port number for the Administration Server. This
number specifies the port at which the server listens for connections.
Typically, 7001. The port number can be any integer from 1 to 65535.
C_serverSSLListenPort A dedicated secure listen port number for the Administration Server.
The secure listen port number is used for secure Web connections based
on the secure sockets layer (SSL) protocol. Typically, 7002. The port
number can be any integer from 1 to 65535 and cannot be the same port
as the C_serverListenPort.
ClusterName Name of the cluster to create. Only applicable if you are creating a
cluster.
ClusterPort The MultiCast port that the Administration Server uses to communicate
with clustered servers. Typically, 7777. Only applicable if you are
creating a cluster.
ClusterMCAddr The cluster MultiCast IP address that the Administration Server uses to
communicate with clustered servers. Typically, [Link]. Valid
MultiCast addresses begin with 237, 238, or 239. Only applicable if
you are creating a cluster.
ADMIN_LISTEN_PORT The port at which the Administration Server listens. Used when
configuring a Managed Server.
selectedJar The full path to the template JAR file that the Configuration Wizard
uses to create the domain and configure servers.
INSTALL_WINDOWS_STARTUP yes to add an option to the Windows Start menu to start the server; no
_MENU (the default value) to skip the Start menu option.
DB_EMAIL_ADDRESS The address from which e-mail can be sent by a workflow instance in
WebLogic Integration.
managedServers data group Determines the configuration of the group of Managed Servers in the
domain. This data group applies only when you select "Admin Server
with Managed Server(s)" as the value for SERVER-RUN-AS.
For each Managed Server in your configuration, specify the following:
• managedServerRegName—name of the server as registered
with the Administration Server. Alphanumeric characters only; no
spaces.
• managedServerHostIP—IP address or DNS name of the
machine on which the server is installed.
• managedServerListenPort—server listen port.
• managedServerSSLListenPort—secure listen port for the
server.
clusterServers data group Determines the configuration of the group of clustered Managed
Servers in the domain. This data group applies only when you select
"Admin Server with Clustered Managed Server(s)" as the value for
SERVER-RUN-AS.
For each server in the cluster, specify the following:
• clusterServerRegName—name of the server as registered
with the Administration Server. Alphanumeric characters only; no
spaces.
• clusterServerHostIP—IP address or DNS name of the
machine on which the server is installed.
• clusterServerListenPort—server listen port.
• clusterServerSSLListenPort—secure listen port for the
server.
See Creating New Domains Using the Configuration Wizard in Creating and Configuring WebLogic
Server Domains at
[Link] for more
information about how the Configuration Wizard works and the options you can select.
! Sample Template for Configuring a Domain with Separate Admin and Managed Servers
3. Specify the file name [Link] and save it in the directory containing the WebLogic Server
installation program.
<domain-template-descriptor>
<input-fields>
<data-value name="BEAHOME" value="C:\bea" />
<data-value name="USER_INSTALL_DIR" value="C:\bea\weblogic700" />
<data-value name="RUN_DOMAIN_WIZARD" value="false" />
<!--The following values are used by the Configuration Wizard to create and
configure a domain.-->
<!--The selectedJar value determines the template that the Configuration Wizard
uses to create a domain and configure servers.-->
<data-value name="selectedJar"
value="C:\bea\weblogic700\common\templates\domains\[Link]" />
</input-fields>
</domain-template-descriptor>
3. Specify the file name [Link] and save it in the directory containing the WebLogic Server
installation program.
You can modify this template according to Table 4-1, and use the new file as a template when installing
WebLogic Server in silent mode. In Listing 4-2, the strings highlighted in bold are significant in
defining the configuration. Compare the settings for these strings to the settings for corresponding
strings in the other sample template files.
Listing 4-2 Configuring a Domain with Separate Administration Server and Managed Server(s)
<domain-template-descriptor>
<input-fields>
<data-value name="BEAHOME" value="C:\bea\user_domains\mydomain" />
<data-value name="USER_INSTALL_DIR"
value="C:\bea\user_domains\mydomain\weblogic700" />
<data-value name="RUN_DOMAIN_WIZARD" value="true" />
<!--The following values are used by the Configuration Wizard to create and
configure a domain.-->
<data-value name="[Link]"
value="C:\bea\user_domains\mydomain\user_domains\d1" />
<data-value name="C_domainName" value="d1" />
<data-value name="C_serverName" value="admin" />
<data-value name="C_username" value="system" />
<data-value name="C_password" value="weblogic" />
<data-value name="C_serverListenAddress" value="" />
<data-value name="C_serverListenPort" value="8001" />
<data-value name="C_serverSSLListenPort" value="8002" />
<!-- The SERVER-RUN-AS value determines the server configuration that the
Configuration Wizard creates. There are four options as indicated by the
following lines. Comment out the three options you do not want to use.-->
<data-element>
<data-value name="managedServerRegName" value="ms2" />
<data-value name="managedServerHostIP" value="host2" />
<!-- The selectedJar value determines the template that the Configuration Wizard
uses to create a domain and configure servers.-->
<data-value name="selectedJar" value="C:\bea\user_domains\mydomain\
weblogic700\common\\templates\domains\[Link]" />
</input-fields>
</domain-template-descriptor>
3. Specify the file name [Link] and save it in the directory containing the WebLogic Server
installation program.
You can modify this template according to Table 4-1, and use the new file as a template when installing
WebLogic Server in silent mode. In Listing 4-3, the strings highlighted in bold are significant in
defining the configuration. Compare the settings for these strings to the settings for corresponding
strings in the other sample template files.
Listing 4-3 Configuring a Domain with Administration server and Clustered Managed Server(s)
<domain-template-descriptor>
<input-fields>
<!-- The following values are used by the Configuration Wizard to create and
configure a domain.-->
<data-value name="[Link]"
value="C:\bea\user_domains\mydomain\user_domains\myCluster" />
<data-value name="C_domainName" value="myCluster" />
<data-value name="C_serverName" value="admin" />
<data-value name="C_username" value="system" />
<data-value name="C_password" value="weblogic" />
<data-value name="C_serverListenAddress" value="localhost" />
<data-value name="C_serverListenPort" value="8001" />
<data-value name="C_serverSSLListenPort" value="8002" />
<data-value name="ClusterName" value="mycluster" />
<data-value name="ClusterPort" value="7777" />
<!-- The SERVER-RUN-AS value determines the server configuration that the
Configuration Wizard creates. There are four options as indicated by the
following lines. Comment out the three options you do not want to use.-->
<data-group name="clusterServers">
<data-element>
<data-value name="clusterServerRegName" value="cs1" />
<data-value name="clusterServerHostIP" value="host1" />
<data-value name="clusterServerListenPort" value="1001" />
<data-value name="clusterServerSSLListenPort" value="1002" />
</data-element>
<data-element>
<data-value name="clusterServerRegName" value="cs2" />
<data-value name="clusterServerHostIP" value="host2" />
<data-value name="clusterServerListenPort" value="2001" />
<data-value name="clusterServerSSLListenPort" value="2002" />
</data-element>
</data-group>
- <!-- The selectedJar value determines the template that the Configuration
Wizard uses to create a domain and configure servers.-->
<data-value name="selectedJar"
value="C:\bea\user_domains\mydomain\weblogic700\common\
templates\domains\[Link]" />
</input-fields>
</domain-template-descriptor>
3. Specify the file name [Link] and save it in the directory containing the WebLogic Server
installation program.
You can modify this template according to Table 4-1, and use the new file as a template when installing
WebLogic Server in silent mode. In Listing 4-4, the strings highlighted in bold are significant in
defining the configuration. Compare the settings for these strings to the settings for corresponding
strings in the other sample template files.
<domain-template-descriptor>
<input-fields>
<data-value name="BEAHOME" value="C:\bea\user_domains\mydomain" />
<data-value name="USER_INSTALL_DIR"
value="C:\bea\user_domains\mydomain\weblogic700" />
<data-value name="RUN_DOMAIN_WIZARD" value="true" />
<!-- The following values are used by the Configuration Wizard to create and
configure a domain.-->
<data-value name="[Link]"
value="C:\bea\user_domains\mydomain\user_domains/d2" />
<data-value name="C_domainName" value="d2" />
<data-value name="C_serverName" value="admin" />
<data-value name="C_username" value="system" />
<data-value name="C_password" value="weblogic" />
<data-value name="C_serverListenAddress" value="" />
<data-value name="C_serverListenPort" value="8001" />
<data-value name="C_serverSSLListenPort" value="8002" />
<!-- The SERVER-RUN-AS value determines the server configuration that the
Configuration Wizard creates. There are four options as indicated by the
following lines. Comment out the three options you do not want to use.-->
<data-group name="managedServers">
<data-element>
<data-value name="managedServerRegName" value="ms1" />
<data-value name="managedServerHostIP" value="host1" />
<data-value name="managedServerListenPort" value="1001" />
<data-value name="managedServerSSLListenPort" value="1002" />
</data-element>
<data-element>
<data-value name="managedServerRegName" value="ms2" />
<data-value name="managedServerHostIP" value="host2" />
<data-value name="managedServerListenPort" value="2001" />
<data-value name="managedServerSSLListenPort" value="2002" />
</data-element>
</data-group>
<!-- The selectedJar value determines the template that the Configuration Wizard
uses to create a domain and configure servers.-->
<data-value name="selectedJar" value="C:\bea\user_domains\mydomain
\weblogic700\common\templates\domains\[Link]" />
</input-fields>
</domain-template-descriptor>
3. Go to the directory that contains the installation file and start the installation procedure by
entering the following command, making sure to specify the full pathname of the [Link]
template file:
[Link] -mode=silent -silent_xml=path_to_silent.xml
where filename is the name of the WebLogic Server installation file, and
path_to_silent.xml is the full path to the [Link] template file.
3. Include the bin directory of an appropriate SDK at the beginning of the PATH variable on the
target system. For example:
PATH=$JAVA_HOME/bin:$PATH
export PATH
where JAVA_HOME is the full path to the SDK directory.
4. Go to the directory that contains the installation file and start the installation procedure as
described in Table 4-2, making sure to specify the full pathname of the [Link] template
file.
For all commands, [Link] is the name of the WebLogic Server installation file (for
example pj_server700_generic.jar) and path_to_silent.xml is the full path to the
[Link] template file.
WebLogic Server requires a valid product license to run. The following sections explain how to
acquire, install, and update a WebLogic Server license:
Evaluation Licenses
The first time you download and install a BEA WebLogic product, the installation program installs an
evaluation license so that you can start using the product immediately. Subsequently, when you
download and install additional BEA products that contain a [Link] file as part of the
distribution, the installer program automatically adds the new evaluation product licenses to the
[Link] file, but does not extend the evaluation period.
To use WebLogic Server beyond the evaluation period, contact your salesperson about extending the
evaluation period or purchasing a development or production license.
All WebLogic Server evaluation products are licensed for use on a single server machine and allow up
to 20 connections to the server.
! You applied for and received an extension to the evaluation period of WebLogic Server.
! You possess a non-expiring license file for an earlier release of WebLogic Server and you want to
upgrade to a WebLogic Server 7.0 license after downloading WebLogic Server 7.0 from the BEA
Web site. You must convert the license to a WebLogic Server 7.0 license. To do so, see
“Upgrading Licenses from Previous WebLogic Server Releases” on page 5-5.
Note: Enabling 128-bit encryption requires that the 128-bit encryption license be present in the
[Link] file before you install the WebLogic Server software. For details, see “Enabling
128-Bit Encryption” on page 5-4.
1. Save the license update file that you received through e-mail with a name other than
[Link], in the target BEA Home directory. For example, save the file as
platform_license.bea. Use this file as the license_update_file in step 4 of this
procedure.
Warning: Do not overwrite or change the name of the existing [Link] file.
2. Open a command prompt window or a command shell and go to the target BEA Home directory.
3. If it is not already included, add the Java 2 SDK to your PATH variable by entering the following
commands:
– On a Windows system:
set PATH=BEA_HOME\sdk\bin;%PATH%
– On a UNIX system:
PATH=BEA_HOME/sdk/bin:$PATH
export PATH
In these commands, sdk is the directory name of the Java 2 SDK being used for this
installation. For example, jdk131_06 or jrockit70sp2_131.
4. Merge the license update file into your existing license by entering one of the following
commands:
– On a Windows system:
UpdateLicense license_update_file
– On a UNIX system:
sh [Link] license_update_file
license_update_file is the name to which you saved the license update file in step 1.
5. Save a copy of your updated [Link] file in a safe place outside the WebLogic Integration
and application installation directories.
Although no one else can use your license file, you should save it in a place that is protected
from both malicious and innocent tampering.
2. Create a new directory that you want use as a BEA home directory and place the 128-bit
encryption license in the new directory. The license file must be named [Link].
2. In the left navigation area of the Web page, click Upgrade/Downgrade and follow the instructions
on the page. If the license you want to upgrade is not listed, click the Add a Missing License link
in the left navigation area. The BEA Licensing team will research the missing license for you.
You can upgrade your WebLogic Server 7.0 installation by using one of two methods: Smart Update or
a downloadable upgrade installer. The following sections describe how to upgrade your software using
either method:
! “Important Note About Updating WebLogic Server 7.0 GA” on page 6-3
! “Installing Service Packs and Rolling Patches Using Smart Update” on page 6-4
! “Installing Service Packs and Rolling Patches with a Downloadable Installer” on page 6-7
You can install service packs and rolling patches using the following methods:
! Use Smart Update to search for, download, and install software updates from the BEA Web site.
Smart Update downloads only the updates for the software components currently installed in
the target BEA Home directory. For instructions, see “Installing Service Packs and Rolling
Patches Using Smart Update” on page 6-4.
Note: Smart Update upgrades your Windows installation to use the Sun Java 2 SDK and your
Linux installation to use the WebLogic JRockit SDK. If you want to use a different SDK,
you should use a WebLogic Platform upgrade installer that is bundled with the
appropriate SDK or change the SDK, as described in "Switching JVMs in WebLogic
Platform" in the WebLogic Platform Release Notes, at the following URL:
[Link]
undledJVM
! Download the package upgrade installer from the BEA Customer Support Web site at
[Link] The upgrade installation program supports graphical and console
modes of installation. For instructions, see “Installing Service Packs and Rolling Patches with a
Downloadable Installer” on page 6-7.
Both Smart Update and the package upgrade installer create a backup file containing the media state
of the current installation and information about files that were added during the upgrade. This
backup file is used to restore system state if any errors occur during installation, and when you
uninstall or roll back an upgrade installation. For a typical upgrade installation of WebLogic Platform
(that is, all WebLogic Platform component products installed), the backup file requires a minimum of
250MB of available disk space.
! The upgrade installer only updates files installed by the WebLogic Platform installation
program.
! The package upgrade installer replaces the JVM in the current installation with the JVM that is
bundled with the package upgrade installer. For example, if your current installation uses the
Sun JVM and you upgrade your installation using a package upgrade installer that is bundled
with the WebLogic JRockit JVM, the resulting installation will use the WebLogic JRockit JVM.
! If you are not using the JVM that was bundled with the WebLogic Platform installation and you
have edited your scripts to reference the new JVM location, the upgrade installer will not
update all of the edited scripts appropriately unless you edit the scripts to restore the original
JVM values.
To avoid manual editing in the future, it is recommended that you rename the non-bundled JVM
to match the directory structure of the bundled JVM, as described in “Switching JVMs in
WebLogic Platform” in the WebLogic Platform Release Notes at the following URL:
[Link]
JVM
! The upgrade installer does not update any user-created files, or directories created using the
Configuration Wizard (user_projects by default).
! Temporary patches are not compatible across service packs. If you installed a temporary patch
and updated your classpath to reference the patch, you may need to remove any references to
the patch from your classpath.
UNIX:
WL_HOME/common/nodemanager
WL_HOME/server/bin/[Link]
In these pathnames, WL_HOME is the root directory of your WebLogic Platform installation, for
example, c:\bea\weblogic700.
Once the upgrade installation is complete, you should restore these files.
For more information about Node Manager, see “Managing Server Availability with Node Manager" in
Creating and Configuring WebLogic Server Domains at:
[Link]
instructions, see “Installing Service Packs and Rolling Patches with a Downloadable Installer” on
page 6-7. After you install a service pack, you can use Smart Update to install future service packs.
To see which version of WebLogic Server you have installed, open BEA_HOME\logs\[Link]
(BEA_HOME/logs/[Link] on UNIX) in a text editor and look at the last entry in the log file. Each
line in the log file represents an installation event for the current BEA home—an installation or an
uninstallation. If the log entry indicates that the version installed is WebLogic Platform 7.0 SP0 or
earlier, you cannot use Smart Update. If the log entry indicates that the version installed is WebLogic
Platform [Link] or later, you can use Smart Update to install Service Pack 1 ([Link]) and future
service packs.
Note: WebLogic Server and WebLogic Platform use the same installation framework. Therefore,
installation log entries use the term WebLogic Platform to indicate an installation of either
WebLogic Server or WebLogic Platform.
! Installed Products—The left pane of the Smart Update window contains a tree displaying
product and release information for products installed in the target BEA Home directory.
! Upgrade Options—The top-right pane lists the service packs and rolling patches, if any, that are
available for the installed products.
! Downgrade Options—The bottom-right pane lists the versions of the product to which you can
revert your installation, if applicable. For details about uninstalling maintenance upgrades with
Smart Update, see “Uninstalling a Service Pack or Rolling Patch with Smart Update” on
page 8-9.
Note: Smart Update only checks for products associated with the current BEA Home directory. If
you have multiple BEA Home directories on your system, you must run Smart Update for each
one to install available service packs. For more information about BEA Home directories, see
“BEA Home Directory” on page 1-13.
To install service packs or rolling patches using Smart Update, follow these steps:
1. Shut down any servers that are running. Hot installation of a service pack or rolling patch is not
supported.
3. In the left pane of the Smart update window, select the release for the product you want to
update.
Available service packs or rolling patches, if any, are displayed in the Upgrade Options section
of the window.
4. In the Upgrade Options pane, select the service pack or rolling patch to install and click OK.
The Enter BEA eSupport Identification dialog box is displayed.
6. Click Next to proceed with the installation. You may cancel the installation at any time by
clicking Exit.
The Downloading Archive Information window is displayed briefly, followed by the Specify
Download Options window.
9. Indicate whether you want to proceed with the installation automatically after the download is
complete by selecting or clearing the appropriate check box. This check box is selected by
default. If you clear it, you need to click Next when the download is complete to proceed with
the installation.
When the download is complete, the Archive Integrity Check window is displayed while it
verifies the integrity of the upgrade archive files you downloaded.
When the archive verification is complete, the Confirm Product Directory window is displayed,
which contains the path to the BEA home directory and to the product directory in which the
WebLogic Server software will be updated.
! Graphical mode. See “Installing a Service Pack Upgrade Using Graphical Mode” on page 6-8 for
instructions.
! Console mode. See “Installing a Service Pack Upgrade Using Console Mode” on page 6-10 for
instructions.
Notes: To run graphical-mode installation, your console must support a Java-based GUI. If the
installation program determines that your system cannot support a Java-based GUI, the
installation program automatically starts console-mode installation.
The upgrade installer does not support silent-mode installation.
The WebLogic Server installation program requires a Java run-time environment (JRE) to run. A Java 2
Software Development Kit (SDK), which includes a JRE, is bundled in the Windows installation program and in
some UNIX installation programs (those with filenames ending in .bin). For other UNIX platforms, the
WebLogic Server installation program does not include the Java 2 SDK in the installation program. Filenames
for these installation programs end in .jar. To run the .jar installation programs, you must have the
appropriate version of the Java 2 SDK installed on your system, and include the bin directory of the Java 2 SDK
at the front of the PATH variable. It is important that you use an SDK because the installation process sets the
JAVA_HOME and related variables to point to this directory.
1. Download the service pack upgrade installer specific to your platform from the BEA Customer
Support Web site at [Link]
Note: You will need to log in using your eSupport username and password to download a service
pack or rolling patch. If you do not have an eSupport account, you can register for one on
the BEA Customer Support Web site.
2. Shut down any servers that are running. Hot installation of a service pack or rolling patch is not
supported.
Windows 1. Go to the directory where you downloaded the installation program and
double-click [Link], where [Link] is name of the
installation file you downloaded from the BEA Customer Support Web site, for
example, serverXXX_upgrade_win32.exe.
The installation program begins to install the upgrade.
2. Proceed to step 4 following this table.
5. Select the BEA Home directory containing the release of WebLogic Server you want to upgrade
and click Next.
The Confirm Product Directory window is displayed, which includes the path to the BEA home
directory and to the directory in which the WebLogic Server software will be updated.
6. Click Next.
A progress window is displayed during the upgrade installation. When the installation is
finished, the Installation Complete window is displayed.
7. Click Done on the Installation Complete window to exit the installation program.
1. Download the service pack upgrade installer specific to your platform from the BEA Customer
Support Web site at [Link]
Note: You must log in using your eSupport username and password to download a service pack
or rolling patch. If you do not have an eSupport account, you can register for one on the
BEA Customer Support Web site.
2. Shut down any servers that are running. Hot installation of a service pack or rolling patch is not
supported.
For example:
serverXXX_upgrade_solaris.bin -mode=console
-log=/home/bea/logs/server_install.log
The path must be to a file. All folders in the path must exist before you execute the command;
otherwise, the installation program will not create the log file.
4. At the Welcome prompt, type next or press Enter to continue with the installation process.
The Choose BEA Home directory prompt is displayed.
5. Select the BEA Home directory associated with the installation of WebLogic Server that you
want to update. If you have only one installation of WebLogic Server installed on the current
machine, only one BEA Home directory is listed. For details about the BEA Home directory, see
“BEA Home Directory” on page 1-13.
The installation program displays the following prompt:
Choose BEA Home Directory:
->1| /nfs/home/user1/bea1
2| /nfs/home/user1/bea2
Enter index number to select OR [Exit][Previous][Next]>
Press Enter to use the selected BEA Home directory or type the number of the BEA Home
directory that you want to select.
Whether you accept the selected BEA Home directory or select a different BEA Home directory,
you are prompted to confirm your selection, as shown in the following example:
Choose BEA Home Directory:
6. The Confirm Product Directory panel indicates the folder in which the WebLogic Server software
will be updated. For example:
Confirm Product Directory:
Product Installation Directory: [/nfs/home/user1/bea1/weblogic700]
Files in /nfs/home/user1/bea1/weblogic700 will now be upgraded to the
[Link] maintenance level.
Enter [Exit][Previous][Next]>
Press Enter or type next to continue.
7. After you confirm the product directory, the installation program makes a backup copy of
specific files from the previous installation and then installs new versions of the files.
When the installation is complete, the following prompt is displayed:
Install Complete
Congratulations! WebLogic Platform [Link]
has been successfully installed to
/nfs/home/user1/bea1/weblogic700.
Press any key to continue OR [Exit]>
What’s Next?
After you upgrade your WebLogic Server 7.0 installation, you may need to upgrade your user domains.
If you created user domains using the Configuration Wizard and templates available with WebLogic
Platform 7.0 GA software or a service pack earlier than the current service pack, you may need to
update the domains for use with the current service pack. Upgrade procedures are provided in
“Migrating User-Created Domains” in the BEA WebLogic Platform Release Notes at
[Link]
The following sections describe the tasks you perform after installing WebLogic Server:
! “Starting the Examples, Pet Store, and Workshop Examples Servers” on page 7-5
! User Projects—Contains a folder for each domain that you create using the Configuration
Wizard and for which you choose to create a Start Menu option. You use the shortcuts in these
folders to start servers in each domain.
! WebLogic Server 7.0—Contains shortcuts to launch the Examples and Pet Store servers,
introductory documentation about WebLogic Server, and so forth. See Figure 7-2.
! WebLogic Workshop—Contains shortcuts to launch the WebLogic Workshop and examples. For
details about using WebLogic Workshop, see the WebLogic Workshop documentation at
[Link]
! Smart Update—Runs Smart Update to check for and install available software updates for
installed BEA products. See “WebLogic Server Service Packs and Rolling Patches” on page 6-1.
! About WebLogic Server 7.0—Opens About WebLogic Server in a Web Browser. The document
contains important information about WebLogic Server.
! WebLogic Builder—Starts WebLogic Builder, which is a graphical tool for assembling a J2EE
application module, creating and editing its deployment descriptors, and deploying it to a
WebLogic server. For more information about WebLogic Builder, see “WebLogic Builder” at
[Link]
weblogic700 Folders for files shared by all WebLogic Platform components, as well
as individual folders for each installed WebLogic Platform component.
The following sections provide instructions for starting the Examples, Pet Store, and cgServer (for the
WebLogic Workshop Samples project) servers on a Windows or UNIX system.
! “Starting the Pet Store Server and Application on a Windows System” on page 7-7
! “Starting the Pet Store Server and Application on a UNIX System” on page 7-8
For complete information about starting and stopping WebLogic Server, see “Starting and Stopping
WebLogic Servers” in the Administration Guide at
[Link]
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time
(as installed) because all of them are configured to use port 7001 as the non-secure listening
port and 7002 as the secure listening port. To run them concurrently, you must reconfigure
the listening ports as described in Setting the Listen Port in the Administration Console
Online Help at
[Link]
sten_port.
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time
(as installed) because all of them are configured to use port 7001 as the non-secure listening
port and 7002 as the secure listening port. To run them concurrently, you must reconfigure
the listening ports as described in Setting the Listen Port in the Administration Console
Online Help at
[Link]
sten_port.
server boots, your browser should automatically launch and point to the WebLogic Server Petstore
Demo running on the server. Additional information for configuring and executing the Pet Store server
and the Pet Store application is provided in the
WL_HOME\samples\server\src\petstore\[Link] file.
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time
(as installed) because all of them are configured to use port 7001 as the non-secure listening
port and 7002 as the secure listening port. To run them concurrently, you must reconfigure
the listening ports as described in Setting the Listen Port in the Administration Console
Online Help at
[Link]
sten_port.
To start the Pet Store server and application on a UNIX system, follow these steps:
The [Link] script sets up the proper CLASSPATH variable for the Pet Store
server and loads the configuration in the
SAMPLES_HOME/server/config/petstore/[Link].
For complete information about starting and stopping servers, see “Starting and Stopping WebLogic
Servers” in the Administration Guide at
[Link]
Note: You cannot start the Examples, Pet Store, and Workshop Examples servers at the same time
(as installed) because all of them are configured to use port 7001 as the non-secure listening
port and 7002 as the secure listening port. To run them concurrently, you must reconfigure
the listening ports as described in Setting the Listen Port in the Administration Console
Online Help at
[Link]
sten_port.
2. The Administration Console prompts you for a username and password. Enter a username and
password for the server you want to administer. For the Examples and Pet Store servers,
weblogic (username and password) is the default administrative user. For the Workshop
Examples server, installadministrator (username and password) is the default
administrative user.
From the command line 1. Open a command prompt window and go to the following directory:
WL_HOME\server\bin (Windows)
WL_HOME/server/bin (UNIX)
In these pathnames, WL_HOME represents the directory in which you
installed WebLogic Platform.
2. Make sure that your environment is set by entering the following command
at the prompt:
[Link] (Windows)
[Link] (UNIX)
3. Enter the following command at the prompt:
java -version
If you are using WebLogic JRockit, BEA WebLogic JRockit(R)
Virtual Machine is displayed in the output.
Using the server log file 1. In a text editor, open the server log file for your domain.
The location of the server log file may vary. For some domains, the log file is
called [Link] and is located in the domain_name\logs
directory, where domain_name is one of the following: the name of the
domain you provided when you created the domain using the Configuration
Wizard, or, the name of a sample domain.
For example,
C:\bea\user_projects\mydomain\logs\[Link].
For details about server log files, see “Using Log Messages to Manage
WebLogic Server” in the BEA WebLogic Server Administration Guide at
[Link]
[Link].
Note: The server log file is created the first time the server is started.
2. Search the log file for the following values:
[Link]
[Link]
These entries in the log file provide the build version of the JVM and the JVM
vendor (for example Sun Microsystems Inc. or BEA Systems, Inc.)
The following sections provide platform-specific procedures for uninstalling WebLogic Server:
! “Uninstalling a Service Pack or Rolling Patch with Smart Update” on page 8-9
! 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 was invoked from within the product directory structure—specifically, within the
uninstaller directory.
If you have installed a service pack or rolling patch, you can also use the uninstallation program to
revert to a prior service pack. See “Uninstalling WebLogic Server in Graphical Mode” on page 8-2.
Note: If you installed WebLogic Server with additional WebLogic Platform components, refer to the
WebLogic Platform Installation Guide at
[Link] for
information about uninstalling WebLogic Platform components.
1. Shut down any servers that are running. If you configured any of the servers as a Windows service,
you should stop the service(s) before uninstalling the software.
4. Select the components to uninstall by selecting or clearing the appropriate check boxes, then
click Next. By default, all installed components are selected, indicating that they will be
removed.
5. Click Done in the Uninstalling WebLogic Platform 7.0 window to exit the uninstallation program.
1. Shut down any servers that are running. If you configured any of the servers as a Windows service,
you must stop the service(s) before uninstalling the software.
3. Press Enter or type next to proceed to the next panel of the uninstallation program.
4. Select the components you want to uninstall. The available components are displayed as follows:
Choose Components:
Release 7.0
+----WebLogic Server [0] v
+----Server [0.0] v
+----Workshop [0.1] v
+----Server Examples [0.2] v
7. When the uninstallation process is complete, press Enter or type done to complete the
uninstallation and exit the uninstallation program.
! The BEA Home directory, including the logs and utils subdirectories
1. Shut down any servers that are running. If you configured any of the servers as a Windows service,
you must stop the service(s) before uninstalling the software.
2. Start the uninstallation program as described in the Table 8-3.
Notes: When you run the uninstallation program in silent mode, no messages are displayed
indicating the uninstallation is in progress or has completed successfully, even if errors are
encountered.
To create a verbose log file during silent uninstallation, include the
-log=full_path_to_log_file option in the command line. For example:
uninstall -mode=silent -log=d:\logs\weblogic_uninstall.log
The path must be to a file. All folders in the path must exist before you execute the command
or the installation program will not create the log file.
! You can revert to the prior service pack installation on your system. For example, if you
installed WebLogic Server 7.0, then installed Service Pack 1 (SP1), you can revert to WebLogic
Server 7.0. If you have WebLogic Server 7.0 SP1 installed on your system and you upgrade to
WebLogic Server 7.0 SP2 (when available), you can revert only to WebLogic Server 7.0 SP1, you
cannot revert to WebLogic Server 7.0.
! You can revert rolling patch upgrades to the prior service pack on which the rolling patch is
based. (Rolling patches are cumulative, each rolling patch replaces all earlier rolling patches
on a particular service pack base.) For example, if you installed WebLogic Server 7.0 SP1, then
installed rolling patches 1 and 2 (RP1 and RP2), you can revert to WebLogic Server 7.0 SP1. You
cannot revert to an earlier rolling patch.
For instructions, see “Uninstalling a WebLogic Server Service Pack or Rolling Patch in Graphical
Mode” on page 8-8 or “Uninstalling a WebLogic Server Service Pack or Rolling Patch in Console Mode”
on page 8-9.
Note: If you install additional WebLogic Platform components after installing a service pack or
rolling patch, you cannot roll back to any previous versions of the product.
To revert to a previously installed version of WebLogic Server, you can use the uninstallation program
or Smart Update. See “Uninstalling a Service Pack or Rolling Patch with Smart Update” on page 8-9
for instructions to use Smart Update to roll back to a previous installation.
1. Shut down any servers that are running. If you configured any server as a Windows service, stop
the service(s) before uninstalling the software.
2. Start the uninstallation program as described in the Table 8-1, “Starting the Uninstallation
Program in Graphical Mode,” on page 8-3.
The WebLogic Server Uninstaller Welcome window is displayed.
3. Click Next to start the uninstall program.
The Select Uninstall Type window is displayed.
4. Select the service pack to which you want to roll back your system installation and click Next.
A status window displays the progress of the uninstallation. A message is displayed when the
rollback is complete.
1. Shut down any servers that are running. If you configured any of the servers as a Windows service,
you must stop the service(s) before uninstalling the software.
2. Start the uninstallation program as described in the Table 8-2, “Starting the Uninstallation
Program in Console Mode,” on page 8-4.
The Welcome text is displayed.
3. Press Enter or type next to proceed to the next panel of the uninstallation program.
The Uninstall Options panel is displayed:
4. At the prompt, type the number of the option for the service pack to which you want to roll back
your system installation and press Enter.
Text messages indicate the progress of the uninstallation.
! You can revert to the prior service pack installation on your system. For example, if you
installed WebLogic Server 7.0, then installed Service Pack 1 (SP1), you can revert to WebLogic
Server 7.0. If you have WebLogic Server 7.0 SP1 installed on your system and you upgrade to
WebLogic Server 7.0 SP2, you can revert only to WebLogic Server 7.0 SP1, you cannot revert to
WebLogic Server 7.0.
! You can revert rolling patch upgrades to the prior service pack on which the rolling patch is
based. (Rolling patches are cumulative, each rolling patch replaces all earlier rolling patches
on a particular service pack base.) For example, if you installed WebLogic Server 7.0 SP1, then
installed rolling patches 1 and 2 (RP1 and RP2), you can revert to WebLogic Server 7.0 SP1. You
cannot revert to an earlier rolling patch.
Note: If you install additional WebLogic Platform components after installing a service pack or
rolling patch, you cannot roll back to any previous versions of the product.
You can also uninstall a service pack or rolling patch using the standard uninstallation process. For
more information, see “Uninstalling WebLogic Server in Graphical Mode” on page 8-2.
To uninstall a service pack or rolling patch, follow these instructions:
1. Start Smart Update as described in Table 6-1, “Starting Smart Update,” on page 6-5.
2. In the left pane, select the release for the product you want to roll back.
Service packs and rolling patches that you can uninstall (or roll back) are displayed in the
Downgrade Options section of the window.
3. In the Downgrade Options pane, select the service pack or rolling patch to uninstall and click
OK.
The BEA Uninstaller Program opens.
! To continue installing the software using a different BEA Home directory, select an existing
BEA Home directory that does not contain a WebLogic Server installation or create a new BEA
Home directory.
! Exit the installation program. If you want to reinstall WebLogic Server 7.0 in the same BEA
Home, you must uninstall the previous installation. You can invoke the uninstall program as
described in one of the following sections:
– “Uninstalling WebLogic Server in Graphical Mode” on page 8-2
– “Uninstalling WebLogic Server in Console Mode” on page 8-4
Then reinstall the software as described in one of the following sections:
– Chapter 2, “Installing WebLogic Server Using Graphical-Mode Installation”
– Chapter 3, “Installing WebLogic Server Using Console-Mode Installation”
– Chapter 4, “Installing WebLogic Server Using Silent-Mode Installation”
U
uninstall
short cut 7-2
UNIX
starting WebLogic Platform installation 2-3,
3-3
update
license 5-2
UpdateLicense tool
about 1-15