Skip navigation.
Downloads | Product Documentation | Support

Installing WebLogic Platform

# Preparing to Install WebLogic Platform

BEA WebLogic Platform 8.1 includes application infrastructure technology from proven BEA products that are used by thousands of customers worldwide, including BEA WebLogic Server®, BEA WebLogic WorkshopTM, BEA WebLogic PortalTM, BEA WebLogic IntegrationTM, and BEA JRockit® 1.4.2 SDK.

You can install WebLogic Server using a separate WebLogic Server installation program, or as a component selection using the WebLogic Platform installation program. The information provided in this document describes both methods of installation.

The following sections provide information that you need to know before installing the BEA WebLogic Platform software:

- About BEA WebLogic Platform Installation
- WebLogic Platform Software Components
- Dependencies Between Installable Components
- WebLogic Platform Distribution Methods
- Installation Prerequisites
- Choosing a Type of Installation
- Installing the Node Manager as a Windows Service
- Selecting Directories for the WebLogic Platform Installation
- Where to Find Upgrade Information
- About Smart Update

# About BEA WebLogic Platform Installation

BEA WebLogic Platform 8.1 is distributed and installed using the BEA Installation and Distribution System, which provides a complete framework for the following:

- Simplified distribution of BEA products via download from the BEA Web site using a net installer.
- Installation and uninstallation of the entire WebLogic Platform product, or individual components, as desired.
- Simplified mechanism for obtaining and installing product upgrades using Smart Update.
- The ability to launch installers for third-party products.

Two installation programs are available: a WebLogic Platform installer for all components of WebLogic Platform, and a WebLogic Server installer, which includes WebLogic Server and WebLogic Workshop only. Both programs provide the same functionality; all installation procedures described in this document apply to both installers.

## WebLogic Express Support

You can use the WebLogic Server or WebLogic Platform installation program to install BEA WebLogic ExpressTM. WebLogic Express is a cost-effective entry point to the WebLogic Product Family creating a productive ramp for customers to begin using BEA's market-leading application server technology. From WebLogic Express, customers can easily upgrade to BEA WebLogic Platform, where they can take advantage of a wide variety of enterprise-level functionality.

Note: WebLogic Express does not support applications developed in the WebLogic Workshop IDE.

To install WebLogic Express, you install WebLogic Server and then install a WebLogic Express license. The WebLogic Express license activates WebLogic Express features. For additional information about WebLogic Express, see the WebLogic Express documentation at the following URL:

>     http://e-docs.bea.com/wls/docs81/wlx.html

## WebLogic Server Process Edition Support

You must use the WebLogic Platform installation program to install WebLogic Server Process EditionTM. WebLogic Server Process Edition provides you with the technologies and tools you need to effectively service-enable your existing resources, create composite services using process-driven development, and extend these composite services to interact with other applications and technologies. Each of these phases allows you to take distinct measurable steps that are effective for both project and enterprise level architectures.

### Installation

To use WebLogic Server Process Edition, you must install WebLogic Integration using the WebLogic Platform installation program. You can install WebLogic Integration (using any of the installation methods described in this document) as part of a complete WebLogic Platform installation, or individually by performing a custom installation, and selecting WebLogic Integration.

Note: When you install WebLogic Integration, WebLogic Server and WebLogic Workshop are installed by default.

For standard installation procedures, refer to the following chapters:

- Installing WebLogic Platform Using Graphical-Mode Installation
- Installing WebLogic Platform Using Console-Mode Installation
- Installing WebLogic Platform Using Silent-Mode Installation

### Licensing

The development license installed on your system when you install WebLogic Integration enables full WebLogic Integration functionality for use in a development environment. To use WebLogic Server Process Edition in a production environment, you must install a WebLogic Server Process Edition license.

WebLogic Server Process Edition enables a subset of the WebLogic Integration functionality. To avoid building applications that are not supported by the WebLogic Server Process Edition license, you should change the development mode in the WebLogic Workshop IDE to WebLogic Server Process Edition. For more information, refer to the section "WebLogic Server Process Edition Mode" in the WebLogic Server Process Edition Overview at the following URL: `http://e-docs.bea.com/wli/docs81/peoverview/introduction.html#process_edition_mode`.

Note: WebLogic Integration and WebLogic Platform licenses include support for WebLogic Server Process Edition functionality, and may also be used for WebLogic Server Process Edition applications. For more information about WebLogic Platform licenses, see the Licensing page at `http://e-docs.bea.com/platform/docs81/interm/license.html`.

Instructions for installing a license with WebLogic Server Process Edition support are provided in Installing and Updating WebLogic Platform License Files.

For more information about WebLogic Server Process Edition, see the WebLogic Server Process Edition documentation at the following URL:

`http://e-docs.bea.com/wli/docs81/wlspe.html`

## WebLogic Platform ISV Edition Support

You must use the WebLogic Platform installation program to install WebLogic Platform ISV Edition. WebLogic Platform ISV Edition is a special software package tailored for ISVs who have a current agreement with BEA to build value-added solutions on WebLogic. WebLogic Platform ISV Edition comprises a set of WebLogic Platform components specifically packaged to help ISVs jumpstart their service-oriented architecture (SOA) initiatives.

### Installation

To use WebLogic Platform ISV Edition, you must install all the WebLogic Platform product components using the WebLogic Platform installation program. You can do so using any of the installation methods described in this document.

For standard installation procedures, refer to the following chapters:

- Installing WebLogic Platform Using Graphical-Mode Installation
- Installing WebLogic Platform Using Console-Mode Installation
- Installing WebLogic Platform Using Silent-Mode Installation

### Licensing

The development license installed on your system when you install WebLogic Platform enables full WebLogic Platform functionality for use in a development environment. To use WebLogic Platform ISV Edition in a production environment, you must install a WebLogic Platform ISV Edition license.

WebLogic Platform ISV Edition enables a subset of the WebLogic Platform functionality. It provides full WebLogic Server, WebLogic Workshop, and BEA JRockit SDK functionality, and a subset of WebLogic Integration and WebLogic Portal functionality. The WebLogic Integration features included with WebLogic Platform ISV Edition are the same as those included with WebLogic Server Process Edition.

Instructions for installing a license with WebLogic Platform ISV Edition support are provided in Installing and Updating WebLogic Platform License Files.

For more information about WebLogic Platform ISV Edition, see the WebLogic Platform ISV Partners' Guide at the following URL: `http://e-docs.bea.com/platform/docs81/isv/index.html`.

## Installation Methods

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

- Graphical mode

Graphical-mode installation is an interactive, GUI-based method for installing WebLogic Platform. It can be run on both Windows and UNIX systems. For installation procedures, see Installing WebLogic Platform Using Graphical-Mode Installation.

Note: If you want to run graphical-mode installation, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX systems do. If you attempt to start the installation program in graphical mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation.

- Console mode

Console-mode installation is an interactive, text-based method for installing WebLogic Platform, from the command line, on either a UNIX system or a Windows system. For instructions for using this method, see Installing WebLogic Platform Using Console-Mode Installation.

- Silent mode

Silent-mode installation is a noninteractive method of installing WebLogic Platform that requires the use of an XML properties file for selecting installation options. You can run silent-mode installation in either of two ways: as part of a script or from the command line. Silent-mode installation is a way of setting installation configurations only once and then using those configurations to duplicate the installation on many machines. For instructions, see Installing WebLogic Platform Using Silent-Mode Installation.

# WebLogic Platform Software Components

WebLogic Platform consists of the following software that can be installed on your system:

- WebLogic Server
- WebLogic Workshop
- WebLogic Integration
- WebLogic Portal
- WebLogic Platform Samples and Utilities
- BEA JRockit SDK

Note: If you are using the WebLogic Server installation program, only the WebLogic Server and WebLogic Workshop components are available for installation.

For additional information about:

- The features and capabilities of the WebLogic Platform components, see Introducing BEA WebLogic Platform at `http://e-docs.bea.com/platform/docs81/intro/index.html`
- The features and capabilities of WebLogic Server, see Introduction to Weblogic Server and WebLogic Express at `http://e-docs.bea.com/wls/docs81/intro/index.html`
- The features and capabilities of BEA JRockit, see Introduction to BEA JRockit SDK at `http://e-docs.bea.com/wljrockit/docs142/intro/index.html`
- Operating systems and hardware supported by WebLogic Platform 8.1, see Supported Configurations for WebLogic Platform 8.1 at `http://e-docs.bea.com/platform/suppconfigs/configs81/81_over/index.html`

## WebLogic Server

WebLogic Server is the foundation of the WebLogic Platform product: it provides the core services that ensure a reliable, available, scalable, and high performing execution environment for your application. If you select the entire WebLogic Server component, the installation program installs the WebLogic Server program files and the server examples.

WebLogic Server consists of the following subcomponents:

- Server—WebLogic Server program files that contain the core Java 2 Enterprise Edition (J2EE) features.
- Server Examples—WebLogic Server examples and the MedRec example servers and sample applications. These servers and sample applications demonstrate a variety of J2EE features. Resources are provided to help you build, configure, and run each of the sample applications. You must install the server to install and use the WebLogic Server samples.

## WebLogic Workshop

WebLogic Workshop is a unified, visual development environment and run-time framework that lets all application developers—not only J2EE experts—rapidly create, test, and deploy enterprise-class Web applications, Web services, and custom controls for WebLogic Server, WebLogic Integration, and WebLogic Portal. If you select the entire WebLogic Workshop component, the installation program installs the run-time framework, the visual development environment, and the Workshop samples.

WebLogic Workshop consists of the following subcomponents:

- Workshop Runtime Framework—an abstraction layer, provided on top of J2EE, to help all developers build Web applications, Web services, and custom controls.
- WebLogic Workshop Application Developer Edition—a design-time visual development environment in which developers can build applications by adding methods and controls, setting properties, and writing business logic with Java.

Note: Development of WebLogic Integration and WebLogic Portal applications with the WebLogic Workshop IDE requires the installation of the corresponding WebLogic Workshop extensions.

- Workshop Samples—samples that demonstrate how to build applications with WebLogic Workshop.

## WebLogic Integration

WebLogic Integration provides a development and run-time framework for joining business process management and application integration capabilities into a single, flexible environment.

Note: The BPEL Import and Export Tools and the TIBCO RendezvousTM Control and Event Generator subcomponents are not installed by default. To install them you need to choose Custom installation and select the check box for each subcomponent. Alternatively, you can clear the checkbox for the WebLogic Integration component, and then select it again. All the subcomponents are then selected and will be installed on your system.

Note: You must install WebLogic Integration to have access to the WebLogic Server Process Edition controls. For more information about WebLogic Server Process Edition, see the WebLogic Server Process Edition documentation at `http://e-docs.bea.com/wli/docs81/wlspe.html`

WebLogic Integration consists of the following subcomponents:

- Integration Server—the full set of components that comprise WebLogic Integration, including client components Application Integration Design Console, Integration Admin Console, Worklist, and Format Builder.
- WebLogic Workshop Integration Extension—framework and tools for integrating enterprise applications to provide an integrated development environment in WebLogic Workshop.
- Integration Examples—example application that illustrates the use of the Application Integration subcomponent of WebLogic Integration.
- BPEL Import and Export Tools—WebLogic Workshop design-time tools for importing and exporting processes developed in Business Process Execution Language (BPEL) 1.1.

- The BPEL Import tool imports BPEL 1.1 compliant code into a Process Definition for Java (JPD) process file, where it can be used in the WebLogic Workshop design environment.
- The BPEL Export tool exports the semantics of JPD code into BPEL, where it can be used in a BPEL-compatible design environment.

Note: The installation of this subcomponent requires the installation of the WebLogic Workshop Integration Extension.

- TIBCO RendezvousTM Control and Event Generator—Package that enables business processes to send and receive messages in the TIBCO Rendezvous environment.

- The TIBCO RV control is a Java control for WebLogic Workshop that enables seamless connection to, and transfer of data with, TIBCO Rendezvous using the Rendezvous daemon.
- The TIBCO RV event generator is a WebLogic Integration event generator that listens for TIBCO Rendezvous messages and raises events to Message Broker channels.

Note: Use of the TIBCO RendezvousTM Control and Event Generator with BEA WebLogic Integration in no manner confers or grants the right to use TIBCO RendezvousTM including "dynamic libraries." In order to use such TIBCO products, the user of the TIBCO RendezvousTM Control and Event Generator must obtain a valid license from TIBCO.

### Installing the TIBCO Rendezvous Control and Event Generator Subcomponent

If you plan to install the TIBCO Rendezvous Control and Event Generator subcomponent of WebLogic Integration 8.1 SP5, you must install and configure TIBCO Rendezvous on your machine before you install WebLogic Integration.

Information about obtaining and installing a licensed copy of TIBCO Rendezvous is available at the following URL:

`http://www.tibco.com`

By simply following the installation instructions provided by TIBCO for this product, you can make sure that TIBCO Rendezvous is installed correctly, ready to be used later with WebLogic Integration. For more information, see the TIBCO Rendezvous Control and Event Generator User Guide at the following URL:

`http://e-docs.bea.com/wli/docs81/tibcorv/index.html`

## WebLogic Portal

WebLogic Portal simplifies the production and management of custom-fit portals. WebLogic Portal simplifies, personalizes, and lowers the cost of access to information, applications, and business processes, whether the person who needs such access is an employee, a partner, or a customer. If you select the entire WebLogic Portal component, the installation program installs the server program files, the WebLogic Workshop extension, and the samples.

WebLogic Portal consists of the following subcomponents:

- Portal Server—program files for the portal campaign and personalization services features.
- WebLogic Workshop Portal Extension—set of application-building designers and services in WebLogic Workshop, letting you add interaction management (personalization and behavior tracking) to your applications.
- Portal Examples—sample files for all of the WebLogic Portal functionality. These examples help you learn how WebLogic Portal works and demonstrate implementation techniques for your own solutions.

## WebLogic Platform Samples and Utilities

Platform Samples and Utilities apply to all components of WebLogic Platform; they cannot be used unless all WebLogic Platform components (WebLogic Server, WebLogic Workshop, WebLogic Integration, and WebLogic Portal) are installed.

The sample application is the Platform Tour: a fully integrated application that demonstrates key features of WebLogic Platform.

## BEA JRockit SDK

The BEA JRockit SDK provides tools, utilities, and a complete run-time environment for developing and running applications using the Java programming language. The BEA JRockit SDK includes the BEA JRockit Java Virtual Machine (JVM), the first commercial server-side JVM for Intel architectures. The BEA JRockit SDK is fully integrated into the WebLogic Platform package, and is supported by all WebLogic Platform components. In addition, it is available as a standalone SDK.

The BEA JRockit 1.4.2 SDK is installed automatically when you install WebLogic Server or WebLogic Platform on Windows and Linux platforms. On Windows platforms only, two Java 2 SDKs are installed on your system: the BEA JRockit SDK, optimized for server-side applications, and the Sun Java 2 SDK, provided for optional use by both client-side and server-side applications.

Note: The BEA JRockit 1.4.2 SDK is certified to be compatible with Sun Java 2 Standard Edition (J2SE), version 1.4.2.

For more information about BEA JRockit, see the BEA JRockit 1.4.2 SDK documentation at `http://e-docs.bea.com/wljrockit/docs142/index.html`.

For more information about operating systems, hardware, and SDKs supported by WebLogic Platform and WebLogic Server, see Supported Configurations for WebLogic Platform 8.1 at `http://e-docs.bea.com/platform/suppconfigs/configs81/81_over/index.html`

# Dependencies Between Installable Components

The installation program performs dependency checking to ensure that all components that provide functionality on which other components depend for proper operation are installed. These dependencies are visible during graphical and console mode installations. When you select or deselect components to be installed, the installation program checks for dependencies between components and automatically modifies the list of selected components accordingly.

Note: The same dependencies are enforced during silent installation: components on which other components depend are installed even if they are not explicitly referenced in a silent script.

Some examples of component dependencies are as follows:

- All components require the installation of WebLogic Server. This requirement is enforced in an obvious way during a graphical-mode installation: if you clear the WebLogic Server component check box, the boxes for the remaining components are cleared because those components cannot be run without WebLogic Server.
- The server component for any WebLogic Platform product requires the installation of the WebLogic Server server component and the WebLogic Workshop runtime framework. The WebLogic Workshop runtime framework depends on the WebLogic Server server component, and the WebLogic Integration and WebLogic Portal server components depend on both the WebLogic Server server component and the WebLogic Workshop runtime framework.

Note: The WebLogic Integration server component also requires the installation of the WebLogic Workshop IDE.

- The WebLogic Workshop IDE extension for any WebLogic Platform product requires the installation of the WebLogic Workshop runtime framework, the IDE, and the server component of WebLogic Server. This is because all extension users require an IDE installation, and most IDE users require a local server to build their applications.

Dependency checking is also performed when you uninstall part of WebLogic Platform, to ensure that you do not uninstall a component that is required by another component.

# WebLogic Platform Distribution Methods

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

## Web Distribution

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

Two methods are available for download:

- Net installer—this method (recommended) downloads a small setup file that enables you to select the components that you want to install on your system. The installer then downloads only the components you select. The net installer is approximately 23 MB.

Before the download begins, the net installer prompts you to provide the following information:

- Storage directory—the installation program downloads an archive file to your system for each component that you choose to install. By default, these archive files are downloaded to the temporary directory on your system. You can specify an alternate directory on your system for these files; they do not need to be collocated with the installation setup file, or with the installed software. If you do not specify an alternate directory, your temporary directory must have sufficient space to accommodate the archive files and the installation program. For more information about temporary space required by the installation program, see Temporary Disk Space Requirements. To conserve disk space, you can also specify that you want the downloaded files removed from your system after the installation is complete.
- HTTP Proxy—if you want to download these files using an HTTP proxy, you must specify the Host address and port numbers for the proxy server.
- Proxy authentication—if the HTTP proxy you are using requires server-side HTTP authentication, you must enter your username and password.

The net installer supports standard resume processing in the case of interrupted downloads. If the download is interrupted for any reason, either manually or by an unplanned network interruption, you can resume the download from the point at which it was interrupted. When the download is complete, the installation program performs an integrity check on the archive files that were downloaded to your system to verify that the files downloaded correctly.

- Package installer—this method downloads a standalone version of the installation program.

- The WebLogic Platform installation program contains all of the WebLogic Platform software components described in WebLogic Platform Software Components. The package installer is approximately 520 MB.
- The WebLogic Server installation program contains WebLogic Server and related samples, WebLogic Workshop and related samples, and the BEA JRockit SDK (for Windows and Linux platforms only). The package installer is approximately 300 MB.

Note: If you are planning to install the software in silent mode, you must download the package installer. Silent-mode installation is not supported by the net installer.

## CD-ROM Distribution

If you purchased WebLogic Platform or WebLogic Server from your local sales representative, you will find the following items in the product box:

- CD-ROMs containing the product software for Windows, Solaris, HP-UX, and Linux
- BEA WebLogic Platform Online Documentation CD
- The following printed documents:

- Installing BEA WebLogic Platform (this guide)
- Introducing BEA WebLogic Platform
- Introduction to WebLogic Server and WebLogic Express
- BEA Software License and Limited Warranty pamphlet
- Customer Support Quick Reference and Other Important Information card
- A flyer that provides a list of URLs for the online Release Notes for each component
- Legal agreements for third-party products

## Web Distribution of Service Packs and Rolling Patches

Any service packs and rolling patches are included in the latest distribution of WebLogic Platform 8.1, which you can download as described in Web Distribution. If you do not have WebLogic Platform 8.1 installed, you should install this distribution.

If you already have WebLogic Platform 8.1 installed, and if you have a BEA eSupport account, you can upgrade your software in one of the following ways:

- Use the Smart Update feature (recommended) to retrieve and install software updates from the BEA Web site. Smart Update retrieves updates only for those components that are currently installed in the target BEA Home directory.
- Download the Service Pack Upgrade from the BEA Customer Support Web site at `http://support.bea.com`, without downloading the entire WebLogic Platform distribution.

Details about installing WebLogic Platform service packs and rolling patches are provided in Installing Service Packs and Rolling Patches.

If you do not have a BEA eSupport account, go to the following URL to get one: `http://support.bea.com`

# Installation Prerequisites

The following sections specify the installation prerequisites for a WebLogic Platform installation:

- System Requirements
- Temporary Disk Space Requirements
- Administrator Privileges
- Licensing and Encryption

## System Requirements

The system requirements for WebLogic Platform are given in the following table.

Table 1-1 System Requirements

Component | Requirement
--- | ---
Platform configuration | A configuration of hardware, operating system, SDK, and database that is supported by WebLogic Platform is required. See WebLogic Platform Supported Configurations at `http://e-docs.bea.com/platform/suppconfigs/index.html`. This document also specifies other prerequisites and recommendations, such as recommended versions of the Java 2 SDK.
Processor | For a full WebLogic Platform installation, a 1-GHz CPU is recommended.
Hard disk drive | A full WebLogic Platform installation requires approximately 1 GB of disk space.
Memory | Full WebLogic Platform installation—512 MB of RAM minimum, 1 GB recommended WebLogic Server (with Sun Java 2 SDK)—256 MB of RAM minimum, 512 MB or more recommended (without WebLogic Workshop) WebLogic Server (with BEA JRockit SDK)—512 MB of RAM minimum WebLogic Integration—512 MB RAM minimum, 1 GB recommended WebLogic Portal—512 MB of RAM minimum, 1 GB recommended WebLogic Workshop—512 MB RAM minimum, 1 GB recommended
Color bit depth display and size | For graphical user interface (GUI) mode installation, 8-bit color depth (256 colors) is required. For console-mode and silent-mode installation, there is no color bit depth requirement.
Java 2 SDK | The WebLogic Platform installation program requires a Java run-time environment (JRE) to run. A JRE is bundled in the Windows installation program and in some UNIX installation programs (those with filenames ending in `.bin`). For other UNIX platforms, the WebLogic Platform installation program does not install a Java 2 SDK. 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 beginning of the `PATH` variable definition. 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 Starting Console-Mode Installation for .jar Installation Files

## Temporary Disk Space Requirements

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

By default, the installation program uses the following temporary directory:

- Windows platforms—directory referenced by the `TMP` system variable
- UNIX platforms—system-dependent temporary directory

Note: If you do not have enough temporary space to run the installation program, you are prompted to specify an alternate directory or exit the installation program.

To make sure that you have adequate temporary space, you may want to allocate an alternate directory for this purpose. To do so, follow the instructions provided in the following table.

On this platform . . . | Perform this step . . .
--- | ---
Windows | Do one of the following: Set the `TMP` system variable to a directory of your choice. If starting the installation program from the command line, include the `-Djava.io.tmpdir=``tmpdirpath` option replacing `tmpdirpath` with the full path of the directory that you want to designate as a temporary storage area for the WebLogic Platform installation program. For example: `platform` `XXX``_win32.exe -mode=console -Djava.io.tmpdir=D:\Temp` In the filename used in this example, `XXX` represents the version number of the software you are installing.
UNIX | Enter the following option on the command line when you start the installation program: `-Djava.io.tmpdir=``tmpdirpath` Here, `tmpdirpath` is the full path of the directory that you want to designate as a temporary storage area for the WebLogic Platform installation program.

## Administrator Privileges

Administrator privileges are required in the following circumstances:

- Installing Node Manager or an Administration Server as a Windows service

During a custom installation, you are presented with the option to install the WebLogic Server Node Manager as a Windows service. Also, if you choose to run the Configuration Wizard to create user domains, you can configure the Administration Server as a Windows service. When the Node Manager or a server is installed as a Windows service, it starts automatically each time you boot your Windows system. You must have Administrator privileges to install the Node Manager or a server as a Windows service.

For additional information, see "Setting Up a WebLogic Server Instance as a Windows Service" in Configuring and Managing WebLogic Server at `http://e-docs.bea.com/wls/docs81/adminguide/winservice.html`.

- Using WebLogic Workshop

If WebLogic Workshop is installed on a Windows system by a user with Administrator privileges, then all users must have Administrator privileges to use WebLogic Workshop. Otherwise, you may encounter an error when running WebLogic Workshop applications.

## Licensing and Encryption

The WebLogic Platform software cannot be used without a valid license. When you install 8.1 SP3 or higher, the installation program installs two non-expiring licenses: a license to use for development (`license.bea`) and a license to use for limited scale production deployments (`license_scale_limited.bea`).

To use WebLogic Platform in a full-scale production environment, you must purchase a production license. To find out how to do so, contact your sales representative or visit the BEA corporate Web site at `http://www.bea.com`.

For more information about development, scale-limited, and production licenses, see About WebLogic Platform Licenses.

Development and production licenses for pre-8.1 versions of WebLogic Platform do not work with WebLogic Platform 8.1; any such license must be upgraded to 8.1. Procedures for upgrading a license file and installing permanent licenses are provided in Installing and Updating WebLogic Platform License Files.

### About 128-Bit Encryption

Secure sockets layer (SSL) encryption software is available with two levels of encryption: 56-bit and 128-bit. In 8.1 SP3 and higher, the license files installed with WebLogic Platform enable both 56-bit and 128-bit encryption by default.

For instructions about enabling 128-bit encryption for earlier releases of WebLogic Platform, see "Enabling 128-bit encryption in SP2 or Earlier" at `http://e-docs.bea.com/platform/docs81/sp_notes/sp_notes.html#128bit_encryption`.

# Choosing a Type of Installation

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

## Complete Installation

In a complete installation, the following components are automatically installed:

- All software components included in the distribution. Software components vary depending on the software distribution method:

- WebLogic Platform Package Installer or CD-ROM—all the software components provided with WebLogic Platform, including sample files, as described in WebLogic Platform Software Components. Sample domains, as well as the WebLogic Platform Tour, are preconfigured for use with the PointBase database, allowing you to start running the samples as soon as the installation is complete.
- WebLogic Server Package Installer—WebLogic Server and WebLogic Workshop program files and all related sample files.
- Net Installer—All WebLogic Platform components, including WebLogic Server, WebLogic Workshop, WebLogic Integration, WebLogic Portal, and all related sample files.

- Two SDKs are installed on Windows platforms only: the Sun Java 2 SDK 1.4.2 and the BEA JRockit 1.4.2 SDK. For more information, see BEA JRockit SDK.

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

## Custom Installation

In a custom installation, you have the following options:

- You can choose which software components to install on your system. For a description of the software components provided with WebLogic Platform, see WebLogic Platform Software Components.
- You can choose whether to install the WebLogic Server Node Manager as a Windows Service. See Installing the Node Manager as a Windows Service. Sample domains preconfigured to use the PointBase database are created only for the installed components.

On Windows platforms, two SDKs are installed: the Sun Java 2 SDK 1.4.2 and the BEA JRockit 1.4.2 SDK. For more information, see BEA JRockit SDK.

# Installing the Node Manager as a Windows Service

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

- Start and stop managed servers in a domain.
- Monitor the self-reported health of managed servers and automatically kill server instances whose health state is "failed."
- Automatically restart managed servers that have the "failed" health state, or have shut down unexpectedly due to a system crash or reboot.

In a custom installation, you can optionally install the Node Manager as a Windows Service. In a production environment, you usually install the Node Manager only on server machines that host managed server instances of WebLogic Server. The WebLogic Server Node Manager is not installed as a Windows service in a complete installation. In a development environment, you may want to install the Node Manager on a server machine that hosts both the administration server and managed server instances of WebLogic Platform.

The Node Manager is installed as a Windows service only under the following conditions:

- You are installing on a Windows platform.
- You are performing a custom installation.
- The Node Manager for the current version of WebLogic Platform is not already installed on the server.

After you install the Node Manager as a Windows service, the service is started the next time you reboot the system. You can also manually start the service from the Windows Services control panel.

When you uninstall WebLogic Platform, the service is uninstalled also.

Notes: By default, the WebLogic Server Node Manager uses port 5555. If the Node Manager for a previous version of WebLogic Server is installed on the machine, the new version does not start when Windows starts because of port contention. To make sure that the new version starts when Windows starts, reconfigure the Node Manager to use a different port.

The BEA Node Manager service is linked to a BEA Home directory. If you have multiple BEA Home directories on your machine and you uninstall WebLogic Platform in the BEA Home directory linked to the Node Manager service, the uninstaller removes the service. If you have other instances of WebLogic Server that rely on the Node Manager, you must manually start the Node Manager or reinstall the Node Manager service.

If you uninstall an instance of WebLogic Platform that is not in the BEA Home directory linked to the Node Manager service, the uninstallation program does not uninstall the Node Manager service.

For more information about the Node Manager, including instructions for installing it on a UNIX server, see the following topics in Configuring and Managing WebLogic Server:

- "Overview of Node Manager" at `http://e-docs.bea.com/wls/docs81/adminguide/nodemgr.html`
- "Configuring, Starting, and Stopping Node Manager" at `http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html`

# Selecting Directories for the WebLogic Platform Installation

During installation of WebLogic Platform, you need to specify locations for the following directories:

- BEA Home directory
- Product installation directory

## Choosing a BEA Home Directory

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

The files in the BEA Home directory are essential to ensuring that BEA software operates correctly on your system. They perform the following types of functions:

- Ensure that licensing works correctly for the installed BEA products
- Facilitate checking of cross-product dependencies during installation
- Facilitate Service Pack installation

The following illustration shows the structure of a sample BEA Home directory, created by the WebLogic Platform installation program, that includes a bundled SDK.

This illustration depicts only the files and directories required in the BEA Home directory. If you choose the default product installation directory, however, you will see additional directories in the BEA Home directory, such as `weblogic81`. Although the default location for the product installation directory is within the BEA Home directory, you can select a different location outside the BEA Home directory.

Note: For some UNIX platforms, the WebLogic Platform installation program does not install the SDK.

During installation of WebLogic Platform, 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 Platform 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 Platform 8.1 in a BEA Home directory, but that BEA Home directory may also contain an instance of WebLogic Platform 7.0.

### Understanding the Functions of the BEA Home Directory

The files and directories in the BEA Home directory are described in the following table.

Table 1-2 BEA Home Directory Description

Component | Description
--- | ---
`ext_components` directory | Contains controls for third-party components and the TIBCO Rendezvous Control, if the latter is selected during the installation of WebLogic Integration. Java controls are server-side components that encapsulate external resources and business logic for use in Workshop applications. This directory contains two types of controls files supported by WebLogic Platform: full control implementation files (ready to be used) and control stub files (utilities that download the specified control implementations when needed). Both types of control files are integrated with the Workshop IDE and managed by the Workshop run-time framework. The full control implementation files delivered in `ext_components` are automatically installed with WebLogic Platform. When you are ready to start using them, however, you must integrate them, manually, with your application. For instructions, see "How Do I: Start Using a Packaged Control?" in the WebLogic Workshop Help at `http://e-docs.bea.com/workshop/docs81/doc/en /workshop/guide/howdoi/howStartUsingPackagedControl.html`. For ISVs and other software developers who want more information about creating custom controls, see "Creating and Packaging WebLogic Workshop Java Controls" in the WebLogic Platform ISV Partners' Guide at `http://e-docs.bea.com/platform/docs81/isv/controls.html`.
`sdk` directory | Contains the software for the Java 2 SDK installed with WebLogic Platform. The SDK provides the Java run-time environment (JRE) and tools for compiling and debugging Java applications. The SDK directories include: `jdk142_``XX`—the 1.4.2 version of the Sun Java 2 SDK. In this directory name, `XX` indicates the version of the Sun SDK installed on your system, for example `jdk142_08`. `jrockit` `XXX`—the 1.4.2 version of the BEA JRockit SDK. In this directory name, `XXX` indicates the version of the JRockit SDK installed on your system, such as `jrockit81sp5_142_08`. SDK options vary by hardware platform. BEA JRockit is installed on Windows and Linux platforms. On Windows platforms only, both the Sun and BEA JRockit SDKs are installed. Note: 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 are used to support the installation of all BEA WebLogic Platform products. The `utils.jar` file contains code that supports the `UpdateLicense` utility.
`license.bea` file | An XML file that contains the license keys for all the BEA WebLogic products installed in the BEA Home directory. Licenses are release specific. You cannot use a license from a previous release with WebLogic Platform 8.1. To convert a pre-8.1 `license.bea` file to a WebLogic Platform 8.1 `license.bea` file, see Upgrading Licenses from Previous WebLogic Platform Releases. To update your `license.bea` file for additional functionality, see Updating Your license.bea File. Note: Do not edit `license.bea` file manually. Doing so may cause operating problems for the currently installed BEA products, or result in problems later when BEA products are installed for maintenance upgrades.
`license_scale_limited.bea` file | An XML file that contains license keys to enable you to run a single server instance with a server capacity limited to approximately 3 percent of the full capacity of a production server. For instructions on installing this license file, see Replacing Your license.bea File.
`registry.xml` file | A registry file that contains a persistent record of all BEA products installed on the target system. This registry contains product-related information, such as version number, service pack number, and installation directory. Note: Do not edit this file manually. Doing so may cause operating problems for the currently installed BEA products, or result in installation problems when installing future BEA products or maintenance upgrades.
`UpdateLicense` (`.cmd/.sh`) | A command file (Windows) or a shell script (UNIX) that updates the current `license.bea` file with new license sections. The result is a merged license that contains both the existing and new license sections. For details about using the `UpdateLicense` utility, see Updating Your license.bea File.

### Creating Multiple BEA Home Directories

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

## Choosing a Product Installation Directory

The product installation directory contains all the software components that you choose to install on your system, including program files and examples. You are prompted, during the initial installation of WebLogic Platform, to choose a product installation directory. If you accept the default, the WebLogic Platform software is installed in the following directory:

>     C:\bea\weblogic81

Here, `C:\bea` is the BEA Home directory and `weblogic81` is the product installation directory for the WebLogic Platform 8.1 software. However, you can specify any name and location on your system for your product installation directory; there is no requirement that you name the directory `weblogic81` or create it under the BEA Home directory.

The installation program installs the software components in a product installation directory represented by the `WL_HOME` variable. If, on your initial installation, you choose to install individual components of WebLogic Platform and not the full complement of products, and later decide to install additional components (using the same BEA Home directory), you are not prompted, during the subsequent installations, to specify a product installation directory. The installation program detects the `WL_HOME` directory and installs the additional components under in it.

A description of the WebLogic Platform directory structure is provided in Understanding the WebLogic Platform Product Directory Structure.

# Generating a Verbose Installation Log

If you launch the installation from the command line or from a script, you can specify the `-log` option to generate a verbose installation log. The installation log stores messages about events that occur during the installation process, including informational, warning, error, and fatal messages. This type of file can be especially useful for silent installations.

Note: You may see some warning messages in the installation log. However, unless a fatal error occurs, the installation program completes the installation successfully. The installation user interface indicates the success or failure of each installation attempt, and the installation log file includes an entry indicating that the installation was successful.

## Syntax

To create a verbose log file during installation, include the `-log=``full_path_to_log_file` option in the command line. For example:

>     platformXXX_win32.exe -log=C:\logs\platform_install.log

In this filename, `XXX` represents the version number of the software you are installing.

The path must specify a file. You cannot create a folder simply by including a name for it in a pathname; your path should specify only existing folders. If your path includes a nonexistent folder when you execute the command, the installation program does not create the log file.

# Where to Find Upgrade Information

For information about installing service packs, see Installing Service Packs and Rolling Patches.

For information about upgrading WebLogic Platform components from previous releases, see the Upgrade Planning Guide at `http://e-docs.bea.com/platform/docs81/upgrade/index.html`.

For information about migrating from a previous release of WebLogic Server to WebLogic Server 8.1, see the WebLogic Server 8.1 Upgrade Guide at `http://e-docs.bea.com/wls/docs81/upgrade/index.html`.

# About Smart Update

The Smart Update feature enables you to upgrade your software quickly and easily with service packs and rolling patches.

When you start Smart Update, either from the Windows start menu or from the command line, it checks the version numbers of the products installed (associated with the current BEA Home directory), and then connects to the BEA Web site to check for available updates. For details about using Smart Update, see Installing Service Packs and Rolling Patches.

You can also use Smart Update to revert your system installation to an earlier version of the release. For additional information, see Uninstalling Maintenance Upgrades Using Smart Update.